maintenance view and table maintenance generator _ scn

Upload: raky0369

Post on 11-Oct-2015

82 views

Category:

Documents


0 download

DESCRIPTION

sap views

TRANSCRIPT

  • Getting Started Newsletters Store

    Products Services & Support About SCN Downloads

    Industries Training & Education Partnership Developer Center

    Lines of Business University Alliances Events & Webinars Innovation

    Log On Join UsHi, Guest Search the Community

    Activity Communications Actions

    Brow se

    0 Tweet 0

    7 Replies Latest reply: May 15, 2008 12:54 PM by Guest

    Share 0Like

    8882 View s

    Average User Rating

    (0 ratings)

    Maintenance view and Table MaintenancegeneratorThis question is Assumed Answered.

    Hi All,

    What is the difference between Maintenance view and Table Maintenance generator.

    Regards

    helpful answeres are surely rewarded.

    Praveen Makam May 7, 2008 7:17 AM

    Re: Maintenance view and Table Maintenance generator

    Refer to the below related threads

    Table Maintenance Generator

    table maintenance generator

    purpose of table maintenance generator

    Regards,

    Santosh

    Like (0)

    Guest May 7, 2008 7:20 AM (in response to Praveen Makam)

    Re: Maintenance view and Table Maintenance generator

    Can please you give the exact difference?instead of what they are.

    i mean the restrictions among them like. what can be done in one and not in another.

    Like (0)

    Praveen Makam May 7, 2008 7:25 AM (in response to Guest )

    Re: Maintenance view and Table Maintenance generator

    Priyanka,

    Maintenance view and table maintenance generator are two different thing elementarily, and

    Guest May 12, 2008 10:17 AM (in response to Praveen Makam)

  • Re: Maintenance view and Table Maintenance generator

    Hi All,

    Both are same through maintenance generator you are going to create the maintenance table. whcih

    will be accessed from the SM30 t-code.

    Regards,

    Madan.

    Like (0)

    Madan Mohan kurapati May 7, 2008 7:28 AM (in response to Praveen Makam)

    Re: Maintenance view and Table Maintenance generator

    Hi Priyanka,

    Maintenance views offer easy ways to maintain complex application objects.

    Data distributed on several tables often forms a logical unit, for example an application object, for the

    user. You want to be able to display, modify and create the data of such an application object

    together. Normally the user is not interested in the technical implementation of the application object,

    that is in the distribution of the data on several tables.

    A standardized table maintenance transaction is provided (SM30), permitting you to maintain the data

    from the base tables of a maintenance view together.

    Maintenance mechanisms, like screens and processing programs, must be created from the view

    definition with the transaction Generate Table View (SE54).

    Without creating Table View (SE54) for a table we cant use Maintenance views (SM30) to

    maintain the entries.

    Try to do this,

    Without creating the Generate Table Maintenance Dialog (SE54) try to use Maintenance views

    (SM30) for that table.

    it can be accessed only after creating SE54 for the specified table.

    Best regards,

    raam

    Like (0)

    Kodandarami Reddy Suravaram May 7, 2008 7:47 AM (in response to Praveen Makam)

    you cannot make a comparison between them.

    Maintenance view is one of 4 type of views that you could possibly define in SE11. It is a

    DDIC entity, and its own definition sits on underlying table definitions and relations.

    Now, with just the view in place, you cannot maintain data. You need a screen, some

    method to display the data contained in the view, and some logic with which you can

    perform operations like add, change, delete, transport, entries. This is where the table

    maintenance generator comes into picture. This is simply a connected transaction with your

    SE11, which enables you to define what is called a 'maintenance dialog', for your view. It

    automatically generates screens, controls, and logic to do all the above.

    There are enough links on both Maintenance View and Table Maintenange Generator in the

    above links, which give you detailed steps and info on how to go about each one of them.

    PS: remember, the table maintenance generator can also be used directly for tables itself!

    Cheers

    Rekha

    Like (0)

  • Re: Maintenance view and Table Maintenance generator

    Hi Priyanka,

    please visit for table maintenance>>>

    Table Maintenance Generator

    table maintenance generator

    purpose of table maintenance generator

    please visit for maintenance view>>>

    http://help.sap.com/saphelp_nw04/helpdata/en/38/81c1351181b73fe10000009b38f839/frameset.htm

    please mark all helpful answers...

    Amit.

    Like (0)

    Amit Gujargoud May 7, 2008 7:39 AM (in response to Praveen Makam)

    Re: Maintenance view and Table Maintenance generator

    hi,

    Maintenance views offer easy ways to maintain complex application objects.

    Data distributed on several tables often forms a logical unit, for example an application object, for the

    user. You want to be able to display, modify and create the data of such an application object

    together. Normally the user is not interested in the technical implementation of the application object,

    that is in the distribution of the data on several tables.

    A maintenance view permits you to maintain the data of an application object together. The data is

    automatically distributed in the underlying database tables. The maintenance status determines

    which accesses to the data of the underlying tables are possible with the maintenance view.

    All the tables in a maintenance view must be linked with foreign keys, that is the join conditions for

    maintenance views are always derived from the foreign key.

    cannot directly enter the join conditions as for database views.

    There are some restrictions for the attributes of the foreign keys with which the tables in a

    maintenance view can be linked .

    A standardized table maintenance transaction is provided (SM30), permitting you to maintain the data

    from the base tables of a maintenance view together.

    Maintenance mechanisms, like screens and processing programs, must be created from the view

    definition with the transaction Generate Table View (SE54). This makes it possible to create easy-to-

    use maintenance interfaces in a simple manner.

    Table Maintanence generator :

    In the table maintenance generator screen, we should give Authorization Group,

    Function Group name (Function Group name can be same as table name),

    Maintenance type can be one step or two step, usually we will create with one

    step. we should give maintenance screen number. After clicking on create button,

    a table maintenance generator will be created.

    To check it go to SM30 . In SM30, we find display, Maintain options.

    We can view the table contents by choosing Display and we can create table

    entries by choosing Maintain.

    In the production system, end-users will not be having access to transaction

    codes like SE11 and SE16. Developers will not be having access to many

    transaction codes including the above two.

    To view the contents of the database table, we will use SE16n in Production

    system. All these authorizations will be maintained by BASIS team, by creating access profiles.

    So in order to edit or create the contents of a database table, we should go for

    table maintenance generator. In real time, authorizations will be maintained in

    production system. (even in development and Test systems to some extent).

    The second reason is, we can edit or create multiple entries at a time, using table maintenance

    generator.

    Apart from that we have options like 'Enter conditions' in table maintenance screen SM30.

    Table Maintenance generator: Difference between one step and two steps.

    Guest May 15, 2008 12:54 PM (in response to Praveen Makam)

  • Follow SCNSite Index Contact Us SAP Help Portal

    Privacy Terms of Use Legal Disclosure Copyright

    0 Tweet 0Share 0Like

    While creating table maintenance generator, we find below options:

    1.When we choose one step, we have to give the screen number in Overview Screen field.

    2.When we choose two step, we have to give both overview screen number and single screen

    number.

    You can give any number for screen. Dont give 1000 screen number. As this number is reserved for

    selection screen.

    When we choose two step, two screens will be created for table maintenance. For single step only

    one screen will be created.

    When we choose two step, table maintenance will work as follows

    Go to SM30, give the table name for which you have created table maintenance-

    Overview screen will be displayed. To create entries, when you click on new

    entries. Another screen will be displayed, where you give input and save. You can enter one record at

    a time.

    When we choose single step, table maintenance will work as follows:

    Go to SM30; give table name for which you have created table maintenance-

    Overview screen will be displayed; To create entries click on new entries, you can enter the records

    on the same screen. You can enter multiple records at a time.

    We use single step generally, as it is user friendly.

    To completely understand the difference and above points please do exercise by

    creating table maintenance generator in both ways (using single step and two

    step).

    Like (0)