I have to make Multiple entry at table maintanance at a time

Question

Hello all,
My requirment is to enable the multple user can loginto the same table for making there entry simultaneosuly .
i have created the table and table maintance as well. and i have created the new lock object and added the code accrdingly and i have used the custom fm which is generated in the tablemainta  function group.
forex: table xyz
user 1 , 2, 3, 4, 5,so on..
table should allow all user tomake there entry at time and the entry edited one user should be disabled to other user.
I have gone the forum i didnt found the correct one ..plz guide me ..plz find the attached code .i got this code and referredthe samein my prog ..any suggestions on the below.
1.       Create table ZTEST_SHUKS3.
2.       Create table maintenance generator for the table. 
3       Create lock object EYTSS_E433SH in SE11. Give it name as EZTEST_SHUKS3. 
4       create a report  ZREP_SHUKS3 and transaction code ZTEST_SHUKS3  to call this report. This tcode will call table  mainatance     generator of table ZTEST_SHUKS3 . 
5  create the report as below
6 Now open table maintenance function  group(ZTEST_SHUKS3)  in SE80.We know for table maintenance SAP automatically creates code in the function group. Now we will make some modification in that existing code to change the behavior. Open the screen you created through table maintenance and add one module. 
screen: 0001
double clik on screen and add one module in PBO of the screen
loop at extract with control
tctrl_ZTEST_SHUKS3 CURSOR NEXTLINE.
MODULE LIST SHOW LISTE
ADD HERE
MODULE m_change_locking
Check the code below to be added in the module m_change_locking. 
MODULE m_change_locking OUTPUT.
*Call the function module corresponding to the lock object we created
  CALL FUNCTION 'ENQUEUE_EZTEST_SHUKS3'
    EXPORTING
      matnr          = ztest_shuks3-matnr
      werks          = ztest_shuks3-werks
    EXCEPTIONS
      foreign_lock   = 1
      system_failure = 2
      OTHERS         = 3.
  IF sy-subrc NE 0.
row is locked..hence gray..
    LOOP AT SCREEN.
      screen-input = 0.
      MODIFY SCREEN.
    ENDLOOP.
  ENDIF.
ENDMODULE.                 " m_change_locking  OUTPUT 
REPORT  zrep_shuks3.
**Selection range for view maintenance
DATA:
  BEGIN OF selekttab OCCURS 1.         "Selektionsbereich
        INCLUDE STRUCTURE vimsellist.
DATA: END OF selekttab,
**Table of inactive CUA functions for view maintenance
BEGIN OF excl_cua_funct OCCURS 1.    "inaktive CUA-Fkt bei View-Pflege
        INCLUDE STRUCTURE vimexclfun.
DATA: END OF excl_cua_funct.
DATA: lt_enq_del TYPE STANDARD TABLE OF seqg3,
      lt_enq_read TYPE STANDARD TABLE OF seqg7,
      lw_enq_read TYPE seqg7,
      lw_enq_del TYPE seqg3,
      lv_subrc TYPE sy-subrc.
*Read all the lock details in system
CALL FUNCTION 'ENQUE_READ2'
  EXPORTING
    gclient = sy-mandt
    gname   = ' '
    guname  = '*'
  TABLES
    enq     = lt_enq_read.
*We will search entry for table level lock for our table
LOOP AT lt_enq_read INTO lw_enq_read
WHERE gname EQ 'RSTABLE'
AND   garg CS 'ZTEST_SHUKS3'.
  MOVE-CORRESPONDING lw_enq_read TO lw_enq_del.
  APPEND lw_enq_del TO lt_enq_del.
ENDLOOP.
*Delete table level lock entry for our table
CALL FUNCTION 'ENQUE_DELETE'
  EXPORTING
    check_upd_requests = 1
  IMPORTING
    subrc              = lv_subrc
  TABLES
    enq                = lt_enq_del.
*Now call the table maintenace generator.
CALL FUNCTION 'VIEW_MAINTENANCE_CALL'
  EXPORTING
    action               = 'U'
    view_name            = 'ZTEST_SHUKS3'
    show_selection_popup = 'X'
  TABLES
    dba_sellist          = selekttab
    excl_cua_funct       = excl_cua_funct.
I followed the same steps but still not getting the multiple user enable .
plz help
regards
Raju
Edited by: abaprthree on Jul 22, 2009 7:54 PM

Answer 1

Hi,
I think you are looking for the report which will allow only for entries not for change. In this case, at PBO you write the code to make all the rows in display mode which have records using LOOP at SCREEN .....ENDLOOP. When you click on on NEW ENTRY button, add blank rows and put user entries. When you save,check for existing entries in the table because many users are entering the data at the same time, so check for duplicates KEY entries and UPDATE the table on SAVE button. If you will go in this way, I don't think you have to go for LOCK object. It's required only if you are going for EDIT mode.