Entry restriction in maintenance view

i have created a maintenance view in which user input and save..its working fine.now my requirement is that user should not be able to enter freely in the fields..means only values from database.
like if field is customer then only value came from f4 should allowed.

Hi,
There are several ways:
1. Maintain check tables in for the fields you want the entries to be validated.
2. You can also use events in maintaince views and use event entry created to validate the entries. in order to create the event
in the maintainence view fo to menu path Environment > Modification> events and maintain an entry there for event 5 which is create new entry then you can use the structure of the fielld of the table to carry out what ever checks you wnat in the subroutine that you have created.
Regards,
Himanshu

Similar Messages

Maintenance view: add new entry under existing ones

Hi,
I would like to add a new entry in a maintenance view, but keeping the existing entries visible. That is, I want a new line to appear under the older ones, so I can see them, instead of opening a whole new screen with empty lines.
Thanks in advance,
Ivson

If you want to add new field in the view.
Goto SE54 and carry out the following steps:-
1) Enter the name of the table or view.
2) Choose Generated objects.
3) Choose Create/Change. You go to the generated objects maintenance screen.
4) Choose Change. A screen of reasons for changes appears.
Select option(s) and choose Continue.
The new field will appear in the view.

Maintenance view Vs Table maintenance

Hi,
I would like to know the dif between T.Maintanance And Maintenance view.
As we know as per the def we know Maintenance view will be used to maintain a table. But I have never created any M.view for the same.
However we use Table maintenance generator and SM30 for the same. How these 2 concepts are differnet?
Which one is the best method 2 use?
what one step and two setp process? Advantage and usage of 2step process?
Thanks in advance.
PRa

Hi Praneet..
These two are different concepts altogether but they have some connection.
1. Table Maintenance: To facilitate the Updation / Viewing the Records of a Table thru a Tcode We have to Generate the Table maintenance (program and screens) in Tcode SE54.
This will generate the Function Groups and Screens required to Maintain the Entries in table.
Then only we can maintain this Table in Tcode SM30.
2. Maintenance view: It is one type of View which can be used to update/view the data from multiple tables at a time.
But after creating a Maintenance view, We must generate the Table maintenance .
Only then we can maintain the entries using a Maintenance view.
<b>REWARD IF HELPFUL.</b>

About Maintenance View has 2 ZTABLEs

Hello ALL.
I created a Maintenance View has 2 tables.
2 tables are linked to one another with foreign keys.
(2 tables are ZTABLEs.) (Cardinality is 1:1)
I'm trying to entry records using Maintenance view.(SM30)
I can insert new records to 2 tables at the same time,
BUT I can't update records at the same time.
ONLY 1 table (check table) 's data is updated.
I don't know why.
also I can't delete records at the same time.
ONLY 1 table (check table) 's data is deleted.
please let me know how to do.
Thanks.

Hi Rie,
When you define a view maintenance with 2 or more tables, you select fields from each table, and map tables with foreign keys.
When a record of a view is updated, then the view fields are split into the data of the underlying tables, depending on which field comes from which table. Correspondingly, only those tables are affected, whose fields have changed.
This confirms to 2 points -
1) If you have 2 tables in a maintenance view, you must include the key fields of both the tables in the view. If there are common key-fields, you can them from either of the table.
2) If there are other non-key fields which are common, then you can assign them to only one of the tables in the view. But if you like an extended logic to change their values in the other table also, then you must maintain seperate logic to do so. Events!
You can try using an After Save, or any such events.
Regarding events, you will find a lot of documentation and links by searching the forum itself.
Cheers
Rekha

Maintenance view entries asking for Tr. request

Hi ,
I have created a Maintenance view for a table.
While creating entries through view it is asking for
transport request.
How can I get rid of this prompt for transport request ?
Thanks,
Sandip.

Hi sandip,
1. Thats bcos in se11,
the DELIVERY CLASS
for this table must be C
(customizing table)
2. Make it to A (applicatkion table)
save, and activate the table,
and once again, create table maintenance.
regards,
amit m.

For new entries pass input screen values to PBO of maintenance view

For maintaining Z table using a customized program with selection screen and FM   'VIEW_MAINTENANCE_CALL' is called . Its working fine for selecting existing entries as per selection screen values. In case if there is no entry found as per input values the maintenance screen comes blank with "No entries found that match selection criteria".
Instead of this want to pass input screen values on maintenance view if no entry is found thru PBO selection screen. The total & extract tables are empty. No suitable event is found. How this can be done.
Thanks
pt

You could try in a first step to read database to check existence :
CALL FUNCTION 'VIEW_GET_DATA'
EXPORTING
    view_name   = 'ZXXXX'
TABLES
    dba_sellist = it_sellist
    data        = data
EXCEPTIONS
    OTHERS      = 1.
If data found, call the view maintenance
CALL FUNCTION 'VIEW_MAINTENANCE_CALL'
EXPORTING
    action      = 'U'
    view_name   = 'ZXXXX'
TABLES
    dba_sellist = it_sellist.
else create one new record providing required value in a work area
CALL FUNCTION 'VIEW_MAINTENANCE_SINGLE_ENTRY'
    EXPORTING
      action               = 'INS'
      view_name            = 'ZXXXX'
      insert_key_not_fixed = ' ' " if full key provided
      no_transport         = 'X'
    TABLES
      dba_sellist          = it_sellist
    CHANGING
      entry                = wa_zxxxx
    EXCEPTIONS
      OTHERS               = 1.
Regards,
Raymond

Maintenance view error

Hi All,
I am facing a weird issue: -
There is a view /asgws/scr_v001 (a z view in custom namespace). This view is transported from system G1 to G2.
G1 system is SAP4.7 and G2 system is SAP ECC6.0.
Now maintenance view for this view is maintained and generated successfully. It is working fine in G1 system.
But in G2 system when i try to see its contents through Se11, it shows "No database view exists for the view /asgws/scr_v001".
I have seen other threads also and found relevant solutions : -
1) View Type: It is C in both the cases, so no problem with that
2) Table maintenance allowed or not: It is 'Table display/maintenance allowed with restrictions' in both the systems G1 and G2.
However, I could see one difference while comparing the tables in both systems.
Database entry Dd02L-Mainflag is 'X' in G1 system where it is working fine.
Database entry DD02L-mainflag is ' ' in G2 system where it is not working.
As per my understanding this is because table maintenance is not allowed in this case. but again there are no differences in both the systems.
Also Is compare flag related to this in anyways. Though i could not find any reelvance just confirming because so far no clues of why things are going wrong ??
Request you to please help me sorting this issue.
Thanks in advance for your valuable time and inputs.

Hello,
You really need to pay attention when transporting objects especially dictionary objects between different releases of SAP.
Technically the import will succeed most of the time, but generation errors can happen, certain functionalities may no longer work, table data can be truncated, etc ...
I never transport view definitions from a lower release towards an ECC 6.0 system (Netweaver 7.0).
In Netweaver 7.0 SAP has built in new features for dictionary objects like views, tables, etc.
This is why most of the DD0** tables in Netweaver 7.0 contain extra fields and extra field values.
These new field values can never be transported from a lower release because they don't exist there !
A good starting point is the composite OSS-note:
SAP Note 1090842 Composite note: Transport across several releases
Wim

Maintenance View Validations

I have a custom table for which I am maintaining a Maintenance View.
I want to provide some validations and checks on the fields entered by the user in that maintenance view.
For example, if the user enters a value greater than 1000 in quantity field, I want to display a message saying that " enter only values below 1000". This is part of customer requirement.
Can I provide validations on fields in Maintenance view and if yes, then how ?
Thanks,
Urmila

Hi this may help u.
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 (see Foreign Key Relationship and Join Condition). You 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 (see Restrictions for Maintenance and Help Views).
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.
You can find out how to create such maintenance mechanisms in the documentation BC - Generate Table Maintenance Dialog.
Creating Maintenance Views
Procedure
Enter an explanatory short text in the field Short text.
You can for example find the view at a later time using this short text.
Enter the primary table of the view under Tables in the Tables/Join conditions tab page.
Only those tables that are linked with the primary table (indirectly) with a foreign key can be included in the maintenance view.
If required, include more tables in the view. In a maintenance view you can only insert tables that are linked to one another with foreign keys.
Place the cursor on the primary table and choose Relationships. All existing foreign key relationships of the primary table are displayed. Select the required foreign key and choose Copy. The secondary table used in such a foreign key is included in the view. The join conditions derived from the foreign keys (see Foreign Key Relationship and Join Condition) are displayed.
You can also insert tables that are linked by foreign key with one of the secondary tables that was already inserted. To do this, place the cursor on the secondary table and choose Relationships. Then proceed as described above.
For maintenance and help views, there are certain restrictions on the foreign keys with which the tables can be included in the view (see Restrictions for Maintenance and Help Views). The foreign keys violating these conditions are displayed at the end of the list under the header Relationships with unsuitable cardinality.
On the View fields tab page, select the fields that you want to copy to the view.
Choose Table fields. All the tables contained in the view are displayed in a dialog box. Select a table. The fields of the table are now displayed in a dialog box. You can copy fields by selecting them in the first column and choosing Copy.
All key fields of the primary table must be included in a maintenance view. In addition, all key fields of secondary tables that are not involved in the foreign key (that is, which are not linked via a join condition to a key field already included in the view) must be included in the view.
This ensures that the records inserted with a maintenance view can be written correctly in the tables contained in the view.
On the Selection conditions tab page, you can (optionally) formulate restrictions for the data records that can be displayed with the view (see Maintaining Selection Conditions for Views).
The selection conditions define the data records that can be selected with the view.
In the Maintenance status tab page, define the maintenance status of the view.
The maintenance status defines how you can access the view data with the standard maintenance transaction (SM30).
Choose .
At activation, a log is written; it can be displayed with Utilities ® Activation log. If errors or warnings occurring when the view was activated, the activation log is automatically displayed.
Go to Transaction SE54 with Environment ® Tab.maint.generator.
From the view definition you can generate maintenance modules and maintenance interfaces that distribute the data entered with the view to the base tables of the view. You can find more information in Creating a Maintenance Dialog.
Other Options
Recording documentation: You can create information about using the view with Goto ® Documentation. This documentation is output for example when you print the view.
Changing the data element of a view field: Select column Mod (modification) for the view field. The Data element field is now ready for input. You can enter a data element that refers to the same domain as the data element of the assigned table field here. Cancel the Mod flag if you want to use the data element of the assigned table field again.
Enter the delivery class of the view: In the Maintenance status tab page, select the delivery class of the maintenance view. If you assign the delivery class G or E to the view, you must also maintain a customer namespace (key block) for the view entries. To navigate to the appropriate maintenance transaction, choose Define Customer Namespace.
Entering the maintenance attributes of the view field: In the View fields tab page you can define the Maintenance Attributes of the view field in column F.
Check functions: With Extras ® Runtime object ® Check you can determine whether the definition of the view in the ABAP Dictionary maintenance screen is identical to the definitions in the runtime object of the view. With Extras ® Runtime object ® Display you can display the runtime object of the view.
table maintai9nenece generator
The Table Maintenance Generator is used to create table maintenance program to add, modify or delete records in the database table. This can be accessed using transaction SE54 or in SE11 using the menu Utilities->Table Maintenance Generator.
Table maintenance allows you to create entries for that table
Follow these steps to generate table maintenance
1) Go to SE11 and check table maintanance check box under attributes tab.
2) Go to menu Utilities -> Table Maintanance Generator ->
Create function group and assign it under function group input box. You can enter same as table name for function group. Also assign authorization group default &NC& .
3) Select standard recording routine radio in table table mainitainence generator to move table contents to quality and production by assigning it to request.
4) Select maintenance type as single step.
5) Maintainence screen as system generated numbers this dialog box appears when you click on create button.
6) Save and activate table.
useful links
http://www.saptechies.com/how-to-create-table-maintenance-generator/
http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ecdf446011d189700000e8322d00/content.htm
http://www.saptechies.com/table-maintainance-generator/
with regards,
Hema Sundara.
pls reward if u find it helpful.

Possibility to edit datasets, when there is already a maintenance view?

Hello again,
is it right that I can modify datasets even when there exists a generated maintenance view for the table?
It was usual for me, that in the transaction SE16 don't allow that.
Thank you for your answers!
Melanie

Depends on the setting for "delivery and maintenance" in SE11, should be set to "allowed with restrictions" for the underlying tables of the view. Also check the very good F1 help for this field.
Thomas

Using DYNP_VALUES_UPDATE with a Maintenance View

Hi,
I am using a maintenance view to insert values into a table. When user creates a new entry, based on the value provided for a field,I need to fill a read-only field. In PAI, when user enters a value for one field, I am using FM 'DYNP_GET_STEPL' to get the current line and then DYNP_VALUES_UPDATE to fill the contents to the read-only field. But this does not seem to work. Any idea?
Regards
Rachana

Hi Tamas,
I tried both the options suggested by you.
I am updating the underlying structure, still its not visible when the screen loads again. But if you see the same field gets filled with DYNP_VALUES_UPDATE if an F4 help is used for teh first(editable) field and then my read-only field is also filled in the PROCESS ON VALUE REQUEST module.
So my guess is that, since it is a table control, it loops through the rest of the table control which is empty and my underlying structure gets cleared. So the problem could be where I am actually filling the field.
Is it possible to somehow fill the <EXTRACT> table so that teh value is not lost?
Regards
Rachana

How to call a maintenance view from a program

Hello Abapers,
Can anybody explain with some examples. How to call a mainetenance view from a program.
Thanks
Ranjith.

Use FM 'VIEW_MAINTENANCE_CALL'.
REPORT zmaintaintest.
VARIABLES / CONSTANTS
CONSTANTS:
                c_action(1) TYPE c VALUE 'U',                                 "Update
          c_viewname TYPE tabname value 'ZEMP_EXAMPLE', "View Name
          c_field(6) TYPE c VALUE 'EMPNO'.                            "Field Name
INTERNAL TABLES
DATA: itab_rangetab TYPE STANDARD TABLE OF vimsellist,
          v_empno TYPE zempno,
          wa_rangetab TYPE vimsellist.
SELECTION SCREEN
PARAMETERS:     p_empno TYPE   zempno   OBLIGATORY. "Emplyee ID
AT SELECTION-SCREEN
AT SELECTION-SCREEN.
Chcking the existence of the user in EMPLOYEE table
PERFORM validate_employee.
START_OF_SELECTION
START-OF-SELECTION.
This will restrict the user view so that user can only view/change
Table data corresponding to his/her Employee ID
PERFORM define_limited_data_area.
Displaying table maintenance view for a particular employee ID
PERFORM call_view_maintenance.
*&      Form validate_employee
Validate plant entered in the selection screen
FORM validate_employee.
SELECT SINGLE empno     u201CEmployee ID
    FROM zemp_example     u201CEmployee Table
    INTO v_empno
    WHERE empno = p_empno.
IF sy-subrc <> 0.
    MESSAGE 'Not an Valid User' TYPE 'I'.
ENDIF.
ENDFORM.                    "validate_employee
*&      Form DEFINE_LIMITED_DATA_AREA
To restrict the user view so that user can see/change table data
corresponding to his employee ID. Here one internal table is
getting populated with field name as u201CEMPNOu201D (Key field of the table)
And value as given by user in Selection Screen and this is passed as
Parameter in function module 'VIEW_MAINTENANCE_CALL'
FORM define_limited_data_area.
CLEAR wa_rangetab.
wa_rangetab-viewfield = c_field.
wa_rangetab-operator = 'EQ'.
wa_rangetab-value       = p_empno.
APPEND wa_rangetab TO itab_rangetab.
ENDFORM.                    "define_limited_data_area
*&      Form CALL_VIEW_MAINTENANCE.
Displaying table maintenance view for a particular employee ID
FORM call_view_maintenance.
CALL FUNCTION 'VIEW_MAINTENANCE_CALL'
    EXPORTING
      action           = c_action
      view_name   = c_viewname
    TABLES
      dba_sellist     = itab_rangetab.
ENDFORM.                    "call_view_maintenance
Regards,
Joy.

Updates through a maintenance view

Hi,
I'm having difficulty with maintenance views. I thought it ws possible to construct a maintenance view consisting of two or more tables and be able to update non-key fields in any table, provided the tables were linked via FK and had suitable cardinality of C:1.
However, this seems to be what I've found: you can only update non-key fields in the primary table. Although fields in the secondary tables appear as though you can update them (via SM30), any data changes you make are erased (as you look at it!) when you hit Save - the original value returns.
Is my assessment correct? SAP Help is vague and ambiguous on the matter.
Also, maybe someone could explain the cardinality requirements. SAP Help states the FKs must have N:1 cardinality, but as far as I can see it should be C:1.
Thanks,
T.

Hello Tenchy
You are talking about view clusters (SE54) where you have hierarchical linked tables that can be maintained together.
Obviously, you cannot edit key fields of the primary table. Instead you need to use execute two operations:
- DELETE entry
- CREATE new entry
It goes without saying that the same operations are propagated to the dependent entries in secondary tables.
The cardinality between primary table and secondary table should be 1:N meaning
- for each entry in the primary table you can have none or multiple entries in the secondary table
- you cannot have secondary records for which the corresponding primary record does not exist
Regards
Uwe

Short Dump while scrolling in a maintenance view

A maintenance view has one field, defined as "Radiobutton".
1) Select the radiobutton for one entry.
2) Scroll down so that in the new page (i.e. the entries displayed in the new page) the entry selected in the first step is not visible.
3) Select any radiobutton again corresponding to any of the entries displayed in the new page.
4) On scrolling up again the short dump occurs.
The short dump text says "More than one radio button is active".
Any inputs in this regards are appreciated.
Thanks.
Gajendra.

Hi,
that means you are trying to make two radio buttons active.
parameters: ra radiobutton group g1 default = 'X',
rb radiobutton group g1.
ra = 'X'.
and rb = 'X'.
in your case so obviously it will dump.
check your coding..
and show your code...
Regards
vijay

Activate Delimit in Table maintenance view

Hi,
I am creating a maintenance view for a custom table which has begin and end dates as part of the key fields. I want to activate the Delimit functionality on SM31 so we can have a history of the changes. Do you know how to activate this option? Please help!
Thanks, Chuong

It is not possible via SE11 . in SAP HR you define u201Ctime constrain u201C in table u201CV_T582Au201D for all ITs . If I want to do something like this , I will probably look at module pool logic of any IT .
Thanks,
Saquib Khan
FYI
Time Constraint
A time constraint indicates whether more than one infotype record may be available at one time. The following time constraint indicators are permissible:
o     1: An infotype record must be available at all times. This record may have no time gaps. You may not delete the record last stored on the database because all records of this infotype would otherwise be deleted.
o     2: Only one record may be available at one time, but time gaps are permitted.
o     3: Any number of records may be valid at one time, and time gaps are permitted.
Other possible time constraint indicators are as follows:
o     A: Only one record may ever exist for this infotype. It is valid from 01/01/1800 to 12/31/9999. Splitting is not permissible.
View V_T582B Infotypes Which are Created Automically controls whether the system automatically creates the infotype record for an employee hiring or an applicant data entry action.
Infotypes with time constraint A may not be deleted.
o     B: Only one record may ever exist for this infotype. It is valid from 01/01/1800 to 12/31/9999. Splitting is not permissible.
Infotypes with time constraint B may be deleted.
o     T: The time constraint varies depending on the subtype.
o     Z: Refers to time management infotypes. The time constraint for these infotypes depends on the time constraint class defined in view V_T554S_I Absence: General Control. Collision checks are defined in view V_T554Y Time Constraint Reaction.

Problem in Table maintenance view

Hi all,
i am getting some problem in table maintenance view.
In my table i have some fields and when i created my table maintenance view , it is created , but when i try to see it in SM30 its not showing my fields and even i am unable to create a new entry. when i click
new entries its going back to the sm30 screen..
How to go abt it
please help me

Hello,
Have you created the table maintanence view the right way.
You can get good help from below link: [[http://www.****************/Tutorials/ABAP/TableMaintenance/demo.htm]]
Also, please check the Delivery Class and Data Browser/Table View Maint. in the Delivery and Maintanence tab of the table.
Thanks,
Jayant
Edited by: Jayant Sahu on Nov 24, 2008 3:00 PM

Entry restriction in maintenance view

Similar Messages

Maybe you are looking for