Hello Tobias,

In our landscape we are have our HANA and SLT instances connected to the ECC QA instance. We have not yet configured HANA for production instance. Now we are planning to refresh our EC QA instance from production.

1. Since we do not have a HANA configured for production, we do not have to delete the triggers or logging tables after the refresh.

2. For QA instance we simply need to stop the replication (not Suspend) for the tables before the refresh and then just replicate the tables again after the refresh.

Are the above statements correct?

Thanks

Dee

this would require a functionalt. Workflow expert and even abap developer to make a Z table to store their grades etc or read from It0001

So main work is for WF expert, to make a WF or copy from anyt existing one, in SWDD

Can you share your code? Please make sure that you pass values for communication structures KOMFK,KOMFKGN,KOMFKKO,KOMFKTX. Also check following notes:

• Note 1520236 - Conditions sequence for GN_INVOICE_CREATE
• Note 869311
  

you are on which release?

You can use IT0105 or make your own iview to update these details, many do this.

00105 is standard delivered and others can be added easily from EHp5 onwards

Introduce new infotype

http://help.sap.com/erp2005_ehp_05/helpdata/en/38/fd1f7ed337404cae5c8a2341dbdca4/content.htm

Hello Kannan,

there is not much to say around this, use in a cell following syntax for a formula:

1. UserResponse(<technical_name_of_variable>)

2. PromptSummary()

If you are not sure, then visit following interactive tutorial:

Web Intelligence 4.0: Create a formula to display a filter selectionWeb Intelligence 4.0: Create a formula to display a filter selection

Also search for those keywords in the product documentation available here:

http://help.sap.com/bobi

Best regards,

Victor

http://help.sap.com/businessobject/product_guides/sbo41/en/sbo41_webi_user_guide_en.pdf

Hi Narasimha,

BASIS, ABAP or HANA would be best.

BASIS - if you want to move to administration.

ABAP - programming and debugging.

HANA - Database mangaement, cloud or Analytics.

Regrds,

Kalyan.

Hi,

Go to QMFE table in ECC, there is a field called "Defect valuation" which can store up to length 16 as FLOAT type.

I think  1.0100000000000000E+01 is overflowing than 16 length. You may try to adjust the value in the table or length has to be increased(which may be risky thing). Please sit with your functional team and discuss about this value in the QMFE table.

Please contact SAP before editing the domain of the field.

Regards,

Suman

Hi Sandeep,

I don't quite understand what you're trying to achieve. Can you explain what is your main report and what is the sub reposrt?

Also:

1. Are those screen shots belong to the subreport or to the main report?
2. Why do you use the command and then link it to again to the same tables?

Beni.

Hi

Fund Management - Issues

The configurations of Fund Management have been completed in test system. When we allocate the Budget through transaction code FMBCC, the budgets have been allocated to whole year and no issues. All the related Budget Report - FMRP_RW_BUDGET is populated the current year budgets against Fund /commitment items. When we try to consume the budget through transaction FB60, we will not be able to post the document.  Got the following error

Program "RFMATGRNEP9000001 " not found

Category               ABAP Programming Error
Runtime Errors         LOAD_PROGRAM_NOT_FOUND
Except.                CX_SY_PROGRAM_NOT_FOUND
ABAP Program           SAPLABADR
Application Component  CA-GTF
Date and Time          17.07.2013 10:56:32
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|Short text                                                                                       
|    Program "RFMATGRNEP9000001 " not found.                                                      
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|What happened?                                                                                   
|    There are several possibilities:                                                             
|                                                                                                 
|    Error in the ABAP Application Program                                                        
|                                                                                                 
|    The current ABAP program "SAPLABADR" had to be terminated because it has                     
|    come across a statement that unfortunately cannot be executed.                               
|    or                                                                                           
|    Error in the SAP kernel.                                                                     
|                                                                                                 
|    The current ABAP "SAPLABADR" program had to be terminated because the                        
|    ABAP processor detected an internal system error.                                            
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|What can you do?                                                                                 
|    Note down which actions and inputs caused the error.                                         
|                                                                                                 
|                                                                                                
|    To process the problem further, contact you SAP system                                       
|    administrator.                                                                               
|                                                                                                 
|    Using Transaction ST22 for ABAP Dump Analysis, you can look                                  
|    at and manage termination messages, and you can also                                         
|    keep them for a long time.                                                                   
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|Error analysis                                                                                   
|    An exception occurred that is explained in detail below.                                     
|    The exception, which is assigned to class 'CX_SY_PROGRAM_NOT_FOUND', was not                 
|     caught in                                                                                   
|    procedure "STEP--METHOD_DRULE" "(FORM)", nor was it propagated by a RAISING                  
|     clause.                                                                                     
|    Since the caller of the procedure could not have anticipated that the                        
|    exception would occur, the current program is terminated.                                    
|    The reason for the exception is:                                                             
|    On account of a branch in the program                                                        
|    (CALL FUNCTION/DIALOG, external PERFORM, SUBMIT)                                             
|    or a transaction call, another ABAP/4 program                                                
|    is to be loaded, namely "RFMATGRNEP9000001 ".                                                
|                                                                                                 
|    However, program "RFMATGRNEP9000001 " does not exist in the library.                         
|                                                                                                 
|    Possible reasons:                                                                            
|    a) Wrong program name specified in an external PERFORM or                                    
|       SUBMIT or, when defining a new transaction, a new                                         
|       dialog module or a new function module.                                                   
|    b) Transport error                                                                           
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|How to correct the error                                                                         
|    Check the last transports to the R/3 System.                                                 
|                                                                                                 
|    Are changes currently being made to the program "SAPLABADR"?                                 
|                                                                                                 
|    Has the correct program been entered in table TSTC for Transaction "FB60 "?              
|    -                                                                                            
|                                                                                                
|                                                                                                 
|    If the error occures in a non-modified SAP program, you may be able to                       
|    find an interim solution in an SAP Note.                                                     
|    If you have access to SAP Notes, carry out a search with the following                       
|    keywords:                                                                                    
|                                                                                                 
|    "LOAD_PROGRAM_NOT_FOUND" "CX_SY_PROGRAM_NOT_FOUND"                                           
|    "SAPLABADR" or "LABADRF01"                                                                   
|    "STEP--METHOD_DRULE"                                                                         
|                                                                                                 
|    If you cannot solve the problem yourself and want to send an error                           
|    notification to SAP, include the following information:                                      
|                                                                                                 
|    1. The description of the current problem (short dump)                                       
|                                                                                                 
|       To save the description, choose "System->List->Save->Local File                           
|    (Unconverted)".                                                                              
|                                                                                                 
|    2. Corresponding system log                                                                  
|                                                                                                 
|       Display the system log by calling transaction SM21.                                       
|       Restrict the time interval to 10 minutes before and five minutes                          
|    after the short dump. Then choose "System->List->Save->Local File                            
|    (Unconverted)".                                                                              
|                                                                                                 
|    3. If the problem occurs in a problem of your own or a modified SAP                          
|    program: The source code of the program                                                      
|       In the editor, choose "Utilities->More                                                    
|    Utilities->Upload/Download->Download".                                                       
|                                                                                                 
|    4. Details about the conditions under which the error occurred or which                      
|    actions and input led to the error.                                                          
|                                                                                                 
|    The exception must either be prevented, caught within proedure                               
|    "STEP--METHOD_DRULE" "(FORM)", or its possible occurrence must be declared in                
|     the                                                                                         
|    RAISING clause of the procedure.                                                             
|    To prevent the exception, note the following:                                                
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|System environment                                                                               
|    SAP Release..... 702                                                                         
|    SAP Basis Level. 0010                                                                        
|                                                                                                 
|    Application server... "hoerp06ides"                                                          
|    Network address...... "172.16.0.36"                                                          
|    Operating system..... "Windows NT"                                                           
|    Release.............. "5.2"                                                                  
|    Hardware type........ "4x AMD64 Level"                                                       
|    Character length.... 16 Bits                                                                 
|    Pointer length....... 64 Bits                                                                
|    Work process number.. 16                                                                     
|    Shortdump setting.... "full"                                                                 
|                                                                                                 
|    Database server... "HOERP06IDES"                                                             
|    Database type..... "ORACLE"                                                                  
|    Database name..... "NEI"                                                                     
|    Database user ID.. "SAPSR3"                                                                                                                                                                   |
|    Terminal.......... "Dev-03"                                                                  
|                                                                                                 
|    Char.set.... "C"                                                                          
|                                                                                                 
|    SAP kernel....... 720                                                                        
|    created (date)... "Jul 8 2012 23:15:28"                                                      
|    create on........ "NT 5.2 3790 S x86 MS VC++ 14.00"                                          
|    Database version. "OCI_10201_SHARE, 10.2.0.2.0 "                                             
|                                                                                                 
|    Patch level. 300                                                                             
|    Patch text.. " "                                                                             
|                                                                                                 
|    Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*"              
|    SAP database version. 720                                                                    
|    Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows               
|     NT 6.0, Windows NT 6.1, Windows NT 6.2"                                                     
|                                                                                                 
|    Memory consumption                                                                           
|    Roll.... 0                                                                                   
|    EM...... 20948960                                                                            
|    Heap.... 0                                                                                   
|    Page.... 2605056                                                                             
|    MM Used. 14905600                                                                            
|    MM Free. 1850224                                                                             
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|User and Transaction                                                                             
|    Client.............. 900                                                                     
|    User................ "NATIBR"                                                                
|    Language key........ "E"                                                                     
|    Transaction......... "FB60 "                                                                 
|    Transaction ID...... "89B5EEE284BAF1A88E3500215A45D1C4"                                      
|                                                                                                 
|    EPP Whole Context ID.... "00215A45D1C41ED2BBD607E08F008E35"                                  
|    EPP Connection ID....... 00000000000000000000000000000000                                    
|    EPP Caller Counter...... 0                                                                   
|                                                                                                 
|    Program............. "SAPLABADR"                                                             
|    Screen.............. "SAPMF05A 0300"                                                         
|    Screen Line......... 98                                                                      
|    Debugger Active..... "none"                                                                  
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|Information on where terminated                                                                  
|    Termination occurred in the ABAP program "SAPLABADR" - in "STEP--METHOD_DRULE".              
|    The main program was "SAPMF05A ".                                                            
|                                                                                                 
|    In the source code you have the termination point in line 1062                               
|    of the (Include) program "LABADRF01".                                                        
|    The termination is caused because exception "CX_SY_PROGRAM_NOT_FOUND" occurred               
|     in                                                    |
|    procedure "STEP--METHOD_DRULE" "(FORM)", but it was neither handled locally nor              
|     declared in the RAISING clause of its signature.                                                                                   
|                                                         |                                                                                                 
|    The procedure is in program "SAPLABADR "; its source code begins in line                     
|    941 of the (Include program "LABADRF01 ".                                                    
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|Source Code Extract (Source code has changed)                                                    
----------------------------------------------------------------------------------------------------
|Line |SourceCde                                                                                  
----------------------------------------------------------------------------------------------------
| 1032|            e_failed valid_from                                                            
| 1033|            <value1> <value2> <value3> <value4> <value5> <value6>                          
| 1034|            l_temp                                                                         
| 1035|            delflag                                                                        
| 1036|            request_handled.                                                               
| 1037|  ELSE.                                                                                    
| 1038|    PERFORM exit--entry_from_table                                                         
| 1039|        IN PROGRAM (<strategy>-callback_report)                                            
| 1040|        IF FOUND                                                                           
| 1041|        USING x_step-param_1           "name of the table                                  
| 1042|            global-call-date                                                               
| 1043|            <source1> <source2> <source3> <source4> <source5> <source6>                    
| 1044|            <version>                                                                      
| 1045|        CHANGING                                                                           
| 1046|            e_failed valid_from                                                           
| 1047|            <value1> <value2> <value3> <value4> <value5> <value6>                          
| 1048|            <guid>                                                                         
| 1049|            delflag                                                                        
| 1050|            request_handled.                                                               
| 1051|  ENDIF.                                                                                   
| 1052|                                                                                           
| 1053|  IF request_handled IS INITIAL.                                                           
| 1054|                                                                                           
| 1055|    IF <strategy>-uses_guid_version IS INITIAL.                                            
| 1056|      PERFORM get_entry_from_table IN PROGRAM (x_step-param_2)                             
| 1057|        USING global-call-date                                                             
| 1058|              <source1> <source2> <source3> <source4> <source5> <source6>                  
| 1059|              e_failed                                                                     
| 1060|              <value1> <value2> <value3> <value4> <value5> <value6>                        
| 1061|              delflag.                                                                     
|>>>>>|    ELSE.                                                                                  
| 1063|* version and guid are used by strategy -> further params for generated                    
| 1064|* routines. guid is only used for reference purposes and not returned at                   
| 1065|* the moment                                                                               
| 1066|      PERFORM get_entry_from_table IN PROGRAM (x_step-param_2)                             
| 1067|        USING global-call-date                                                             
| 1068|              <source1> <source2> <source3> <source4> <source5> <source6>                  
| 1069|              <version>                                                                    
| 1070|        CHANGING                                                                           
| 1071|              e_failed valid_from                                                          
| 1072|              <value1> <value2> <value3> <value4> <value5> <value6>                        
| 1073|              <guid>                                                                       
| 1074|              delflag.                                                                     
| 1075|                                                                                           
| 1076|* the call-back should be notified, if any entry has been read                             
| 1077|      IF delflag  IS INITIAL AND                                                           
| 1078|         e_failed IS INITIAL.                                                              
| 1079|                                                                                           
| 1080|        PERFORM exit--entry--read                                                          
| 1081|            IN PROGRAM (<strategy>-callback_report)                                        
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|Active Calls/Events                                                                              
----------------------------------------------------------------------------------------------------
|No.   Ty.          Program                             Include                             Line  
|      Name                                                                                       
----------------------------------------------------------------------------------------------------
|   24 FORM         SAPLABADR                           LABADRF01                            1062 
|      STEP--METHOD_DRULE                                                                         
|   23 FORM         SAPLABADR                           LABADRF01                             340 
|      STEP--PROCESS                                                                              
|   22 FORM         SAPLABADR                           LABADRF01                             132 
|      STRATEGY--STEP--PROCESS                                                                    
|   21 FORM         SAPLABADR                           LABADRF01                              44 
|      STRATEGY--PROCESS                                                                          
|   20 FUNCTION     SAPLABADR                           LABADRU03                             150 
|      ABADR_DERIVE_CHARACTERISTICS                                                               
|   19 FUNCTION     SAPLFMAVC_DERI_TOOLS                LFMAVC_DERI_TOOLSU12                  100 
|      FMAVC_DERI_ACTGRP_FMUPDATE                                                                  |
|   18 METHOD       CL_FMAVC_ENTRY================CP    CL_FMAVC_ENTRY================CM006     4 
|      CL_FMAVC_ENTRY=>ACTIVITY_GROUP_GET_FOR_UPD                                                 
|   17 METHOD       CL_FMAVC_ENTRY================CP    CL_FMAVC_ENTRY================CM004   156 
|      CL_FMAVC_ENTRY=>IF_FMAVC_ENTRY~COLLECT_UPD                                                 
|   16 METHOD       CL_IM_FMAVC_DECO_ISPS=========CP    CL_IM_FMAVC_DECO_ISPS=========CM001   462
|      CL_IM_FMAVC_DECO_ISPS=>IF_EX_FMAVC_DECO~CHECK_FUNDS_FM                                     
|   15 METHOD       CL_EX_FMAVC_DECO==============CP    CL_EX_FMAVC_DECO==============CM001   159 
|      CL_EX_FMAVC_DECO=>IF_EX_FMAVC_DECO~CHECK_FUNDS_FM                                          
|   14 FUNCTION     SAPLBPFC                            LBPFCU16                               87 
|      BP_CHECK_FUNDS_FM                                                                          
|   13 FUNCTION     SAPLFMFC                            LFMFCU01                               93 
|      FM_FUNDS_CHECK                                                                             
|   12 FUNCTION     SAPLFMFC                            LFMFCU02                               57 
|      FM_FUNDS_CHECK_FI                                                                          
|   11 FORM         SAPLFMRI                            LFMRIF0S                               29 
|      CHECK_AVAIL                                                                                
|   10 FUNCTION     SAPLFMRI                            LFMRIU03                              143 
|      FM_DOCUMENT_CLOSE                                                                          
|    9 FORM         SAPLFACG                            LFACGU03                              356 
|      PROCESS_TCOMP                                                                              
|    8 FORM         SAPLFACG                            LFACGU03                              196 
|      PROCESS_PROJECT                                                                            
|    7 FUNCTION     SAPLFACG                            LFACGU03                               43 
|      FI_DOCUMENT_PROCESS                                                                        
|    6 FORM         SAPMF05A                            MF05AFF0_FCODE_BEARBEITUNG           1186 
|      FCODE_BEARBEITUNG                                                                          
|    5 FORM         SAPMF05A                            MF05AFF0_FUSSZEILE_VERARBEITEN        149 
|      FUSSZEILE_VERARBEITEN                                                                      
|    4 FORM         SAPMF05A                            MF05AFF0_FCODE_BEARBEITUNG            174 
|      FCODE_BEARBEITUNG                                                                          
|    3 FORM         SAPMF05A                            MF05AFF0_FCODE_BEARBEITUNG           3371 
|      FCODE_BEARBEITUNG                                                                          
|    2 FORM         SAPMF05A                            MF05AFF0_FUSSZEILE_VERARBEITEN        14 
|      FUSSZEILE_VERARBEITEN                                                                      
|    1 MODULE (PAI) SAPMF05A                            MF05AI00_FUSSZEILE_BEARBEITEN          46 
|      FUSSZEILE_BEARBEITEN                                                                       
----------------------------------------------------------------------------------------------------

Finallay we are not able toexecute FB60 nor PO om the test system. Not sure what exactly causes this issue. Your help would highly appreciated on this issue

Thanks & Regards

IBrahim N

Just check the documentation in INSERT and MODIFY.

INSERT dbtab

INSERT { {INTO target VALUES source }
       | {     target FROM   source } }.

Effect

The INSERT statement inserts one or more rows specified in source in the database table specified in target. The two variants with INTO and VALUES or without INTO with FROM behave identically, with the exception that you cannot specify any internal tables in source after VALUES.

System Fields

The INSERT statement sets the values of the system fields sy-subrc and sy-dbcnt.

• The INSERT statement sets sy-dbcnt to the number of rows inserted.
  
  
  

Note

• The inserted rows are finally included in the table in the next database commit. Up until this point, they can still be removed by a database rollback.
• The statement INSERT sets a database lock until the next database commit or rollback. If used incorrectly, this can lead to a deadlock. 
• The number of rows that can be inserted in the tables of a database within a database LUW is limited, since a database system can only manage a limited amount of locks and data in the rollback area.
  
  

Example, INSERT INTO ztable VALUES wa_ztable

MODIFY dbtab

MODIFY target FROM source.

Effect

The MODIFY statement inserts one or several lines specified in source in the database table specified in target, or overwrites existing lines.

System fields

The MODIFY statement sets the values of the sy-subrc and sy-dbcnt system fields.

The MODIFY statement sets sy-dbcnt to the number of processed lines.

Note

The changes are finally transferred to the database table with the next database commit. Up to that point, they can be reversed with a database rollback.

• The MODIFY statement sets a database lock until the next database commit or database rollback; incorrect usage can result in a deadlock .
• The number of rows that can be inserted into or changed in the tables of a database within a database LUW is restricted database-specifically by the fact that a database system can only manage a limited amount of locks and data in the rollback area.
  
  EXAMPLE : MODIFY ztable FROM wa_ztable.

UPDATE dbtab

Syntax

UPDATE targetsource.

Effect:

The statement UPDATE changes the content of one or more lines of the database table specified in target. The entries in source determine which columns of which lines are changed, and how they are changed.

System fields

The statement UPDATE sets the values of the system fields sy-subrc and sy-dbcnt.

The statement UPDATE sets sy-dbcnt to the number of changed lines.

Note

The changes are definitively copied to the database with the next database commit. Until that point, they can still be undone using a database rollback

• The statement UPDATE sets a database lock up to the next database commit or rollback, which may lead to a deadlock if used incorrectly.
• For the specific database, the number of rows that can be changed within a database LUW in the database table is restricted by the fact that a database system can only manage a certain amount of data in the rollback area and from locks.
  
  

Fund Management - Issues

We are implementing Fund Management in testing system, the configurations have been completed.
When we allocate the Budget through transaction code FMBCC, the budgets have been allocated to whole year and no issues.
All the related Budget Report - FMRP_RW_BUDGET is populated the current year budgets against Fund /commitment items.
When we try to consume the budget through transaction FB60, we will not be able to post the document.
When we simulate the document no problem but when post got the following error

Category               ABAP Programming Error
Runtime Errors         LOAD_PROGRAM_NOT_FOUND
Except.                CX_SY_PROGRAM_NOT_FOUND
ABAP Program           SAPLABADR
Application Component  CA-GTF
Date and Time          17.07.2013 10:56:32
----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------
|Short text                                                                                        |
|    Program "RFMATGRNEP9000001 " not found.                                                       |
----------------------------------------------------------------------------------------------------

Hi All,

In CBIH82 - Entry Type field, i am able to change the "Entry type" when the status is in create/In Process status.

Now, i am not able to change the "Entry type" field and my end user is facing this problem for changing it after entering and saving.

I want to enable it again to change the entry type whenever required unless the status change to closed.

Please provide your solutions.

Regards

Hari Prasath

Hi Arora,

Are you using BW 7.3?

Attributes and texts always reside outside the cube. Don't think that Attributes and texts are in your cube. Those always reside in the master data characteristics which can be re-used in any other infoproviders. So you can simply map the main characteristic from your cube to DSO.

Regards,

Suman

Hi,

1. ya, i already checked debugged the job in ecc side.i checked the FM ,till e_t_data the data is passing correctly.

I created a dummy FM datasource and its working fine. If it is going to authourisation issue then it should be the case to all the datasource.

Please correct me if im wrong.

You say dummy FM is working fine. Then drop the old Fm and create the DS by based on this copied FM. Your problem will be resolved.

You need not to investigate further on the issue.

Dear Rakesh,

IF employee transferred on 15th july there is a possibility of getting reporting error after 15th because you may assigned new position which is no where relevant to old reporting structure, as per your scenario what you have mentioned belongs to old reporting structure(suppose 01 April to 5th April 2013) which may not changed.

Please check the Info type 1  of the employee to whom you had transferred and check the reporting structure or else please share the screen shot of the error so that we can resolve.

Regards,

Dora

we are using material ledger, so variance category and actual costing is transfered to CO-PA, is there any way to reconcil between co-PA and PC, if I see in period 5, my input price varaince value field is updated with 3000 USD, how will i know it is correct or not?

also in co-pa, period 5, single level price variance value field is 2000 USD, how will i know it is correct or not? any reconcillation tool can be used? thanks

Hello,

Read the table based on lead selection index of the selected row of the table.

For example,Check the following link,

http://www.sapdev.co.uk/sap-webapps/sap-webdynpro/table-dropdown.htm

Thanks

Katrice

Hi,

I see your query is recent (17 May 2013). Did you solve the problem as we have the same issue?

If a user with ADMIN rights executes a certain BPC input template it executes correctly but if a user with specific data member access runs the same report it fails with the  UJO_READ_EXCEPTION_000. However, if that same user who got the error selects fewer members for the report it works again.

We applied the RSADMIN parameter but this has not corrected the problem.

We have not applied the note 1666816. We are on kernel 7.20 ext uc patch level 117, AIX.

Not sure now if this is a pure PARSER error which will be fixed by the kernel update or another problem related perhaps to S_RFC_ADM issue for authorising member nodes.

Would help if someone can clarify.

Regards,

Noel.

Hi All,

  I have created a 'Z' Genil model. I was able to add, modify & delete an entry for this 'Z' Genil model using GENIL_BOL_BROWSER transaction code. I have created a UI component and implemented this Z model but using my UI component i was not able to create any new entries

  The problem i face is, i am not able to get the values what i have entered in my UI screen. If i get those value then i can save it. But if i hard code soome entries in my UI method it saves correctly. So now the problem is getting my UI screen values into my event handler method. How to achieve this? Any clues/suggestions will be very much helpful

Thanks & Regards

Gokul Ragunathan