NullPointerException for hidden field in table with col of type DBSequence

All,
I implemented the use of the DBSequence type on my entity to automatically populate my employee_id on the hr.employees table on insert. In jheadstart, I had to manually change the EmployeeId attribute java type to DBSequence to get my generated pages working. When I try to use the generated form to insert a new employee, the insert works(employeeid is populated w/a negative val and then replaced w/the next seq number) if the column is displayed in the table layout. However, when I change the Display type of the sequence field to "hidden," when I try to add an employee I receive the following error:
- JBO-27008: Attribute set for EmployeeId in view object EmployeesView1 failed
- java.lang.NullPointerException
Has anyone encountered this before? This same error occurs if the table using the hidden dbsequence field is in the table layout as a stacked detail group of another group such as departments. If you click on one of the detail tabs you will receive the same error message.
Is the use of the DBSequence type supported by jheadstart? Is this easily remedied?
Thanks,
Paul
ADF Business Components 10.1.3.42.70
JHeadstart 10.1.3.3.75
Edited by: p.mon on Sep 3, 2008 2:31 PM

Steven,
The sequence field is just being used as a surrogate key and we don't want to display it to the user. However, since we're using the default display value property to populate it, I assumed it needed to be on the entry form for inserts in order to fetch the next value. Please let me know if my assumption was wrong.
We've already found a workaround by reverting the column back to a number data type and using a managed bean to populate the field w/the same sequence.
Thanks,
Paul

Similar Messages

How to provide F4 help for a field in table control

Hi Friends,
I have requirement like below.
1.Create one custom transaction code with header and item information.
2.In item level, we will be designed table control to enter/display the data.
3.Table controls first field will be material number and next DOT number (Material may have many DOT numbers) and so on.
4.First user will enter material number in the table controls first rows first field and go to DOT number field.
5.DOT number has drop down option. If user selects drop down box of DOT number, he gets all the DOT numbers available in database. User selects one DOT number and double clicks on it then it will be populated in DOT number field box.
But for point number 5, business wants like when ever user enters material number in table control first field then select DOT numbers drop down then they want to see the particular materials DOT numbers only in the drop down list for selection. Not all DOT numbers available in data base. Same thing should happen for all item lines in table control.
Please see below example.
Assume data base table has 10 DOT numbers. But material number has only 2 DOT numbers. When ever user enters material number in item level table control and selects DOT numbers drop down then it should show only 2 DOT numbers which are related to particular material number. Not all 10 DOT numbers.
Could you please suggest me, how can we achieve this?

Hello,
Check this :-
For POV
Input Help in Dialog Modules
You can call dialog modules in the POV event using the event keyword PROCESS ON VALUE-REQUEST.
PROCESS ON VALUE-REQUEST.
FIELD <f> MODULE <mod>.
After the PROCESS ON VALUE-REQUEST statement, you can only use the MODULE statement together with the FIELD statement. When the user chooses F4 for a field <f>, the system calls the module <mod> belonging to the FIELD <f> statement. If there is more than one FIELD statement for the same field <f>, only the first is executed. The module <mod> is defined in the ABAP program like a normal PAI module. However, the contents of the screen field <f> are not available, since it is not transported by the FIELD statement during the PROCESS ON HELP-REQUEST event. You can now program your own value lists in the module. However, this procedure is only recommended if it really is not possible to use a search help. Defining search helps is much easier than PROCESS ON VALUE-REQUEST, since the system takes over some of the standard operations, such as getting field contents from the screen. It also ensures that the F4 help has a uniform look and feel throughout the system. Furthermore, it means that you do not have to reassign input help to fields on each screen.
Despite the introduction of search helps (and search help exits), there are still cases in which you need to use parts of the standard F4 functions directly. In this case, there are some standard function modules that you can use in the POV event. They support search helps, as well as all other kinds of input help, and are responsible for data transport between the screen and the input help. These all have the prefix F4IF_. The most important are:
F4IF_FIELD_VALUE_REQUEST
Calls the input help of the ABAP Dictionary dynamically. You can pass the component names of a structure or database table of the ABAP Dictionary to the function module in the import parameters TABNAME and FIELDNAME. The function module starts the ABAP Dictionary input help for this component. All of the relevant screen fields are read. If you specify the import parameters DYNPPROG, DYNPNR, and DYNPROFIELD, the users selection is returned to the corresponding field on the screen. If you specify the table parameter RETURN_TAB, the selection is returned into the table instead.
F4IF_INT_TABLE_VALUE_REQUEST
This function module displays a value list that you created in an ABAP program. The value list is passed to the function module as the table parameter VALUE_TAB. If you specify the import parameters DYNPPROG, DYNPNR, and DYNPROFIELD, the users selection is returned to the corresponding field on the screen. If you specify the table parameter RETURN_TAB, the selection is returned into the table instead.
There are also two function modules - DYNP_VALUES_READ and DYNP_VALUES_UPDATE - that can read the values of screen fields and return values to them during the POV event. For further information, refer to the relevant function module documentation.
Input help in dialog modules
REPORT DEMO_DYNPRO_F4_HELP_MODULE.
TYPES: BEGIN OF VALUES,
CARRID TYPE SPFLI-CARRID,
CONNID TYPE SPFLI-CONNID,
END OF VALUES.
DATA: CARRIER(3) TYPE C,
CONNECTION(4) TYPE C.
DATA: PROGNAME LIKE SY-REPID,
DYNNUM LIKE SY-DYNNR,
DYNPRO_VALUES TYPE TABLE OF DYNPREAD,
FIELD_VALUE LIKE LINE OF DYNPRO_VALUES,
VALUES_TAB TYPE TABLE OF VALUES.
CALL SCREEN 100.
MODULE INIT OUTPUT.
PROGNAME = SY-REPID.
DYNNUM = SY-DYNNR.
CLEAR: FIELD_VALUE, DYNPRO_VALUES.
FIELD_VALUE-FIELDNAME = 'CARRIER'.
APPEND FIELD_VALUE TO DYNPRO_VALUES.
ENDMODULE.
MODULE CANCEL INPUT.
LEAVE PROGRAM.
ENDMODULE.
MODULE VALUE_CARRIER INPUT.
CALL FUNCTION 'F4IF_FIELD_VALUE_REQUEST'
EXPORTING
TABNAME = 'DEMOF4HELP'
FIELDNAME = 'CARRIER1'
DYNPPROG = PROGNAME
DYNPNR = DYNNUM
DYNPROFIELD = 'CARRIER'.
ENDMODULE.
MODULE VALUE_CONNECTION INPUT.
CALL FUNCTION 'DYNP_VALUES_READ'
EXPORTING
DYNAME = PROGNAME
DYNUMB = DYNNUM
TRANSLATE_TO_UPPER = 'X'
TABLES
DYNPFIELDS = DYNPRO_VALUES.
READ TABLE DYNPRO_VALUES INDEX 1 INTO FIELD_VALUE.
SELECT CARRID CONNID
FROM SPFLI
INTO CORRESPONDING FIELDS OF TABLE VALUES_TAB
WHERE CARRID = FIELD_VALUE-FIELDVALUE.
CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
EXPORTING
RETFIELD = 'CONNID'
DYNPPROG = PROGNAME
DYNPNR = DYNNUM
DYNPROFIELD = 'CONNECTION'
VALUE_ORG = 'S'
TABLES
VALUE_TAB = VALUES_TAB.
ENDMODULE.
The next screen (statically defined) for screen 100 is itself. It has the following layout:
The input fields have been adopted from the program fields CARRIER and CONNECTION. The pushbutton has the function code CANCEL with function type E.
The screen flow logic is as follows:
PROCESS BEFORE OUTPUT.
MODULE INIT.
PROCESS AFTER INPUT.
MODULE CANCEL AT EXIT-COMMAND.
PROCESS ON VALUE-REQUEST.
FIELD CARRIER MODULE VALUE_CARRIER.
FIELD CONNECTION MODULE VALUE_CONNECTION.
When the user chooses input help for the individual fields, the following is displayed:
For the Airline field, the POV module VALUE_CARRIER is called. The function module F4IF_FIELD_VALUE_REQUEST displays the input help for the component CARRIER1 of the structure DEMOF4HELP from the ABAP Dictionary, namely the search help DEMOF4DE. The users selection is returned to the screen field CARRIER.
For the Flight number field, the POV module VALUE_CONNECTION is called. The function module DYNP_VALUE_READ transports the value of the screen field CARRIER into the program. The program then reads the corresponding values from the database table SPFLI into the internal table VALUES_TAB using a SELECT statement, and passes the internal table to F4IF_INT_TABLE_VALUE_REQUEST. This displays the internal table as input help, and places the users selection into the screen field CONNECTION.
For POH------------
Field Help
There are three ways of displaying field help for screen elements:
Data Element Documentation
If you place a field on the screen in the Screen Painter by copying a ABAP Dictionary field, the corresponding data element documentation from the ABAP Dictionary is automatically displayed when the user chooses field help (as long as the help has not been overridden in the screen flow logic).
For further information about creating data element documentation, refer to data elements.
Data Element Supplement Documentation
If the data element documentation is insufficient, you can expand it by writing a data element supplement
Data element supplement documentation contains the heading Definition, as well as the following others:
Use
Procedure
Examples
Dependencies
To create data element supplement documentation for a screen, choose Goto ® Documentation ® DE supplement doc. from the element list of the screen. A dialog box appears in which the system proposes a number as the identified for the data element supplement. You can then enter help texts for the above headings using the SAPscript editor.
Data element supplement documentation created in this way is program- and screen-specific. Any data element supplement documentation created in the ABAP Dictionary with the same number is overridden by the screen-specific documentation. You can link existing data element supplement documentation created in the ABAP Dictionary with a screen field by using the table THLPF. To do this, crate a new row in THLPF containing the following data: Program name, screen name, field name, and number of the data element supplement documentation.
To display data element supplement documentation, you must code the following screen flow logic in the POH event:
PROCESS ON HELP-REQUEST.
FIELD <f> [MODULE <mod>] WITH <num>.
After PROCESS ON HELP-REQUEST, you can only use FIELD statements. If there is no PROCESS ON HELP-REQUEST keyword in the flow logic of the screen, the data element documentation for the current field, or no help at all is displayed when the user chooses F1. Otherwise, the next FIELD statement containing the current field <f> is executed.
If there is screen-specific data element supplement documentation for the field <f>, you can display it by specifying its number <num>. The number <num> can be a literal or a variable. The variable must be declared and filled in the corresponding ABAP program.
You can fill the variables, for example, by calling the module <mod> before the help is displayed. However, the FIELD statement does not transport the contents of the screen field <f> to the ABAP program in the PROCESS ON HELP-REQUEST event.
For further information about data element supplement documentation, refer to Data Element Supplements.
Calling Help Texts from Dialog Modules
If data element supplement documentation is insufficient for your requirements, or you want to display help for program fields that you have not copied from the ABAP Dictionary, you can call dialog modules in the POH event:
PROCESS ON HELP-REQUEST.
FIELD <f> MODULE <mod>.
After the PROCESS ON HELP-REQUEST statement, you can only use the MODULE statement together with the FIELD statement. When the user chooses F1 for a field <f>, the system calls the module <mod> belonging to the FIELD <f> statement. If there is more than one FIELD statement for the same field <f>, only the first is executed. However, the contents of the screen field <f> are not available in the module <mod>, since it is not transported by the FIELD statement during the PROCESS ON HELP-REQUEST event. The field help should not be dependent on the user input.
The module <mod> is defined in the ABAP program like a normal PAI module. The processing logic of the module must ensure that adequate help is displayed for the field in question. Instead of calling an extra screen with text fields, you should use one of the following function modules to display a suitable SAPscript document:
HELP_OBJECT_SHOW_FOR_FIELD
This function module displays the data element documentation for components of any structure or database table from the ABAP Dictionary. You pass the name of the component and structure or table to the import parameters FIELD and TABLE.
HELP_OBJECT_SHOW
Use this function module to display any SAPscript document. You must pass the document class (for example, TX for general texts, DE for data element documentation) and the name of the document to the import parameters DOKCLASS and DOKNAME. For technical reasons, you must also pass an empty internal table with the line type TLINE to the tables parameter of the function module.
For further information about how to create SAPscript documents, refer to the Documentation of System Objects documentation.
Field help on screens.
REPORT DEMO_DYNPRO_F1_HELP.
DATA: TEXT(30),
VAR(4),
INT TYPE I,
LINKS TYPE TABLE OF TLINE,
FIELD3, FIELD4.
TABLES DEMOF1HELP.
TEXT = TEXT-001.
CALL SCREEN 100.
MODULE CANCEL INPUT.
LEAVE PROGRAM.
ENDMODULE.
MODULE F1_HELP_FIELD2 INPUT.
INT = INT + 1.
CASE INT.
WHEN 1.
VAR = '0100'.
WHEN 2.
VAR = '0200'.
INT = 0.
ENDCASE.
ENDMODULE.
MODULE F1_HELP_FIELD3 INPUT.
CALL FUNCTION 'HELP_OBJECT_SHOW_FOR_FIELD'
EXPORTING
DOKLANGU = SY-LANGU
DOKTITLE = TEXT-002
CALLED_FOR_TAB = 'DEMOF1HELP'
CALLED_FOR_FIELD = 'FIELD1'.
ENDMODULE.
MODULE F1_HELP_FIELD4 INPUT.
CALL FUNCTION 'HELP_OBJECT_SHOW'
EXPORTING
DOKCLASS = 'TX'
DOKLANGU = SY-LANGU
DOKNAME = 'DEMO_FOR_F1_HELP'
DOKTITLE = TEXT-003
TABLES
LINKS = LINKS.
ENDMODULE.
The next screen (statically defined) for screen 100 is 100. It has the following layout:
The screen fields DEMOf1HELP-FIELD1 and DEMOF1HELP-FIELD2 from the ABAP Dictionary and the program fields FIELD3 and FIELD4 are assigned to the input fields. The pushbutton has the function code CANCEL with function type E.
The screen flow logic is as follows:
PROCESS BEFORE OUTPUT.
PROCESS AFTER INPUT.
MODULE CANCEL AT EXIT-COMMAND.
PROCESS ON HELP-REQUEST.
FIELD DEMOF1HELP-FIELD2 MODULE F1_HELP_FIELD2 WITH VAR.
FIELD FIELD3 MODULE F1_HELP_FIELD3.
FIELD FIELD4 MODULE F1_HELP_FIELD4.
The components FIELD1 and FIELD2 of structure DEMOF1HELP both refer to the data element DEMOF1TYPE. This data element is documented, and also has two supplements with numbers 0100 and 0200.
The following field help is displayed:
When the user chooses F1 on the input field for DEMOF1HELP-FIELD1, the data element documentation for DEMOF1TYPE is displayed, since the field does not occur in the PROCESS ON HELP-REQUEST event.
If the user chooses F1 repeatedly for the input field DEMOF1HELP-FIELD2, the data element documentation is displayed, along with the supplement documentation for either 0100 or 0200 alternately. The variable VAR is filled in the dialog module F1_HELP_FIELD2.
When the user chooses F1 on the input field for FIELD3, the data element documentation for DEMOF1TYPE is displayed, since this is called in the dialog module F1_HELP_FIELD3 by the function module HELP_OBJECT_SHOW_FOR_FIELD.
When the user chooses F1 on the input field for FIELD4, the SAPscript documentation DEMO_FOR_F1_HELP is displayed, since this is called in the dialog module F1_HELP_FIELD4 by the function module HELP_OBJECT.
Regards,
Deepu.K

How to create Search Help for a field in Table control !!

Hello Friends,
              I like to know - How to create Search Help for a field in Table control. Is it possible, if it is please share ur knowledge, I wud be happy if U provide some source code example for this.
Thanks,
Senthil

Check the sample code:
*& Include           ZSRO_MPRN_SEARCH                                 *
MODULE PSTLZ_F4 INPUT
MODULE pstlz_f4 INPUT.
reading post code
DATA: stepl TYPE systepl,
        stepl_index TYPE systepl.
CLEAR: stepl, stepl_index.
CLEAR:   lt_returntab,lt_dynpfields,i_mprn1.
REFRESH: lt_returntab,lt_dynpfields,i_mprn1.
lt_dynpfields-fieldname = 'I_MPRN-POST_CODE'.
lt_dynpfields-stepl     = stepl.
APPEND lt_dynpfields. CLEAR lt_dynpfields.
CALL FUNCTION 'DYNP_VALUES_READ'
    EXPORTING
      dyname               = sy-repid
      dynumb               = sy-dynnr
      translate_to_upper   = c_x
      determine_loop_index = c_x
    TABLES
      dynpfields           = lt_dynpfields
    EXCEPTIONS
      invalid_abapworkarea = 1
      invalid_dynprofield = 2
      invalid_dynproname   = 3
      invalid_dynpronummer = 4
      invalid_request      = 5
      no_fielddescription = 6
      invalid_parameter    = 7
      undefind_error       = 8
      double_conversion    = 9
      stepl_not_found      = 10
      OTHERS               = 11.
IF sy-subrc EQ 0.
    READ TABLE lt_dynpfields INDEX 1.
ENDIF.
ws_outcode = lt_dynpfields-fieldvalue.
stepl_index = lt_dynpfields-stepl.
REPLACE '*' WITH ' ' INTO lt_dynpfields-fieldvalue.
IF NOT lt_dynpfields-fieldvalue IS INITIAL.
    MOVE lt_dynpfields-fieldvalue TO ws_outcode.
    ws_len = STRLEN( lt_dynpfields-fieldvalue ).
    IF ws_len GE 7.
      ws_len = ws_len - 3.
     ws_icode = ws_code+ws_len(3).
      lt_dynpfields-fieldvalue = lt_dynpfields-fieldvalue+0(ws_len).
      CONCATENATE lt_dynpfields-fieldvalue '%'
          INTO ws_outcode.
      CONDENSE lt_dynpfields-fieldvalue.
   REPLACE ws_icode WITH ' ' INTO lt_dynpfields-fieldvalue.
    ELSE.
      CONCATENATE lt_dynpfields-fieldvalue+0(4) '%'
        INTO ws_outcode.
    ENDIF.
   ws_ocode = ws_code+0(3).
ENDIF.
reading MPRN
CLEAR:   lt_returntab,lt_dnpfields,i_mprn1.
REFRESH: lt_returntab,lt_dnpfields,i_mprn1.
lt_dnpfields-fieldname = 'I_MPRN-MPRN'.
lt_dnpfields-stepl     = stepl_index.
APPEND lt_dnpfields. CLEAR lt_dnpfields.
CALL FUNCTION 'DYNP_VALUES_READ'
    EXPORTING
      dyname               = sy-repid
      dynumb               = sy-dynnr
      translate_to_upper   = 'X'
    TABLES
      dynpfields           = lt_dnpfields
    EXCEPTIONS
      invalid_abapworkarea = 1
      invalid_dynprofield = 2
      invalid_dynproname   = 3
      invalid_dynpronummer = 4
      invalid_request      = 5
      no_fielddescription = 6
      invalid_parameter    = 7
      undefind_error       = 8
      double_conversion    = 9
      stepl_not_found      = 10
      OTHERS               = 11.
IF sy-subrc EQ 0.
    READ TABLE lt_dnpfields INDEX 1.
ENDIF.
MPRN blank and Post code exist
IF lt_dnpfields-fieldvalue IS INITIAL.
    IF NOT lt_dynpfields-fieldvalue IS INITIAL.
      SELECT mprn ser_num sub_bud bud_name del_pt_alias
             bud_num dep_street prin_street dbl_dep_street
             dep_locty post_town county outcode incode
             lg_site_ind file_date FROM zspa_mprn INTO
             CORRESPONDING FIELDS OF TABLE i_mprn1
             WHERE outcode LIKE ws_outcode.
    ELSE.
MPRN blank and Post code blank
      SELECT mprn ser_num sub_bud bud_name del_pt_alias
             bud_num dep_street prin_street dbl_dep_street
             dep_locty post_town county outcode incode
             lg_site_ind file_date FROM zspa_mprn INTO
             CORRESPONDING FIELDS OF TABLE i_mprn1.
    ENDIF.
ELSE.
MPRN exist and Post code exist
    IF NOT lt_dynpfields-fieldvalue IS INITIAL.
      SELECT mprn ser_num sub_bud bud_name del_pt_alias
             bud_num dep_street prin_street dbl_dep_street
             dep_locty post_town county outcode incode
             lg_site_ind file_date FROM zspa_mprn INTO
             CORRESPONDING FIELDS OF TABLE i_mprn1
             WHERE outcode LIKE ws_outcode AND
                   mprn EQ lt_dnpfields-fieldvalue.
    ELSE.
MPRN exist and Post code blank
      SELECT mprn ser_num sub_bud bud_name del_pt_alias
             bud_num dep_street prin_street dbl_dep_street
             dep_locty post_town county outcode incode
             lg_site_ind file_date FROM zspa_mprn INTO
             CORRESPONDING FIELDS OF TABLE i_mprn1
             WHERE mprn EQ lt_dnpfields-fieldvalue.
    ENDIF.
ENDIF.
CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
    EXPORTING
      retfield        = 'MPRN'
      dynpprog        = sy-repid
      dynpnr          = sy-dynnr
      window_title    = 'Select MPRN'
      value_org       = 'S'
    TABLES
      value_tab       = i_mprn1 "lt_mprn
      return_tab      = lt_returntab
    EXCEPTIONS
      parameter_error = 1
      no_values_found = 2
      OTHERS          = 3.
IF sy-subrc EQ 0.
    READ TABLE lt_returntab INDEX 1.
    READ TABLE i_mprn1 WITH KEY mprn = lt_returntab-fieldval.
    IF sy-subrc EQ 0.
Updating post code
      CONCATENATE i_mprn1-outcode i_mprn1-incode
                    INTO ws_postcode
                         SEPARATED BY space.
      MOVE ws_postcode TO i_mprn-post_code.
      CLEAR   : i_dnpfld,
                ws_dynpfld.
      REFRESH : i_dnpfld.
      ws_dyname   = 'ZSRO_MASTER_DATA'.
      ws_dynumb   = '0301'.
      ws_dynpfld-fieldname ='I_MPRN-POST_CODE'.
      ws_dynpfld-fieldvalue = ws_postcode .
      ws_dynpfld-stepl      = stepl_index.
      APPEND ws_dynpfld TO i_dnpfld.
      CALL FUNCTION 'DYNP_VALUES_UPDATE'
        EXPORTING
          dyname               = ws_dyname
          dynumb               = ws_dynumb
        TABLES
          dynpfields           = i_dnpfld
        EXCEPTIONS
          invalid_abapworkarea = 1
          invalid_dynprofield = 2
          invalid_dynproname   = 3
          invalid_dynpronummer = 4
          invalid_request      = 5
          no_fielddescription = 6
          undefind_error       = 7
          OTHERS               = 8.
      IF sy-subrc <> 0.
      ENDIF.
Updating MPRN
      MOVE i_mprn1-mprn TO i_mprn-mprn.
      CLEAR   : i_dnpfld,
                ws_dynpfld.
      REFRESH : i_dnpfld.
      ws_dyname   = 'ZSRO_MASTER_DATA'.
      ws_dynumb   = '0301'.
      ws_dynpfld-fieldname ='I_MPRN-MPRN'.
      ws_dynpfld-fieldvalue = i_mprn1-mprn .
      ws_dynpfld-stepl      = stepl_index.
      APPEND ws_dynpfld TO i_dnpfld.
      CALL FUNCTION 'DYNP_VALUES_UPDATE'
        EXPORTING
          dyname               = ws_dyname
          dynumb               = ws_dynumb
        TABLES
          dynpfields           = i_dnpfld
        EXCEPTIONS
          invalid_abapworkarea = 1
          invalid_dynprofield = 2
          invalid_dynproname   = 3
          invalid_dynpronummer = 4
          invalid_request      = 5
          no_fielddescription = 6
          undefind_error       = 7
          OTHERS               = 8.
      IF sy-subrc <> 0.
      ENDIF.
    ENDIF.
ELSEIF sy-subrc EQ 2.
    MESSAGE s005(zspa) WITH ws_postcode .
ENDIF.
ENDMODULE.                    "PSTLZ_F4 INPUT
MODULE MPRN_F4 INPUT
MODULE mprn_f4 INPUT.
reading post code
DATA: stepl TYPE systepl,
       stepl_index TYPE systepl.
CLEAR: stepl, stepl_index.
CLEAR:   lt_returntab,lt_dynpfields,i_mprn1.
REFRESH: lt_returntab,lt_dynpfields,i_mprn1.
lt_dynpfields-fieldname = 'I_MPRN-POST_CODE'.
lt_dynpfields-stepl     = stepl.
APPEND lt_dynpfields. CLEAR lt_dynpfields.
CALL FUNCTION 'DYNP_VALUES_READ'
    EXPORTING
      dyname               = sy-repid
      dynumb               = sy-dynnr
      translate_to_upper   = c_x
      determine_loop_index = c_x
    TABLES
      dynpfields           = lt_dynpfields
    EXCEPTIONS
      invalid_abapworkarea = 1
      invalid_dynprofield = 2
      invalid_dynproname   = 3
      invalid_dynpronummer = 4
      invalid_request      = 5
      no_fielddescription = 6
      invalid_parameter    = 7
      undefind_error       = 8
      double_conversion    = 9
      stepl_not_found      = 10
      OTHERS               = 11.
IF sy-subrc EQ 0.
    READ TABLE lt_dynpfields INDEX 1.
ENDIF.
ws_outcode = lt_dynpfields-fieldvalue.
stepl_index = lt_dynpfields-stepl.
REPLACE '*' WITH ' ' INTO lt_dynpfields-fieldvalue.
IF NOT lt_dynpfields-fieldvalue IS INITIAL.
    MOVE lt_dynpfields-fieldvalue TO ws_outcode.
    ws_len = STRLEN( lt_dynpfields-fieldvalue ).
    IF ws_len GE 7.
      ws_len = ws_len - 3.
     ws_icode = ws_code+ws_len(3).
      lt_dynpfields-fieldvalue = lt_dynpfields-fieldvalue+0(ws_len).
      CONCATENATE lt_dynpfields-fieldvalue '%'
          INTO ws_outcode.
      CONDENSE lt_dynpfields-fieldvalue.
   REPLACE ws_icode WITH ' ' INTO lt_dynpfields-fieldvalue.
    ELSE.
      CONCATENATE lt_dynpfields-fieldvalue+0(4) '%'
        INTO ws_outcode.
    ENDIF.
   ws_ocode = ws_code+0(3).
ENDIF.
reading MPRN
CLEAR:   lt_returntab,lt_dnpfields,i_mprn1.
REFRESH: lt_returntab,lt_dnpfields,i_mprn1.
lt_dnpfields-fieldname = 'I_MPRN-MPRN'.
lt_dnpfields-stepl     = stepl_index.
APPEND lt_dnpfields. CLEAR lt_dnpfields.
CALL FUNCTION 'DYNP_VALUES_READ'
    EXPORTING
      dyname               = sy-repid
      dynumb               = sy-dynnr
      translate_to_upper   = 'X'
    TABLES
      dynpfields           = lt_dnpfields
    EXCEPTIONS
      invalid_abapworkarea = 1
      invalid_dynprofield = 2
      invalid_dynproname   = 3
      invalid_dynpronummer = 4
      invalid_request      = 5
      no_fielddescription = 6
      invalid_parameter    = 7
      undefind_error       = 8
      double_conversion    = 9
      stepl_not_found      = 10
      OTHERS               = 11.
IF sy-subrc EQ 0.
    READ TABLE lt_dnpfields INDEX 1.
ENDIF.
MPRN blank and Post code exist
IF lt_dnpfields-fieldvalue IS INITIAL.
    IF NOT lt_dynpfields-fieldvalue IS INITIAL.
      SELECT mprn ser_num sub_bud bud_name del_pt_alias
             bud_num dep_street prin_street dbl_dep_street
             dep_locty post_town county outcode incode
             lg_site_ind file_date FROM zspa_mprn INTO
             CORRESPONDING FIELDS OF TABLE i_mprn1
             WHERE outcode LIKE ws_outcode.
    ELSE.
MPRN blank and Post code blank
      SELECT mprn ser_num sub_bud bud_name del_pt_alias
             bud_num dep_street prin_street dbl_dep_street
             dep_locty post_town county outcode incode
             lg_site_ind file_date FROM zspa_mprn INTO
             CORRESPONDING FIELDS OF TABLE i_mprn1.
    ENDIF.
ELSE.
MPRN exist and Post code exist
    IF NOT lt_dynpfields-fieldvalue IS INITIAL.
      SELECT mprn ser_num sub_bud bud_name del_pt_alias
             bud_num dep_street prin_street dbl_dep_street
             dep_locty post_town county outcode incode
             lg_site_ind file_date FROM zspa_mprn INTO
             CORRESPONDING FIELDS OF TABLE i_mprn1
             WHERE outcode LIKE ws_outcode AND
                   mprn EQ lt_dnpfields-fieldvalue.
    ELSE.
MPRN exist and Post code blank
      SELECT mprn ser_num sub_bud bud_name del_pt_alias
             bud_num dep_street prin_street dbl_dep_street
             dep_locty post_town county outcode incode
             lg_site_ind file_date FROM zspa_mprn INTO
             CORRESPONDING FIELDS OF TABLE i_mprn1
             WHERE mprn EQ lt_dnpfields-fieldvalue.
    ENDIF.
ENDIF.
CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
    EXPORTING
      retfield        = 'MPRN'
      dynpprog        = sy-repid
      dynpnr          = sy-dynnr
      window_title    = 'Select MPRN'
      value_org       = 'S'
    TABLES
      value_tab       = i_mprn1 "lt_mprn
      return_tab      = lt_returntab
    EXCEPTIONS
      parameter_error = 1
      no_values_found = 2
      OTHERS          = 3.
IF sy-subrc EQ 0.
    READ TABLE lt_returntab INDEX 1.
    READ TABLE i_mprn1 WITH KEY mprn = lt_returntab-fieldval.
    IF sy-subrc EQ 0.
Updating MPRN
      MOVE i_mprn1-mprn TO i_mprn-mprn.
      CLEAR   : i_dnpfld,
                ws_dynpfld.
      REFRESH : i_dnpfld.
      ws_dyname   = 'ZSRO_MASTER_DATA'.
      ws_dynumb   = '0301'.
      ws_dynpfld-fieldname ='I_MPRN-MPRN'.
      ws_dynpfld-fieldvalue = i_mprn1-mprn .
      ws_dynpfld-stepl      = stepl_index.
      APPEND ws_dynpfld TO i_dnpfld.
**code changed by laxman 10.08.2005
     ws_dynpfld-stepl = mprn-current_line.
**code changed by laxman 10.08.2005
      CALL FUNCTION 'DYNP_VALUES_UPDATE'
        EXPORTING
          dyname               = ws_dyname
          dynumb               = ws_dynumb
        TABLES
          dynpfields           = i_dnpfld
        EXCEPTIONS
          invalid_abapworkarea = 1
          invalid_dynprofield = 2
          invalid_dynproname   = 3
          invalid_dynpronummer = 4
          invalid_request      = 5
          no_fielddescription = 6
          undefind_error       = 7
          OTHERS               = 8.
      IF sy-subrc <> 0.
      ENDIF.
Updating post code
      CONCATENATE i_mprn1-outcode i_mprn1-incode
                    INTO ws_postcode
                         SEPARATED BY space.
      MOVE ws_postcode TO i_mprn-post_code.
      CLEAR   : i_dnpfld,
                ws_dynpfld.
      REFRESH : i_dnpfld.
      ws_dyname   = 'ZSRO_MASTER_DATA'.
      ws_dynumb   = '0301'.
      ws_dynpfld-fieldname ='I_MPRN-POST_CODE'.
      ws_dynpfld-fieldvalue = ws_postcode .
      ws_dynpfld-stepl      = stepl_index.
      APPEND ws_dynpfld TO i_dnpfld.
**code changed by laxman 10.08.2005
     break gblap0.
     ws_dynpfld-stepl = mprn-current_line.
     LOOP AT i_mprn.
       MOVE i_mprn1-mprn TO i_mprn-mprn.
       MOVE ws_postcode TO i_mprn-post_code.
       MODIFY i_mprn INDEX
                mprn-current_line." transporting MPRN POST_CODE.
     ENDLOOP.
**code changed by laxman 10.08.2005
      CALL FUNCTION 'DYNP_VALUES_UPDATE'
        EXPORTING
          dyname               = ws_dyname
          dynumb               = ws_dynumb
        TABLES
          dynpfields           = i_dnpfld
        EXCEPTIONS
          invalid_abapworkarea = 1
          invalid_dynprofield = 2
          invalid_dynproname   = 3
          invalid_dynpronummer = 4
          invalid_request      = 5
          no_fielddescription = 6
          undefind_error       = 7
          OTHERS               = 8.
      IF sy-subrc <> 0.
      ENDIF.
    ENDIF.
ELSEIF sy-subrc EQ 2.
    MESSAGE s006(zspa) WITH i_mprn1-mprn .
ENDIF.
ENDMODULE.                    "MPRN_F4 INPUT
MODULE GNTC_F4 INPUT
MODULE gntc_f4 INPUT.
DATA: BEGIN OF lt_gntc OCCURS 0,
          gntc LIKE iflot-zzgntc,
        END OF lt_gntc.
CLEAR:   lt_returntab, lt_gntc.
REFRESH: lt_returntab, lt_gntc.
lt_gntc-gntc = 'DM'.
APPEND lt_gntc. CLEAR lt_gntc.
lt_gntc-gntc = 'NDM'.
APPEND lt_gntc. CLEAR lt_gntc.
CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
    EXPORTING
      retfield        = 'ZZGNTC'
      dynpprog        = sy-repid
      dynpnr          = sy-dynnr
      window_title    = 'Select Gas Nomination Type Code'
      value_org       = 'S'
    TABLES
      value_tab       = lt_gntc
      return_tab      = lt_returntab
    EXCEPTIONS
      parameter_error = 1
      no_values_found = 2
      OTHERS          = 3.
IF sy-subrc EQ 0.
    READ TABLE lt_returntab INDEX 1.
    i_mprn-dm_ndm = lt_returntab-fieldval.
ENDIF.
ENDMODULE.                    "GNTC_F4 INPUT
*&      Module mprn1_f4 INPUT
      text
MODULE mprn1_f4 INPUT.
DATA: lt_f4          TYPE ddshretval OCCURS 0 WITH HEADER LINE,
        lt_returntab1 LIKE ddshretval OCCURS 0 WITH HEADER LINE,
        lt_dynpfields1 LIKE dynpread OCCURS 0 WITH HEADER LINE,
        lt_dnpfields1 LIKE dynpread OCCURS 0 WITH HEADER LINE.
DATA: stepl1 TYPE systepl,
        stepl_index1 TYPE systepl.
DATA : i_dnpfld1      LIKE dynpread OCCURS 0 WITH HEADER LINE,
         ws_dyname1     LIKE d020s-prog,
         ws_dynumb1     LIKE d020s-dnum,
         ws_dynpfld1    LIKE dynpread.
CLEAR: i_dnpfld1, ws_dyname1, ws_dynumb1, ws_dynpfld1,
         lt_f4, lt_returntab1,lt_dynpfields1, lt_f4,
         stepl1, stepl_index1.
REFRESH: i_dnpfld1, lt_returntab1,lt_dynpfields1, lt_f4.
To Determine Steploop Index
lt_dynpfields1-fieldname = 'I_MPRN-POST_CODE'.
lt_dynpfields1-stepl     = stepl1.
APPEND lt_dynpfields1. CLEAR lt_dynpfields1.
CALL FUNCTION 'DYNP_VALUES_READ'
    EXPORTING
      dyname               = sy-repid
      dynumb               = sy-dynnr
      translate_to_upper   = 'X'
      determine_loop_index = 'X'
    TABLES
      dynpfields           = lt_dynpfields1
    EXCEPTIONS
      invalid_abapworkarea = 1
      invalid_dynprofield = 2
      invalid_dynproname   = 3
      invalid_dynpronummer = 4
      invalid_request      = 5
      no_fielddescription = 6
      invalid_parameter    = 7
      undefind_error       = 8
      double_conversion    = 9
      stepl_not_found      = 10
      OTHERS               = 11.
IF sy-subrc EQ 0.
    READ TABLE lt_dynpfields1 INDEX 1.
ENDIF.
stepl_index1 = lt_dynpfields1-stepl.
CALL FUNCTION 'F4IF_FIELD_VALUE_REQUEST'
    EXPORTING
      tabname           = 'IFLOT'
      fieldname         = 'I_MPRN-MPRN'
      searchhelp        = 'ZS_MPRN_PC'
      dynpprog          = sy-repid
      dynpnr            = sy-dynnr
    TABLES
      return_tab        = lt_f4
    EXCEPTIONS
      field_not_found   = 1
      no_help_for_field = 2
      inconsistent_help = 3
      no_values_found   = 4
      OTHERS            = 5.
IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
    WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
Update tablecontrol
READ TABLE lt_f4 WITH KEY fieldname = 'MPRN'.
IF sy-subrc = 0.
    MOVE lt_f4-fieldval TO i_mprn-mprn.
    ws_dyname1   = 'ZSRO_MASTER_DATA'.
    ws_dynumb1   = '0301'.
    ws_dynpfld1-fieldname ='I_MPRN-MPRN'.
    ws_dynpfld1-fieldvalue = i_mprn-mprn.
    ws_dynpfld1-stepl      = stepl_index1.
    APPEND ws_dynpfld1 TO i_dnpfld1.
    CALL FUNCTION 'DYNP_VALUES_UPDATE'
      EXPORTING
        dyname               = ws_dyname1
        dynumb               = ws_dynumb1
      TABLES
        dynpfields           = i_dnpfld1
      EXCEPTIONS
        invalid_abapworkarea = 1
        invalid_dynprofield = 2
        invalid_dynproname   = 3
        invalid_dynpronummer = 4
        invalid_request      = 5
        no_fielddescription = 6
        undefind_error       = 7
        OTHERS               = 8.
    IF sy-subrc <> 0.
    ENDIF.
ENDIF.
CLEAR : i_dnpfld1, ws_dynpfld1.
REFRESH: i_dnpfld1.
READ TABLE lt_f4 WITH KEY fieldname = 'ZZPSTLZ'.
IF sy-subrc = 0.
    MOVE lt_f4-fieldval TO i_mprn-post_code.
    ws_dyname1   = 'ZSRO_MASTER_DATA'.
    ws_dynumb1   = '0301'.
    ws_dynpfld1-fieldname ='I_MPRN-POST_CODE'.
    ws_dynpfld1-fieldvalue = i_mprn-post_code.
    ws_dynpfld1-stepl      = stepl_index1.
    APPEND ws_dynpfld1 TO i_dnpfld1.
    CALL FUNCTION 'DYNP_VALUES_UPDATE'
      EXPORTING
        dyname               = ws_dyname1
        dynumb               = ws_dynumb1
      TABLES
        dynpfields           = i_dnpfld1
      EXCEPTIONS
        invalid_abapworkarea = 1
        invalid_dynprofield = 2
        invalid_dynproname   = 3
        invalid_dynpronummer = 4
        invalid_request      = 5
        no_fielddescription = 6
        undefind_error       = 7
        OTHERS               = 8.
    IF sy-subrc <> 0.
    ENDIF.
ENDIF.
ENDMODULE.                 " mprn1_f4 INPUT
*&      Module pstlz1_f4 INPUT
      text
MODULE pstlz1_f4 INPUT.
CLEAR: i_dnpfld1, ws_dyname1, ws_dynumb1, ws_dynpfld1,
          lt_f4, lt_returntab1,lt_dynpfields1, lt_f4,
          stepl1, stepl_index1.
REFRESH: i_dnpfld1, lt_returntab1,lt_dynpfields1, lt_f4.
To Determine Steploop Index
lt_dynpfields1-fieldname = 'I_MPRN-MPRN'.
lt_dynpfields1-stepl     = stepl1.
APPEND lt_dynpfields1. CLEAR lt_dynpfields1.
CALL FUNCTION 'DYNP_VALUES_READ'
    EXPORTING
      dyname               = sy-repid
      dynumb               = sy-dynnr
      translate_to_upper   = 'X'
      determine_loop_index = 'X'
    TABLES
      dynpfields           = lt_dynpfields1
    EXCEPTIONS
      invalid_abapworkarea = 1
      invalid_dynprofield = 2
      invalid_dynproname   = 3
      invalid_dynpronummer = 4
      invalid_request      = 5
      no_fielddescription = 6
      invalid_parameter    = 7
      undefind_error       = 8
      double_conversion    = 9
      stepl_not_found      = 10
      OTHERS               = 11.
IF sy-subrc EQ 0.
    READ TABLE lt_dynpfields1 INDEX 1.
ENDIF.
stepl_index1 = lt_dynpfields1-stepl.
CALL FUNCTION 'F4IF_FIELD_VALUE_REQUEST'
    EXPORTING
      tabname           = 'IFLOT'
      fieldname         = 'I_MPRN-POST_CODE'
      searchhelp        = 'ZS_MPRN_PC'
      dynpprog          = sy-repid
      dynpnr            = sy-dynnr
    TABLES
      return_tab        = lt_f4
    EXCEPTIONS
      field_not_found   = 1
      no_help_for_field = 2
      inconsistent_help = 3
      no_values_found   = 4
      OTHERS            = 5.
IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
    WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
Update tablecontrol
READ TABLE lt_f4 WITH KEY fieldname = 'ZZPSTLZ'.
IF sy-subrc = 0.
    MOVE lt_f4-fieldval TO i_mprn-post_code.
    ws_dyname1   = 'ZSRO_MASTER_DATA'.
    ws_dynumb1   = '0301'.
    ws_dynpfld1-fieldname ='I_MPRN-POST_CODE'.
    ws_dynpfld1-fieldvalue = i_mprn-post_code.
    ws_dynpfld1-stepl      = stepl_index1.
    APPEND ws_dynpfld1 TO i_dnpfld1.
    CALL FUNCTION 'DYNP_VALUES_UPDATE'
      EXPORTING
        dyname               = ws_dyname1
        dynumb               = ws_dynumb1
      TABLES
        dynpfields           = i_dnpfld1
      EXCEPTIONS
        invalid_abapworkarea = 1
        invalid_dynprofield = 2
        invalid_dynproname   = 3
        invalid_dynpronummer = 4
        invalid_request      = 5
        no_fielddescription = 6
        undefind_error       = 7
        OTHERS               = 8.
    IF sy-subrc <> 0.
    ENDIF.
ENDIF.
CLEAR : i_dnpfld1, ws_dynpfld1.
REFRESH: i_dnpfld1.
READ TABLE lt_f4 WITH KEY fieldname = 'MPRN'.
IF sy-subrc = 0.
    MOVE lt_f4-fieldval TO i_mprn-mprn.
    ws_dyname1   = 'ZSRO_MASTER_DATA'.
    ws_dynumb1   = '0301'.
    ws_dynpfld1-fieldname ='I_MPRN-MPRN'.
    ws_dynpfld1-fieldvalue = i_mprn-mprn.
    ws_dynpfld1-stepl      = stepl_index1.
    APPEND ws_dynpfld1 TO i_dnpfld1.
    CALL FUNCTION 'DYNP_VALUES_UPDATE'
      EXPORTING
        dyname               = ws_dyname1
        dynumb               = ws_dynumb1
      TABLES
        dynpfields           = i_dnpfld1
      EXCEPTIONS
        invalid_abapworkarea = 1
        invalid_dynprofield = 2
        invalid_dynproname   = 3
        invalid_dynpronummer = 4
        invalid_request      = 5
        no_fielddescription = 6
        undefind_error       = 7
        OTHERS               = 8.
    IF sy-subrc <> 0.
    ENDIF.
ENDIF.
ENDMODULE.                 " pstlz1_f4 INPUT
Regards,
Prakash.

Search help for a field in table control based on another field value

Hi,
I want to attach the Search help for a field in table control based on another field value.
Please help me asap.
Will be highly rewarded

HI,..
Check these links
search help in table control
Re: How to create Search Help for a field in Table control !!
How to create Search Help for a field in Table control !!
F4 Help In Table Control
Control table F4 help
Problem in F4 help in screen field
check this code
DATA: BEGIN OF it_value4 OCCURS 0,
         TEXTCODE LIKE ZXX-TEXTCODE,
         TEXTDESC LIKE ZXX-TEXTDESC,
       END OF it_value4.
progname = sy-repid.
dynnum   = sy-dynnr.
         SELECT TEXTCODE TEXTDESC
           FROM xxxx
           INTO CORRESPONDING FIELDS OF TABLE<b> it_value4</b>
          WHERE LOSS_CODE =<b> IT_VALUE1 .</b>
CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
    EXPORTING
      retfield    = 'TEXTCODE'
      dynpprog    = progname
      dynpnr      = dynnum
      dynprofield = 'ITVALUE-TEXTCODE' "-->UR 4 th filed value in screen
      value_org   = 'S'
    TABLES
      value_tab   = it_value4.
endmodule.
Message was edited by:
        veereshbabu ponnada

Sample report for filling the database table with test data .

Hi ,
Can anyone provide me sample report for filling the database table with test data ?
Thanks ,
Abhi.

hi
the code
data : itab type table of Z6731_DEPTDETAIL,
wa type Z6731_DEPTDETAIL.
wa-DEPT_ID = 'z897hkjh'.
wa-DESCRIPTION = 'computer'.
append wa to itab.
wa-DEPT_ID = 'z897hkjhd'.
wa-DESCRIPTION = 'computer'.
append wa to itab.
loop at itab into wa.
insert z6731_DEPTDETAIL from wa.
endloop.
rewards if helpful

ORA-19007 when coping a table with an xml type in it to a new schema in the

ORA-19007 when coping a table with an xml type in it to a new schema in the same database.
Hi all,
When I copy a table with an xml type in it to a new schema in the same database I get an ora-19009.
The setup is as follows I have a schema a with table TABLE_WITH_XMLTYPE where data is:
CREATE
TABLE TABLE_WITH_XMLTYPE
FOLDER_ID NUMBER (10, 0) NOT NULL,
SEARCH_PROPERTIES XMLTYPE ,
CONSTRAINT TABLE_WITH_XMLTYPE PK PRIMARY KEY (FOLDERID) USING INDEX
XMLTYPE COLUMN SEARCH_PROPERTIES XMLSCHEMA
"http://xxxxxxx.net/FolderProperties.xsd" element "FolderProperties"
VARRAY SEARCH_PROPERTIES."XMLDATA"."PROPERTIES"."PROPERTY" STORE AS TABLE
PROPERTY_TABLE
(PRIMARY KEY (NESTED_TABLE_ID, ARRAY_INDEX)) ORGANIZATION INDEX OVERFLOW
Both schemas have the following xml schema registered as a local xml schema
BEGIN
DBMS_XMLSCHEMA.registerSchema(
SCHEMAURL => 'http://xxxxxxx.net/FolderProperties.xsd',
SCHEMADOC =>
'<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:xdb="http://xmlns.oracle.com/xdb"
xdb:storeVarrayAsTable="true">
<xs:element name="FolderProperties"
type="FolderPropertiesType"
xdb:defaultTable="FOLDER_SEARCH_PROPERTIES" />
<xs:complexType name="FolderPropertiesType" xdb:SQLType="FOLDERPROPERTIES_T">
<xs:sequence>
<xs:element name="FolderID" type="FolderIDType" minOccurs="1" xdb:SQLName="FOLDER_ID"/>
<xs:element name="Properties" type="PropertiesType" xdb:SQLName="PROPERTIES"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="PropertiesType" xdb:SQLType="PROPERTIES_T">
<xs:sequence>
<xs:element name="Property" type="PropertyType" maxOccurs="unbounded"
xdb:SQLName="PROPERTY" xdb:SQLCollType="PROPERTY_V"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="PropertyType" xdb:SQLType="PROPERTY_T">
<xs:sequence>
<xs:element name="DateValue" type="DateType" xdb:SQLName="DATE_VALUE"/>
<xs:element name="NumValue" type="NumType" xdb:SQLName="NUM_VALUE"/>
<xs:element name="StringValue" type="StringType" xdb:SQLName="STRING_VALUE"/>
</xs:sequence>
<xs:attribute name="Name" xdb:SQLName="NAME" xdb:SQLType="VARCHAR2">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:minLength value="1"/>
<xs:maxLength value="255"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:complexType>
<xs:simpleType name="FolderIDType">
<xs:restriction base="xs:integer"/>
</xs:simpleType>
<xs:simpleType name="DateType">
<xs:restriction base="xs:dateTime"/>
</xs:simpleType>
<xs:simpleType name="NumType">
<xs:restriction base="xs:decimal"/>
</xs:simpleType>
<xs:simpleType name="StringType">
<xs:restriction base="xs:string" />
</xs:simpleType>
</xs:schema>',
LOCAL => TRUE,
GENTYPES => TRUE,
GENTABLES => FALSE);
END;
when I try to do the following insert:
insert into schemaB.TABLE_WITH_XMLTYPE ( FOLDER_ID, SEARCH_PROPERTIES)
select FOLDER_ID, SEARCH_PROPERTIES from schemaB.TABLE_WITH_XMLTYPE;
I’ll get an ora-19007.
Can some one point me in the right direction how to solve this error.
Thanks Roelof.

Who did you create the second table, in other words, how did you COPY the table as you said...
If you created the second table via a CTAS (create table as select) then you will have created a table that is not the same as the original one. AFAIK I have once created an enhancement request for this after discovering that JDeveloper, for example, creates a "copy" via a CTAS which creates the wrong structure. Double check via package DBMS_METADATA.
SQL> set long 1000000
SQL> select DBMS_METADATA('TABLE','TABLE_WITH_XMLTYPE','SchemaA') from dual;
SQL> select DBMS_METADATA('TABLE','TABLE_WITH_XMLTYPE','SchemaB') from dual;If you have got two different tables, than Mark's solution should help.
M.
Edited by: Marco Gralike on Feb 15, 2009 11:16 AM

Search Help(F4....) for a FIELD in table

Hi,
In SE11 I created a SEARCH HELP.
And I assigned it to a field in a table.
GOTO>Search help->for field.Here i assigned that created search help name and COPY.
**But it is not reflecting in screens.
Any one suggest me what to do or any thing else i need to take care.
Thnkas in advance.
Message was edited by: Deepak333 k
Message was edited by: Deepak333 k

Hi deepak,
This is the Search Help Process(F4) for a Particular Field.
Go to SE11.
Select Search Help Radio button : Any name with Z or Y.
Create.
Short Description : Any.
Selection Method : Table Name.
Dialog Type : Display Values immediately.
Search Help Parameter : Field Name (for which field ur doing in the table).
Exp : Tick it.
Lpos : 1 Just giving the position.
SAVE CHECK ACTIVATE.
Next Assign the Search Help to the table or field.
SE11.
Your Table Name : Change.
Search Help Button above the fields.
Search Help name : Your search help name.
Copy.
SAVE CHECK ACTIVATE.
Now go and check to the field by F4.
Thats it.
hope this helps you.
reward points for helpfull answers and close the thread if your question is solved.
regards,
venu.

Gaps appear in IE 6 browser window for hidden fields in Create User form

Hi,
I need an urgent input on this one.
I hid an OIM default attribute for users in the 'Create User' form by modifying clear_all_fields.js
The field is hidden from the 'Create User' page fine!
But if I open the page from Internet Explorer 6 it shows a gap in the place of the hidden field.
For Mozilla 3.0.5 the gaps are not appearing.
I tried removing these gaps by deleting the tags and the field in the clear_all_fields.js
or, by reducing the dimension of the spacer.gif in GenerateCreateUserForm.jsp.
But it reflected no change in the form look n feel.
The requirement is to hide the fields and not remove them.
Any suggestion as to what may be the way out?

Thanks for the update Leonard. This would be an extremely useful plugin. I've been looking for it on http://labs.adobe.com/technologies/ under the plug-ins tab but have been unable to find it. It wasn't even there in the Pre-Release Programs. Is it located somewhere else or with a different name? Please let me know.
Meanwhile, I've been trying to write my own VB script to get the button clicked. Here's what I've come up till now-
FindText
HiliteList.Add->CreateWordHilite->SetTextSelect->GetBoundingRect->PointToDevice
The last function seems to be deprecated. Also there's nothing to connect the text highlighted by findtext with HiLiteList.Add. I guess
I may have to use the JSO word search method.
Any advice, as always, would be much appreciated.

Checking for a field in tables

Hi All,
    This Quiery is regarding searching for a field   via where used list.Now we can search for a single field ..in which table that field is being used....
1) Can we make search still specific ..like in which tables that field used as primary field...ex: can i search for the ONLY tables in which werks as primary key..instead of all tables in which it is being used......
2)Now we can search for werks or matnr via where used list which gives all the tables which uses that..so basically we can search based on ONLY one field... can we make search for more than one field..For ex.i want to find a table in which both werks & matnr are used...instead of one...
3)extension to the above is let's say i have information of 4 fields out of which 2 are primary keys..how can i search for a table which contains all 4 fields ...and satisafying the primary key criteria....
       In a nut shell, i want to know is there any way we can make field search more specific...than giving out all tables which is using the field...

Hi,
    in table dd03l use single values range in select-options to specify more than one field and use
keyflag = 'X' to get primary keys.
for example
se11-dd03l->fill fieldnames with matnr,werks
        and keyflag = 'X' to get tables
    having matnr and werks as key fields
Regards
amole

Performance for join 9 custom table with native SQL ?

Hi Expert,
I need your opinion regarding performance to join 9 tables with native sql. Recently i have to tunning some customize extraction cost report. This report extract about 10 million cost of material everyday.
The current program actually, try to populate the condition data and insert into customize table and join all the table to get data using native sql.
SELECT /*+ ordered use_hash(mst,pg,rg,ps,rs,dpg,drg,dps,drs) */
            mst.werks, ....................................
FROM
            sapsr3.zab_info mst,
            sapsr3.zab_pc pg,
            sapsr3.zab_rc rg,
            sapsr3.zab_pc ps,
            sapsr3.zab_rc rs,
            sapsr3.zab_g_pc dpg,
            sapsr3.zab_g_rc drg,
            sapsr3.zab_s_pc dps,
            sapsr3.zab_s_rc drs
        WHERE mst.zseq_no = :p_rep_run_id
        AND mst.werks = :p_werks
        AND mst.mandt = rg.mandt(+)
        AND mst.ekorg = rg.ekorg(+)
        AND mst.lifnr = rg.lifnr(+)
        AND mst.matnr = rg.matnr(+)
        ...............................................   unitl all table (9 tables)
        AND ps.mandt = dps.mandt(+)
        AND ps.knumh = dps.knumh(+)
        AND ps.zseq_no = dps.zseq_no(+)
        AND COALESCE (dps.kbetr, drs.kbetr, dpg.kbetr, drg.kbetr) <> 0
It seems the query ask for database to using hashed table. would that be it will burden the database ? and impacted to others sap process ?
Please advise
Thank You and Best Regards

you can only argue coming from measurements and that is not the case.
Coming from the code, I see only that you do not understand it at all, so better leave it as it is. It is not a hash table, but a hash join on these table.

F4 help for a field on table control

Hi All,
I have to display F4 help for a purticular field on the table control depending on one of the value in the row if the table.
There will be multiple entries in the table control and the F4 help for the field should change according to the value of other field in the row.
Can anybdy help me out doing this.....
Edited by: Alvaro Tejada Galindo on Feb 21, 2008 10:46 AM

Check the FM: HELP_VALUES_GET_WITH_TABLE_EXT
Check the documentation for example code.
regards,
Ravi

Best practice to define length for varchar field of table in sql server

What is best practice to define length for a varchar field in table
where field suppose Remarks By Person varchar(max) or varchar(4000)
Could it affect on optimization in future????
experts Reply Must ...
Dilip Patil..

Hi Dilip,
Varchar(n/max) is a variable-length, non-unicode character data. N defines the string length and can be a value from 1 through 8,000. Max indicates that the maximum storage size is 2^31-1 bytes (2 GB). The storage size is the actual length of the data entered
+ 2 bytes. We always use varchar when the sizes of the column data entries vary considerably. While if the filed data size might exceed 8,000 bytes in some way, we should use varchar(max).
So the conclusion is just like Uri said, use varchar(max) or varchar(4000) is depends on how much characters we are going to store.
The following document about varchar in SQL Server is for your reference:
http://technet.microsoft.com/en-us/library/ms176089.aspx
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Using Field Exit for a field in table KNA1

Hi everyone,
I am working on a ticket, the problem is we have a field called STRAS in table KNA1 which holds the address of the customer but now we want to increase the length of this field from 35 charachters to 55 due to some business requirement. SO my question is if this can be done using Field Exit and if yes.. can you please tell me how as I have never used Field exits.
Thanks,
Rajeev

Hi,
Using field exit, you can only validate the data entry for the field (either globally or on a particular screen field)
This is usually done by implementing the field exit for the data element corresponding to the field(in your case STRAS_GP)
Hence you cannot increase the length of the field using the concept of the field exits...
Please note that after SAP R/3 4.6c, SAP has stopped the creation of field exits and there will be no support for any new ones created.
Regards
Shiva

Values for a field in table

Hi Experts
Can you explain me that, in table some of the fields has predefined values, whether its a value table or what.
Pls explain, how to set predefined values for particular fields to our own tables.
Thank in advance.
Regards
Rajaram

Hi,
you can explicitly mention domain range as value table for the fields in the database table.
Also the search help can be maintained for the fields in SE11 transcation where the value table can be specified.
Reward appropriate points.
Regards,
Mansi.

Show colored circles for a field inside table view

HI
I need to show Colored circles based on some conditions for a field (priority) inside a table view. HOw do i implement this solution.
PLease help

Hi,
You have two possibilities:
1. HTMLB charting
See http://www.sapdesignguild.org/resources/ma_guidelines_3/LAYOUT/chart_types.html for more info
2. IGS charting. See this weblog for info
/people/thomas.jung3/blog/2004/08/31/bsp-150-a-developer146s-journal-part-x--igs-charting
You will be certainly interested in this web log
/people/thomas.jung3/blog/2005/09/08/igs-charting-altering-the-customizing-xml-at-runtime
I don't know if you can combine stuff in a tableview.
See also chart graphics
http://help.sap.com/saphelp_nw04/helpdata/en/9b/d9883672d57c73e10000009b38f889/frameset.htm
Alternatively, you can try out the canvas tag in new browsers like Firefox. See /people/eddy.declercq/blog/2005/12/09/blank-canvas
for this
Eddy

NullPointerException for hidden field in table with col of type DBSequence

Similar Messages

Maybe you are looking for