table maintainance or table control

[former_member329859]

Hello experts,

I have to make one screen for the user to put the data.

input format is as below,

at top month and year fieilds and below that other field in a table.

so please suggest me that which way i ll have to choose, table control or table maintainace,

please give me proper example for your suggested option

Thanking You,

Gaurav

[jayanthi_jayaraman]

Hi,

Table maintenance is used for mainitnaning entries for a specific table.

Table control is used in dialog programming.go through this link, I am explaining the table control.

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/documents/a1-8-4/table%20c...

[former_member329859]

hello jayanti,

please tell me how to take those fields which are above the table (month,year).

[Former Member]

Hi Gaurav,

As per my understanding of your requirement I guess you need the best of both Table Maintainence and Table Control.

I have a couple of doubts like will the fields month and Year influence the value of the Table entires any ways? Are they part of the key fields or are they a part of the Table ?

Table Maintainence is mostly used for maintaining the Customization data in SAP. But the same can be used for maintainence of Tables also. If you want to maintain the table then you can use the Table Maintainence Generator to generate the Screens. The advantage is that it will create all the functionality like 'Create Entries, Change/Modification and Deletion' of entries thorough the generated function modules. You don't need to come up with API's to take care of the functionality. But the downside is that you will lose the flexibility of custom coding in the Generated Screens.

If you use Table Control, you will need to come up with the Dynpro's Screens which will give a lot more flexibility to create and add your own code and functionlity. But you need to come up with the API's (FM's interacting with the Databases) along with the Lock Objects (SAP Locking Mechanism) to take care of insertion,deletion and modification of data properly.

So decide which one you want to use. And let me know so that I can suggest you the route through which you can come up to meet the requirements.

Hope this helps.

Thanks,

Samantak.

[former_member329859]

hello samantak,

here in my case the month and year are primar fields in my table so that i can select data for perticular month using that input.

and because of the above condition i think the useof table control will be right for me, if i want to display data on the same screen using input.

(is it possible in table maintainance gerator to display data with condition of month , also how to take fields in maintainance gerator saperatory )

thanks

gaurav

[Former Member]

Hi Gaurav,

As per you response, I will suggest you to approach with the customized Dynpro Creation. This will be very flexible and also very adaptable than the Table Maintainence approach.

You can always use the Table Maintainance Approach, but if you have to seperate the fields as per your requirement then you need to modify the views which will again need to readjust and activated. Also it depends on the approach you need to take as to come up with one screen or two screen approach.

You can have a look at the numerous demo code and examples supplied in the ABAPDOCU Transaction Code which will guide you with the entire development.

Hope this helps.

Thanks,

Samantak.

[christine_evans]

>

> Hello experts,
> I have to make one screen for the user to put the data.
> input format is as below,
> at top month and year fieilds and below that other field in a table.
> so please suggest me that which way i ll have to choose, table control or table maintainace,
> please give me proper example for your suggested option
> 
> Thanking You,
> Gaurav

I find SAP standard table maintenance very restrictive, though there are exits you can use for validation etc to make it more flexible. In this situation, I'd always choose to create a dynpro. Not difficult since the wizard mostly takes care of any table controls you want to create and you get total control over what your transaction does eg you can implement row level locking rather than the full table lock that comes as standard with maintenance views.