How to create a cluster table and cluster view?

Hi,
Can anyone guide me in creation of cluster table in general and also creation of cluster view?

Hi,
check this links.
http://help.sap.com/saphelp_nw04/helpdata/en/cf/21f0b7446011d189700000e8322d00/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/d0/999246b2aa11d1a5700000e82deaaa/content.htm
Regard's
SHAIK.

Similar Messages

How 2 create dynamic internal table and can we pass it to gui_download FM

HI all,
     How can we create a dynamic internal table?
I have a requirement where i have to create an internal table with the no. of fields depending on the selection screen values, i think tat can be possible though dynamic creation only.
         How to solve this issue..?Pointers will be very much useful..
Thanks
Sunny.

hi
Follow the code it will help you out....
REPORT YUSMM_TEXT2                             .
*TABLES
TABLES: MARA,    " General Material Data
        MAKT,    " Material Descriptions
        T002.    " Language Keys
* GLOBAL TYPE-POOL
TYPE-POOLS : SLIS.
* GLOBAL TYPES
TYPES: BEGIN OF TP_LANG ,
         SPRAS LIKE T002-SPRAS,
         LAISO LIKE T002-LAISO,
         SRNO(3) TYPE N,
       END OF TP_LANG.
TYPES: BEGIN OF TP_MATNR,
         MATNR LIKE MARA-MATNR,
         BEGRU LIKE MARA-BEGRU,
       END OF TP_MATNR.
* DECLARATION FOR GLOBAL INTERNAL TABLES (WITH INCLUDE STRUCTURE)
DATA:GT_MAKT    TYPE STANDARD TABLE OF MAKT, "Materialkurztexte,
     GT_THEAD   TYPE STANDARD TABLE OF THEAD, "SAPscript: Text-Header,
     GT_LINETAB TYPE STANDARD TABLE OF TLINE, "SAPscript: Text-Zeilen,
     GT_T002    TYPE STANDARD TABLE OF T002. "Language key
DATA: BEGIN OF GV_TEXT_OUTPUT_LINE,
            MATNR LIKE MARA-MATNR,
            BEGRU LIKE MARA-BEGRU,
            MAKTX LIKE MAKT-MAKTX,
            LTXT40(1250) TYPE C,
            SRNO(3) TYPE N,
            SPRAS LIKE T002-SPRAS,
         END OF GV_TEXT_OUTPUT_LINE.
DATA: GT_MATNR TYPE STANDARD TABLE OF TP_MATNR,
      WA_GT_MATNR TYPE TP_MATNR.
DATA: GT_LANG TYPE STANDARD TABLE OF TP_LANG,
      WA_GT_LANG TYPE TP_LANG.
DATA: GT_TEXT_OUTPUT_LINE LIKE STANDARD TABLE OF GV_TEXT_OUTPUT_LINE,
      GT_FIELDCAT         TYPE SLIS_T_FIELDCAT_ALV,
      GV_FIELDCAT         LIKE LINE OF GT_FIELDCAT,
      CT_GT_FIELDCAT_IN LIKE GV_FIELDCAT,
      GS_LAYOUT           TYPE SLIS_LAYOUT_ALV,
      GV_REPID            TYPE SY-REPID.
DATA: BEGIN OF GV,
        FORMER_ERROR       LIKE SY-MARKY,     " Fehlermeldung bereits
        FILE_OPEN(1),                          " Flag open file
        REC_LENGTH         TYPE I,            " record length
        MATNR              TYPE MARA-MATNR,   " material
        REPID              TYPE SYST-REPID,
        RETCO              TYPE SY-SUBRC,
      END OF GV.
DATA: GV_MAKT             TYPE MAKT,
      GV_T002             TYPE T002,
      GV_LANGU            TYPE THEAD-TDSPRAS.
* DECLARATION FOR FIELD-SYMBOLS
FIELD-SYMBOLS: <FS_DATA> TYPE REF TO DATA,
               <FS_DATA1> TYPE REF TO DATA,
               <FS_2>    TYPE STANDARD TABLE,
               <FS_22>   TYPE STANDARD TABLE,
               <FS_1>,
               <FS_11>,
               <F>,
               <FA>,
               <LWA_LINE_WA>,
               <LWA_LINE_WA1>.
DATA: IT_FLDCAT TYPE LVC_T_FCAT.
DATA: T_FLDCAT1   TYPE SLIS_T_FIELDCAT_ALV.
DATA: L_LT TYPE SLIS_LAYOUT_ALV.
DATA: WA_IT_FLDCAT TYPE LVC_S_FCAT.
DATA: WA_IT_FLDCAT1 TYPE SLIS_FIELDCAT_ALV.
DATA: GP_TABLE TYPE REF TO DATA.
DATA: WA_NEWLINE TYPE REF TO DATA.
*DECLARATION FOR CONSTANTS
CONSTANTS:
   BEGIN OF GC,
     TDID_GRUN     TYPE THEAD-TDID     VALUE 'GRUN',
     TDOBJECT_MAT TYPE THEAD-TDOBJECT VALUE 'MATERIAL',
     ON(01)        TYPE C              VALUE 'X',
     YES(01)       TYPE C              VALUE 'X',
     TXT(25)       TYPE C              VALUE 'MATERIAL DETAILS',
     MAT(25)       TYPE C              VALUE 'MATERIAL NUMBER',
     AUT(25)       TYPE C              VALUE 'AUTHORIZATION GROUP',
     FOUND         TYPE SY-SUBRC       VALUE '00', " Return-Code
     RC_OK         TYPE SY-SUBRC       VALUE '00', " Return-Code
     OFF           TYPE SY-SUBRC       VALUE '00', " return code
     FALSE         TYPE SY-SUBRC       VALUE '00', " boolean
     TRUE          TYPE SY-SUBRC       VALUE '01', " boolean
END OF GC.
* DECLARATION FOR VARIABLES
DATA: V(3) TYPE N,
      STR TYPE STRING,
      STR1 TYPE STRING,
      V_VAR(3) TYPE N,
      V_VAR1(3) TYPE N,
      V_FIELDNAME(15) TYPE C,
      V_CHAR(15) TYPE C,
      V_LINES(3) TYPE N,
      MAKTEXT LIKE MAKT-MAKTX,
      LT_DATA        TYPE   REF TO DATA,
      LT_DATA1        TYPE   REF TO DATA,
      LWA_LINE       TYPE   REF TO DATA,
      LWA_LINE1 TYPE REF TO DATA.
*SELECTION-SCREEN AND PARAMETERS
SELECTION-SCREEN: BEGIN OF BLOCK A1 WITH FRAME TITLE TEXT-002.
SELECT-OPTIONS:
S_MATNR FOR MARA-MATNR, "MATERIAL NUMBER
S_MTART FOR MARA-MTART, "MATERIAL TEXT
S_LANG FOR MAKT-SPRAS.   "LANGUAGE
PARAMETER: GP_SIZE TYPE I DEFAULT 200. "DATA LENGTH
SELECTION-SCREEN: END OF BLOCK A1.
* AT SELECTION SCREEN
AT SELECTION-SCREEN.
IF GP_SIZE < 0.
    MESSAGE E002(00).
ENDIF.
IF GP_SIZE > 50000.
    MESSAGE W130(26) WITH TEXT-004.
    SET CURSOR FIELD 'gp_size'.
ENDIF.
* INITIALIZATION
INITIALIZATION.
GV-REPID = SY-REPID.
*START-OF-SELECTION
START-OF-SELECTION.
PERFORM GET_MARA_DATA
            TABLES
              GT_TEXT_OUTPUT_LINE
            USING
              S_MATNR[]
              S_MTART[]
              GP_SIZE
            CHANGING
              GV-RETCO
PERFORM GET_MAT_TEXT
             TABLES
               GT_MAKT
               GT_TEXT_OUTPUT_LINE
               GT_THEAD
               GT_LINETAB
             USING
               GC
               GV-RETCO
             CHANGING
               GV_TEXT_OUTPUT_LINE
               GV_MAKT
PERFORM GET_LANG.
PERFORM DYNAMIC_TABLES.
PERFORM POPULATE_FINAL_TABLE.
PERFORM POPULATE_DYNAMIC_TABLE.
* END-OF-SELECTION
END-OF-SELECTION.
PERFORM DATA_OUTPUT.
*&      Form get_mara_data
*       Materialdaten lesen
*      <->ct_gt_text_output_line Ausgabetabelle
*      -->it_s_matnr Parameter Materialnummer
*      -->it_s_mtart Parameter Materialart
*      -->if_gp_size Parameter Anzahl Materialnummern
FORM GET_MARA_DATA TABLES   CT_GT_TEXT_OUTPUT_LINE STRUCTURE
                                   GV_TEXT_OUTPUT_LINE
                    USING    IT_S_MATNR LIKE S_MATNR[]
                             IT_S_MTART LIKE S_MTART[]
                             IF_GP_SIZE
                    CHANGING IF_GV-RETCO.                   "#EC *
* MARA in die Übergabestruktur einlesen
SELECT MATNR BEGRU
        FROM MARA UP TO IF_GP_SIZE ROWS
        APPENDING CORRESPONDING FIELDS OF TABLE GT_MATNR
                 WHERE MATNR IN IT_S_MATNR
                   AND MTART IN IT_S_MTART.
IF_GV-RETCO = SY-SUBRC.
ENDFORM.                    " get_mara_data
*&      Form get_mat_text
*       Kurz- und Langtexte zum Material lesen
*      <->ct_gt_makt              Materialkurztexte
*      <->ct_gt_text_output_line Ausgabetabelle
*      <->ct_gt_thead             Kopftabelle für ALV
*      <->ct_gt_linetab           Zeilentabelle für ALV
*      -->if_gc                   Globale Konstanten
*      <--cf_gv_text_output_line Struktur Ausgabetabelle
*      <--cf_gv_makt              Struktru Materialkurztexte
FORM GET_MAT_TEXT TABLES   CT_GT_MAKT             STRUCTURE MAKT
                            CT_GT_TEXT_OUTPUT_LINE STRUCTURE
                                                GV_TEXT_OUTPUT_LINE
                            CT_GT_THEAD            STRUCTURE THEAD
                            CT_GT_LINETAB          STRUCTURE TLINE
                   USING
                            IF_GC                  LIKE GC
                            IF_GV-RETCO
                   CHANGING CF_GV_TEXT_OUTPUT_LINE LIKE
                                                   GV_TEXT_OUTPUT_LINE
                            CF_GV_MAKT             LIKE GV_MAKT
DATA: STRG TYPE STRING,
        STRG1(1255) TYPE C.
IF IF_GV-RETCO = IF_GC-FOUND.
* Materialkurztexte in alles Sprachen einlesen
    SELECT * FROM MAKT APPENDING TABLE CT_GT_MAKT
             FOR ALL ENTRIES IN GT_MATNR "ct_gt_text_output_line
             WHERE MATNR = GT_MATNR-MATNR " ct_gt_text_output_line-matnr
* Kurztexte in die sprachabhängigen Felder bringen
    LOOP AT GT_MATNR INTO WA_GT_MATNR.
      LOOP AT CT_GT_MAKT INTO CF_GV_MAKT
             WHERE MATNR = WA_GT_MATNR-MATNR.
        CF_GV_TEXT_OUTPUT_LINE-MATNR = WA_GT_MATNR-MATNR.
        CF_GV_TEXT_OUTPUT_LINE-BEGRU = WA_GT_MATNR-BEGRU.
        CF_GV_TEXT_OUTPUT_LINE-MAKTX = CF_GV_MAKT-MAKTX.
        CF_GV_TEXT_OUTPUT_LINE-SPRAS = CF_GV_MAKT-SPRAS.
* LANGTEXT
        CLEAR CT_GT_THEAD[].
        CT_GT_THEAD-TDOBJECT = IF_GC-TDOBJECT_MAT.
        CT_GT_THEAD-TDNAME   = WA_GT_MATNR-MATNR.
        CT_GT_THEAD-TDID     = IF_GC-TDID_GRUN.
        CT_GT_THEAD-TDSPRAS = CF_GV_MAKT-SPRAS.
        CALL FUNCTION 'TEXT_READ'
          EXPORTING
            I_HEADER   = CT_GT_THEAD
            I_READONLY = IF_GC-ON
          IMPORTING
            E_HEADER   = CT_GT_THEAD
          TABLES
            T_LINES    = CT_GT_LINETAB[]
          EXCEPTIONS
            NOTFOUND   = 1.
        IF SY-SUBRC = IF_GC-FOUND.
          LOOP AT CT_GT_LINETAB.
            STRG = CT_GT_LINETAB-TDLINE.
            IF STRG1 <> ' '.
              CONCATENATE STRG1 ';' STRG INTO STRG1.
            ELSE.
              STRG1 = STRG.
            ENDIF.
          ENDLOOP.
          CF_GV_TEXT_OUTPUT_LINE-LTXT40 = STRG1.
          APPEND CF_GV_TEXT_OUTPUT_LINE TO CT_GT_TEXT_OUTPUT_LINE.
          CLEAR CF_GV_TEXT_OUTPUT_LINE.
          STRG1 = ' '.
        ELSE.
          APPEND CF_GV_TEXT_OUTPUT_LINE TO CT_GT_TEXT_OUTPUT_LINE.
        ENDIF.
      ENDLOOP.
    ENDLOOP.
ENDIF.
ENDFORM.                    " get_mat_text
*&      Form data_output
*       Daten mit ALV ausgeben
*      <->ct_GT_FIELDCAT          Feldkatalog für ALV
*      <->ct_gt_text_output_line Ausgabetabelle
*      -->P_GS_LAYOUT             Layout für ALV
*      -->if_gc                   Globale Konstanten
*      <--cf_GV_REPID             Zur Zeit aufgerufener Reportname
*      <--cf_gv_fieldcat          Struktur Feldkatalog
*      <--cf_gv                   Globale Variablen
FORM DATA_OUTPUT.
PERFORM FIELDCATBUILD.
PERFORM LAYOUT.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
    EXPORTING
      I_CALLBACK_PROGRAM       = GV-REPID
      I_CALLBACK_PF_STATUS_SET = 'EVENT_SET_STATUS_01'
      I_CALLBACK_USER_COMMAND = 'EVENT_USER_COMMAND'
      IS_LAYOUT                = L_LT
      IT_FIELDCAT              = T_FLDCAT1[]
    TABLES
      T_OUTTAB                 = <FS_2>
    EXCEPTIONS
      PROGRAM_ERROR            = 1
      OTHERS                   = 2.
IF SY-SUBRC <> GC-FOUND.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM.                    " data_output
*&      Form fieldcatbuild
*       text
* --> p1        text
* <-- p2        text
FORM FIELDCATBUILD. " TABLES   ct_gt_fieldcat_in STRUCTURE gv_fieldcat.
LOOP AT IT_FLDCAT INTO WA_IT_FLDCAT.
    WA_IT_FLDCAT1-FIELDNAME = WA_IT_FLDCAT-FIELDNAME.
    WA_IT_FLDCAT1-TABNAME = WA_IT_FLDCAT-TABNAME.
    WA_IT_FLDCAT1-SELTEXT_L = WA_IT_FLDCAT-FIELDNAME.
    APPEND WA_IT_FLDCAT1 TO T_FLDCAT1.
    CLEAR : WA_IT_FLDCAT,WA_IT_FLDCAT1.
ENDLOOP.
ENDFORM.                    " fieldcatbuild
* Form event_set_status_01*
FORM EVENT_SET_STATUS_01 USING LT_EXCL TYPE SLIS_T_EXTAB.
SET PF-STATUS 'ABCD' .
ENDFORM. "EVENT_SET_STATUS_01
*& Form Name: event_user_command *
*& Form Desc: For Handling USER_COMMAND *
FORM EVENT_USER_COMMAND USING
IF_UCOMM TYPE SY-UCOMM
IS_SELFIELD TYPE SLIS_SELFIELD.
CASE IF_UCOMM.
    WHEN 'DOWNLOAD'.
      PERFORM POPULATE_DOWNLOAD_TABLE.
      DATA: L_LENGHT TYPE I.
      CALL FUNCTION 'GUI_DOWNLOAD'
        EXPORTING
          FILENAME              = 'C:data.xls'
          FILETYPE              = 'ASC'
          WRITE_FIELD_SEPARATOR = 'X'
          TRUNC_TRAILING_BLANKS = 'X'
          DAT_MODE              = 'X'
        IMPORTING
          FILELENGTH            = L_LENGHT
        TABLES
          DATA_TAB              = <FS_22>.
      IF SY-SUBRC <> GC-FOUND.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
      IF L_LENGHT NE GC-FOUND.
        MESSAGE S398(00) WITH 'DATA downloaded to c:data.xls'.
      ENDIF.
ENDCASE.
ENDFORM.                    "event_user_command
*&      Form get_lang
*       text
* --> p1        text
* <-- p2        text
FORM GET_LANG.
SELECT SPRAS
           LAISO FROM T002 INTO CORRESPONDING FIELDS OF TABLE GT_LANG
                  WHERE SPRAS IN S_LANG.
DESCRIBE TABLE GT_LANG LINES V_LINES.
LOOP AT GT_LANG INTO WA_GT_LANG.
    V = V + 1.
    WA_GT_LANG-SRNO = V.
    MODIFY GT_LANG FROM WA_GT_LANG TRANSPORTING SRNO.
ENDLOOP.
LOOP AT GT_LANG INTO WA_GT_LANG.
    CONCATENATE 'MATEDESC-' WA_GT_LANG-LAISO INTO V_FIELDNAME.
    CLEAR WA_IT_FLDCAT.
    WA_IT_FLDCAT-FIELDNAME = V_FIELDNAME.
    WA_IT_FLDCAT-SELTEXT = V_FIELDNAME.
    WA_IT_FLDCAT-DATATYPE = 'CHAR'.
    WA_IT_FLDCAT-INTLEN = 40.
    WA_IT_FLDCAT-TABNAME = '<FS_2>'.
    APPEND WA_IT_FLDCAT TO IT_FLDCAT .
    CLEAR WA_GT_LANG.
ENDLOOP.
LOOP AT GT_LANG INTO WA_GT_LANG.
    CONCATENATE 'BASDAT-' WA_GT_LANG-LAISO INTO V_FIELDNAME.
    CLEAR WA_IT_FLDCAT.
    WA_IT_FLDCAT-FIELDNAME = V_FIELDNAME.
    WA_IT_FLDCAT-DATATYPE = 'CHAR'.
    WA_IT_FLDCAT-INTLEN = 255.
    WA_IT_FLDCAT-SELTEXT = V_FIELDNAME.
    WA_IT_FLDCAT-TABNAME = '<FS_2>'.
    APPEND WA_IT_FLDCAT TO IT_FLDCAT .
    CLEAR WA_GT_LANG.
ENDLOOP.
V_FIELDNAME = 'MATNR'.
CLEAR WA_IT_FLDCAT.
WA_IT_FLDCAT-FIELDNAME = V_FIELDNAME.
WA_IT_FLDCAT-DATATYPE = 'CHAR'.
WA_IT_FLDCAT-SELTEXT = 'Matnr'.
WA_IT_FLDCAT-INTLEN = 18.
WA_IT_FLDCAT-TABNAME = '<FS_2>'.
INSERT WA_IT_FLDCAT INTO IT_FLDCAT INDEX 1.
V_FIELDNAME = 'BEGRU'.
CLEAR WA_IT_FLDCAT.
WA_IT_FLDCAT-FIELDNAME = V_FIELDNAME.
WA_IT_FLDCAT-DATATYPE = 'CHAR'.
WA_IT_FLDCAT-SELTEXT = 'BEGRU'.
WA_IT_FLDCAT-INTLEN = 4.
WA_IT_FLDCAT-TABNAME = '<FS_2>'.
INSERT WA_IT_FLDCAT INTO IT_FLDCAT INDEX 2.
ENDFORM.                    " get_lang
*&      Form dynamic_tables
*       text
* --> p1        text
* <-- p2        text
FORM DYNAMIC_TABLES.
ASSIGN LT_DATA TO <FS_DATA>.
* Creating the Dynamic Internal Table
CALL METHOD CL_ALV_TABLE_CREATE=>CREATE_DYNAMIC_TABLE
    EXPORTING
      IT_FIELDCATALOG           = IT_FLDCAT      " Fieldcatalogue
    IMPORTING
      EP_TABLE                  = <FS_DATA>     " Dynamic Internal Table
    EXCEPTIONS
      GENERATE_SUBPOOL_DIR_FULL = 1
      OTHERS                    = 2.
* Assign Dyn Table To Field Sumbol
ASSIGN <FS_DATA>->* TO <FS_1>.
* Assigning the Internal Table TYPE ANY to Standard internal Table
ASSIGN <FS_1> TO <FS_2>.
* Creating a Workarea
CREATE DATA LWA_LINE LIKE LINE OF <FS_2> .
* Assigning the Content to the workares as a Pointer
ASSIGN LWA_LINE->* TO <LWA_LINE_WA>.
ENDFORM.                    " dynamic_tables
*&      Form populate_final_table
*       text
* --> p1        text
* <-- p2        text
FORM POPULATE_FINAL_TABLE.
LOOP AT GT_TEXT_OUTPUT_LINE INTO GV_TEXT_OUTPUT_LINE.
    READ TABLE GT_LANG INTO WA_GT_LANG
              WITH KEY SPRAS = GV_TEXT_OUTPUT_LINE-SPRAS.
    IF SY-SUBRC EQ GC-FOUND.
      GV_TEXT_OUTPUT_LINE-SRNO = WA_GT_LANG-SRNO.
    ENDIF.
    MODIFY GT_TEXT_OUTPUT_LINE FROM GV_TEXT_OUTPUT_LINE.
ENDLOOP.
ENDFORM.                    " populate_final_table
*&      Form populate_dynamic_table
*       text
* --> p1        text
* <-- p2        text
FORM POPULATE_DYNAMIC_TABLE.
DATA: INDX TYPE SY-TABIX.
LOOP AT GT_TEXT_OUTPUT_LINE INTO GV_TEXT_OUTPUT_LINE.
    AT NEW MATNR.
      INDX = SY-TABIX.
      ASSIGN COMPONENT 1 OF STRUCTURE <LWA_LINE_WA> TO <F>.
      <F> = GV_TEXT_OUTPUT_LINE-MATNR.
      ASSIGN COMPONENT 2 OF STRUCTURE <LWA_LINE_WA> TO <F>.
      <F> = GV_TEXT_OUTPUT_LINE-BEGRU.
    ENDAT.
    LOOP AT GT_LANG INTO WA_GT_LANG.
      IF GV_TEXT_OUTPUT_LINE-SRNO = WA_GT_LANG-SRNO.
        V_VAR = GV_TEXT_OUTPUT_LINE-SRNO + 2.
        ASSIGN COMPONENT V_VAR OF STRUCTURE <LWA_LINE_WA> TO <F>.
        <F> = GV_TEXT_OUTPUT_LINE-MAKTX.
        V_VAR = GV_TEXT_OUTPUT_LINE-SRNO + V_LINES + 2.
        ASSIGN COMPONENT V_VAR OF STRUCTURE <LWA_LINE_WA> TO <F>.
        <F> = GV_TEXT_OUTPUT_LINE-LTXT40.
      ENDIF.
    ENDLOOP.
    AT END OF MATNR.
      APPEND <LWA_LINE_WA> TO <FS_2>.
      CLEAR <LWA_LINE_WA>.
    ENDAT.
ENDLOOP.
ENDFORM.                    " populate_dynamic_table
*&      Form LAYOUT
*       text
* --> p1        text
* <-- p2        text
FORM LAYOUT.
CLEAR L_LT.
L_LT-ZEBRA = GC-YES.
L_LT-COLWIDTH_OPTIMIZE = 'X'.
L_LT-WINDOW_TITLEBAR = GC-TXT.
ENDFORM.                    " LAYOUT
*&      Form populate_download_table
*       text
* --> p1        text
* <-- p2        text
FORM POPULATE_DOWNLOAD_TABLE.
ASSIGN LT_DATA1 TO <FS_DATA1>.
CALL METHOD CL_ALV_TABLE_CREATE=>CREATE_DYNAMIC_TABLE
    EXPORTING
      IT_FIELDCATALOG           = IT_FLDCAT         " Fieldcatalogue
    IMPORTING
      EP_TABLE                  = <FS_DATA1> " Dynamic Internal table
    EXCEPTIONS
      GENERATE_SUBPOOL_DIR_FULL = 1
      OTHERS                    = 2.
* Assign Dyn Table To Field Sumbol
ASSIGN <FS_DATA1>->* TO <FS_11>.
* Assigning the Internal Table TYPE ANY to Standard internal Table
ASSIGN <FS_11> TO <FS_22>.
* Creating a Workarea
CREATE DATA LWA_LINE1 LIKE LINE OF <FS_22> .
* Assigning the Content to the workares as a Pointer
ASSIGN LWA_LINE1->* TO <LWA_LINE_WA1>.
DATA: STRN1 TYPE STRING,
        STRN2 TYPE STRING,
        INDX TYPE SY-TABIX.
ASSIGN COMPONENT 1 OF STRUCTURE <LWA_LINE_WA1> TO <FA>.
<FA> = GC-MAT.
ASSIGN COMPONENT 2 OF STRUCTURE <LWA_LINE_WA1> TO <FA>.
<FA> = GC-AUT.
LOOP AT GT_LANG INTO WA_GT_LANG.
    V_VAR1 = WA_GT_LANG-SRNO + 2.
    CONCATENATE 'MATERIALDESCRIPTION-' WA_GT_LANG-LAISO INTO STRN1.
    ASSIGN COMPONENT V_VAR1 OF STRUCTURE <LWA_LINE_WA1> TO <FA>.
    <FA> = STRN1.
    V_VAR1 = WA_GT_LANG-SRNO + V_LINES + 2.
    CONCATENATE 'BASICDATA-' WA_GT_LANG-LAISO INTO STRN2.
    ASSIGN COMPONENT V_VAR1 OF STRUCTURE <LWA_LINE_WA1> TO <FA>.
    <FA> = STRN2.
ENDLOOP.
APPEND <LWA_LINE_WA1> TO <FS_22>.
CLEAR <LWA_LINE_WA1>.
APPEND <LWA_LINE_WA1> TO <FS_22>.
V_VAR1 = 0.
LOOP AT GT_TEXT_OUTPUT_LINE INTO GV_TEXT_OUTPUT_LINE.
    AT NEW MATNR.
      INDX = SY-TABIX.
      ASSIGN COMPONENT 1 OF STRUCTURE <LWA_LINE_WA1> TO <FA>.
      <FA> = GV_TEXT_OUTPUT_LINE-MATNR.
      ASSIGN COMPONENT 2 OF STRUCTURE <LWA_LINE_WA1> TO <FA>.
      <FA> = GV_TEXT_OUTPUT_LINE-BEGRU.
    ENDAT.
    LOOP AT GT_LANG INTO WA_GT_LANG.
      IF GV_TEXT_OUTPUT_LINE-SRNO EQ WA_GT_LANG-SRNO.
        V_VAR1 = GV_TEXT_OUTPUT_LINE-SRNO + 2.
        ASSIGN COMPONENT V_VAR1 OF STRUCTURE <LWA_LINE_WA1> TO <FA>.
        <FA> = GV_TEXT_OUTPUT_LINE-MAKTX.
        V_VAR1 = GV_TEXT_OUTPUT_LINE-SRNO + V_LINES + 2.
        ASSIGN COMPONENT V_VAR1 OF STRUCTURE <LWA_LINE_WA1> TO <FA>.
*        STR = GV_TEXT_OUTPUT_LINE-LTXT40.
*        SEARCH STR FOR ';'.
*        DO.
*          IF SY-SUBRC = 0.
*            SPLIT STR AT ';' INTO STR1 STR.
*            <FA> = STR1.
*            APPEND <LWA_LINE_WA1> TO <FS_22>.
*            SEARCH STR FOR ';'.
*            CLEAR <LWA_LINE_WA1>.
*          ELSE.
*            EXIT.
*          ENDIF.
*        ENDDO.
*        <FA> = STR.
*        APPEND <LWA_LINE_WA1> TO <FS_22>.
        <FA> = GV_TEXT_OUTPUT_LINE-LTXT40.
      ENDIF.
    ENDLOOP.
    AT END OF MATNR.
      APPEND <LWA_LINE_WA1> TO <FS_22>.
      CLEAR <LWA_LINE_WA1>.
    ENDAT.
ENDLOOP.
ENDFORM.                    " populate_download_table
thanks
Nitya

How to create solved fact table and corresponding cube

Hello,
I want to create cube with solved fact table. It means, i need to feed data for higher levels of dimension also from fact table instead of aggreting from base level.
I am using star schema and AWM 10g R2 for creating cube.
If anyone knows how to do this, i would be very benificial.
Thanks
Subash

I have generated parent child script using cwm2_olap_pc_transform.create_script. After running this generated script, it has created 3 table/view.
My Base Parent Child table is like this:-
drop table PARENT_CHILD;
create table PARENT_CHILD (PARENT varchar2(30), CHILD varchar2(30));
insert into PARENT_CHILD values ('Eligible', 'Compliant');
insert into PARENT_CHILD values ('Eligible', 'Non-Compliant');
insert into PARENT_CHILD values ('All', 'Eligible');
insert into PARENT_CHILD values ('All', 'Ineligible');
insert into PARENT_CHILD values (null, 'All');
After running generated script thru cwm2_olap_pc_transform.create_script, it has created :-
Table - PARENT_CHILD_SOLVED
View - PARENT_CHILD_SOLVED_view , PARENT_CHILD_view
This script also inserted data in above table/view. (5 rec in each). Table/View structure is like this:-
SQL> desc PARENT_CHILD_view
Name Null? Type
GID NUMBER
CHILD1 VARCHAR2(30)
CHILD2 VARCHAR2(30)
CHILD3 VARCHAR2(30)
Data:-
0 All Eligible Compliant
0 All Eligible Non-Compliant
1 All Eligible
1 All Ineligible
3 All
SQL> desc PARENT_CHILD_SOLVED
Name Null? Type
GID NUMBER
CHILD1 VARCHAR2(30)
CHILD2 VARCHAR2(30)
CHILD3 VARCHAR2(30)
Data:-
0 All Eligible Compliant
0 All Eligible Non-Compliant
1 All Eligible
1 All Ineligible
3 All
SQL> desc PARENT_CHILD_SOLVED_view
Name Null? Type
GID NUMBER
SHORT_DESCRIPTION VARCHAR2(30)
LONG_DESCRIPTION VARCHAR2(30)
CHILD1 VARCHAR2(30)
CHILD2 VARCHAR2(30)
CHILD3 VARCHAR2(30)
Data:-
0 Compliant Compliant All Eligible Compliant
0 Non-Compliant Non-Compliant All Eligible Non-Compliant
1 Eligible Eligible All Eligible
1 Ineligible Ineligible All Ineligible
3 All All All
I tried to create dim and cube based on this. I am not sure whether its correct or not! Though validate_dimension API call shows that it is valid.
Script for Dim:-
DECLARE
-- variable to hold error message
errtxt varchar(60);
BEGIN
-- To be on safer side just drop dimension before creating new one and catch exceptions
BEGIN
cwm2_olap_dimension.drop_dimension('APPS', 'HCP_DIM_PC');
EXCEPTION
WHEN OTHERS THEN
dbms_output.put_line('Dimension HCP_DIM_PC not dropped');
END;
cwm2_olap_dimension.create_dimension(
'APPS',
'HCP_DIM_PC',
'Parent Child',
NULL,
'Parent Child',
'Parent Child',
NULL);
cwm2_olap_dimension_attribute.create_dimension_attribute(
'APPS',
'HCP_DIM_PC',
'Short Description',
'Short Description',
'Short Description',
'Short Description',
TRUE);
cwm2_olap_dimension_attribute.create_dimension_attribute(
'APPS',
'HCP_DIM_PC',
'Long Description',
'Long Description',
'Long Description',
'Long Description',
TRUE);
cwm2_olap_dimension_attribute.create_dimension_attribute(
'APPS',
'HCP_DIM_PC',
'Grouping ID',
'Grouping ID',
'Grouping ID',
'Grouping ID',
TRUE);
cwm2_olap_hierarchy.create_hierarchy(
'APPS',
'HCP_DIM_PC',
'HCP_DIM_PC_HIER',
'Standard',
'Standard',
'Standard Parent Child Hierarchy',
'SOLVED LEVEL-BASED');
cwm2_olap_dimension.SET_DEFAULT_DISPLAY_HIERARCHY ('APPS', 'HCP_DIM_PC', 'HCP_DIM_PC_HIER');
cwm2_olap_level.create_level(
'APPS',
'HCP_DIM_PC',
'ALL_PARENT_LVL',
'All Parent Child',
'All Parent Child',
'All Parent Child',
'All Parent Child Level');
cwm2_olap_level_attribute.create_level_attribute(
'APPS',
'HCP_DIM_PC',
'Short Description',
'ALL_PARENT_LVL',
'Short Description',
'Short Description',
'Short Description',
'Short Description',
TRUE);
cwm2_olap_level_attribute.create_level_attribute(
'APPS',
'HCP_DIM_PC',
'Long Description',
'ALL_PARENT_LVL',
'Long Description',
'Long Description',
'Long Description',
'Long Description',
TRUE);
cwm2_olap_level_attribute.create_level_attribute(
'APPS',
'HCP_DIM_PC',
'Grouping ID',
'ALL_PARENT_LVL',
'Grouping ID',
'Grouping ID',
'Grouping ID',
'HTB Grouping ID',
TRUE);
-- Add all levels one by one to dimension hierarchy. For top most level last parameter is null.
cwm2_olap_level.add_level_to_hierarchy(
'APPS',
'HCP_DIM_PC',
'HCP_DIM_PC_HIER',
'ALL_PARENT_LVL',
NULL);
BEGIN
cwm2_olap_table_map.removemap_dimtbl_hierlevel(
'APPS',
'HCP_DIM_PC',
'HCP_DIM_PC_HIER',
'ALL_PARENT_LVL');
cwm2_olap_table_map.removemap_DimTbl_HierLevelAttr(
'APPS', 'HCP_DIM_PC', 'Short Description', 'HCP_DIM_PC_HIER', 'ALL_PARENT_LVL', 'Short Description');
cwm2_olap_table_map.removemap_DimTbl_HierLevelAttr(
'APPS', 'HCP_DIM_PC', 'Long Description', 'HCP_DIM_PC_HIER', 'ALL_PARENT_LVL', 'Long Description');
cwm2_olap_table_map.removemap_DimTbl_HierLevelAttr(
'APPS', 'HCP_DIM_PC', 'Grouping ID', 'HCP_DIM_PC_HIER', 'ALL_PARENT_LVL', 'Grouping ID');
EXCEPTION
WHEN OTHERS THEN
dbms_output.put_line('Level map for ALL_PARENT_LVL not removed');
END;
-- Map ALL_PARENT_LVL level to dimension table. Last parameter is null since it is top most level
cwm2_olap_table_map.map_dimtbl_hierlevel(
'APPS',
'HCP_DIM_PC',
'HCP_DIM_PC_HIER',
'ALL_PARENT_LVL',
'APPS',
'PARENT_CHILD_SOLVED_VIEW',
'GID',
NULL);
-- one by one map all the level attributes to respective columns in the dimension table.
cwm2_olap_table_map.Map_DimTbl_HierLevelAttr(
'APPS',
'HCP_DIM_PC',
'Short Description',
'HCP_DIM_PC_HIER',
'ALL_PARENT_LVL',
'Short Description',
'APPS',
'PARENT_CHILD_SOLVED_VIEW',
'SHORT_DESCRIPTION');
cwm2_olap_table_map.Map_DimTbl_HierLevelAttr(
'APPS',
'HCP_DIM_PC',
'Long Description',
'HCP_DIM_PC_HIER',
'ALL_PARENT_LVL',
'Long Description',
'APPS',
'PARENT_CHILD_SOLVED_VIEW',
'LONG_DESCRIPTION');
cwm2_olap_table_map.Map_DimTbl_HierLevelAttr(
'APPS',
'HCP_DIM_PC',
'Grouping ID',
'HCP_DIM_PC_HIER',
'ALL_PARENT_LVL',
'Grouping ID',
'APPS',
'PARENT_CHILD_SOLVED_VIEW',
'GID');
-- Use cwm2_olap_validate.validate_dimension to validate the dimension
cwm2_olap_validate.validate_dimension('APPS', 'HCP_DIM_PC');
cwm2_olap_metadata_refresh.mr_refresh;
-- Rollback if any exception occurs during processing this script
EXCEPTION
WHEN OTHERS THEN
cwm_utility.dump_error;
errtxt := cwm_utility.get_last_error_description;
dbms_output.put_line('ERROR: ' || errtxt);
ROLLBACK;
RAISE;
END;
Script for Cube:-
declare
HCP_time_dim number;
errtxt varchar(60);
begin
cwm_utility.collect_garbage;
begin
cwm2_olap_cube.drop_cube('APPS', 'HCP_PC_CUBE');
exception
when others then
dbms_output.put_line('No HCP_PC_CUBE to drop');
end;
begin
cwm2_olap_catalog.drop_catalog('HCP_PC_CAT');
exception
when others then
dbms_output.put_line('No HCP_PC_CAT to drop');
end;
CWM2_OLAP_CUBE.Create_Cube('APPS', 'HCP_PC_CUBE', 'Parent Child Cube', 'Parent Child Cube','Parent Child Cube');
cwm2_olap_cube.add_dimension_to_cube('APPS', 'HCP_PC_CUBE','APPS', 'HCP_DIM_PC');
cwm2_olap_measure.create_measure('APPS', 'HCP_PC_CUBE', 'HCP_PC_MEASURE', 'PC Measure','PC Measure', 'PC Measure Fact');
cwm2_olap_table_map.map_facttbl_levelkey('APPS','HCP_PC_CUBE','APPS','HCP_PC_FACT','ET', 'DIM:APPS.HCP_DIM_PC/HIER:HCP_DIM_PC_HIER/GID:GID/LVL:ALL_PARENT_LVL/COL:CHILD3;');
cwm2_olap_table_map.Map_FactTbl_Measure('APPS', 'HCP_PC_CUBE','HCP_PC_MEASURE', 'APPS', 'HCP_PC_FACT', 'MEASURE_COL', 'DIM:APPS.HCP_DIM_PC/HIER:HCP_DIM_PC_HIER/GID:GID/LVL:CHILD3/COL:SHORT_DESCRIPTION;');
cwm2_olap_catalog.create_catalog('HCP_PC_CAT', 'Parent Child Catalog');
cwm2_olap_catalog.add_catalog_entity('HCP_PC_CAT', 'APPS', 'HCP_PC_CUBE', 'HCP_PC_MEASURE');
cwm2_olap_validate.validate_cube('APPS', 'HCP_PC_CUBE','DEFAULT','YES');
cwm2_olap_metadata_refresh.mr_refresh;
exception
when others then
cwm_utility.dump_error;
errtxt := cwm_utility.get_last_error_description;
dbms_output.put_line('ERROR: ' || errtxt);
rollback;
raise;
END;
My Fact Table is :-
DROP TABLE HCP_PC_FACT CASCADE CONSTRAINT;
CREATE TABLE HCP_PC_FACT (
SHORT_DESCRIPTION VARCHAR2(30) NOT NULL,
GID NUMBER NOT NULL,
CHILD1 VARCHAR2(30) NOT NULL,
CHILD2 VARCHAR2(30) ,
CHILD3 VARCHAR2(30) ,
MEASURE_COL NUMBER NOT NULL);
Data in Fact Table:-
insert into HCP_PC_FACT values('Compliant',0,'All','Eligible','Compliant', 100);
insert into HCP_PC_FACT values('Non-Compliant',0,'All','Eligible','Non-Compliant', 200);
insert into HCP_PC_FACT values('Eligible',1,'All','Eligible',null, 300);
insert into HCP_PC_FACT values('Ineligible',1,'All','Ineligible',null, 400);
insert into HCP_PC_FACT values('All',3,'All',null,null, 500);
I am not sure how to create level, level attr, dim attr for such dim.
All CWM2 validation API shows that my all dims, cubes are valid but when I try to create presentation thru JDev it hangs after selecting Parent-Child Measure.
Any complete working exapmle will be helpful.
P.S. One more query I have can we have one solved and one un-solved dim in the same cube/measure?
regds
Prakash

How to create one master table and two detail for it

I have one table , imagine it like mastertable( empid,deptid );
and two different tables like employeetable(empid ) , departmenttable ( deptid )....
I dont have any relation on database side. I need to create view link and ı need to use only one master table for two detail tables.
How can ı manage this scenerio ?
thanks...

yes Shay ı really want to use two detail table in one UI as you suggest in your blog. But in that scenerio probably tables have link in database side with foreign key. My detail tables dont have any connection in database side with my master table. How can ı link them under one mastertableVO ?
I am really sorry about my bad explanation. I am a newbie and probably ı dont know the correct words to tell my problem.
Thanks for your time...

How to create the custom table?

Hi, how to create the custom table and how to integrate the table with defferent R/3?
my requiremnt is i have to create the two tables and those i have to integrate with the existed R/3 and using those R/3 i have to update my custom tables .....can give me some idea?
Tks
DPk

how to create the custom table
There are two approach in creating a table.
1. Bottom-up approach
2. Top-down approach.
Both are valid and you can choose which approach is suitable for you. I always use the bottom-up approach. Here are the steps to create the tables with this approach.
1. SE11 will take you to the DDIC and enter the name of the new table to be created. Let us say Zname. Click create.
2. Enter the short discription of the table and enter the field of the table. If it is primary key and you have to check the box.
3. Enter the data element and double click it, you will be asked to save and will take you to data element discription page. Enter the short discription of the data element and enter the information of domain like the length of field and type of field.
4. If you wanted to use the existing domain then its fine, or else, you have to create one. Enter the domain name in the data element page and double click it. Page will ask to save and jump to domain creation page.
5. In the domain page, you have to save the information which you have already given in the data elements page and check it. Before going to data element page, you have to activate the domain.
6. Go to data element page and save, check and activate.
7. Go to main table page and save, check, and activate.
8. Also, you have to save the technical settings of the table.
The table is now ready for operation. You can use it in your program or you can use it to enter information.
Check table: It is the table which will have all the information about the Foreign keys which are the primary keys in the check table.
It can be created by creating the foreign key from the main table. Click foreign key in the main table and it will take you to a page which will ask for table name and field to which foreign key relation has to be associated. Enter the information and you can create the check table automatically.
SM30 is used for maintenance of the table, that is to realease the errors occured during the creation of the table.
how to integrate the table with defferent R/3
Transport the Table to the another server/client/qas/prd
Kanagaraja L

How to create a cluster on existing table

how to create a cluster on existing table

user8949393 wrote:
how to create a cluster on existing tableAFAIK you can't. You have to create the cluster from scratch, something like
--cluster key can be just one column also
CREATE CLUSTER s_emp_dept_ic (deptno NUMBER(7), dname varchar2(30));
CREATE TABLE emp(
DEPTNO NUMBER(7),
DNAME VARCHAR2(30),
EMPNO NUMBER(4),
ENAME VARCHAR2(30)
--cluster clause puts table in cluster. Deptno, dname are table columns in
--cluster key
CLUSTER s_emp_dept_ic (deptno,dname);
--a cluster index must be created before any data is inserted
--the index columns used come from the cluster key from CREATE CLUSTER
CREATE INDEX s_emp_idx ON CLUSTER s_emp_dept_ic;

How to create OSB cluster

HI All ,
I have to create an OSB cluster across different machines .
Can I get a detailed steps of how to create a cluster across machines using node manager .
I am using osb 11gR2 .Please let me know the exact steps .

You can bundle two or more wires together using the 'bundle function' - the output is a cluster. This is the top example.
The other way is drop the constand cluster and drag any constants (like the numeric and string) into the cluster. This is the lower example in the VI snippet. You can also do this on the frontpanel - drop the cluster constant on the frontpanel and drag any controls or indicators into it. They have to be controls or indicators - you can't have a mix of both.
Also in case you are not familiar with the concept if you are working with big clusters you should 'type def' them. In LV2011 you do this by right-clicking on the block diagram and clicking 'make type def'. What this does is creates a separate file where the new cluster (or any other type of control) is saved. Then if you change the cluster - say add a boolean alogn with the numeric and string - the change happens and is propogated through your program. This stops you getting broken wires when you have two clusters wired together, you change one and not the other.
Regards,
Dave

How was created the cluster with keys in example: Sim Phone.vi

Hello all
I have LV 7.1.1
I have found the example: Sim Phone.vi
And I don't know how was created the cluster with keys?
Best regards
Iskander

It's just like any other cluster you create. Put a cluster container on the front panel and insert some Booleans. the actual Booleans are on the classic controls palette. The border of the cluster is also colored transparent with the paintbrush on the Tools palette.

How to Create Event polling table

hi,
1)How to Create Event polling table
2) wahts RPD stands for.
3) when we are prefer Dynamic variables.
thanks.
raj

1) http://obiee101.blogspot.com/2008/07/obiee-managing-cache-emptyingpurging.html
2) Repository Project Design ?
- More than likely the extension RPD was not used by anything else when Siebel Analytics first started using it, no doubt the 'RP' is repository, so use 'Definition' or 'Design' as you like. Im pretty sure there is nothing in the documentation but i've not checked, maybe you could check and let us know?
3) Dynamic variables would be something like 'CURRENT_MONTH' where the same query does not need to fire per user (ie SESSION variable) but needs to be periodically refreshed. Another use of you dynamic variable might be 'LAST_ETL_DATE' or somethng similar which might implement with your event polling table. By including the Variable within a Business Model, all cache for the Business Model is purged whenever the Variable's value changes.

How to create a temp table in the memory, not in disk?

in sql server, you can create a temp table in the memory instead of disk,
then you can do the insert, delete,update and select on it.
after finishing, just release it.
in Oracle,
I am wonderfing how to create a temp table in the memory, not in disk?
thanks,

Thanks for rectifying me Howard.
I just read your full article on this too and its very well explained here:
http://www.dizwell.com/prod/node/357
Few lines from your article
It is true, of course, that since Version 8.0 Oracle has provided the ability to create a Keep Pool in the Buffer Cache, which certainly sounds like it can do the job... especially since that word 'keep' is used again. But a keep pool is merely a segregated part of the buffer cache, into which you direct blocks from particular tables (by creating them, or altering them, with the BUFFER POOL KEEP clause). So you can tuck the blocks from such tables out of the way, into their own part of the buffer cache... but that is not the same thing as guaranteeing they'll stay there. If you over-populate the Keep Pool, then its LRU mechanism will kick in and age its contents out just as efficiently as an unsegregated buffer cache would.
Functionally, therefore, there can be no guarantees. The best you can do is create a sufficiently large Keep Pool, and then choose the tables that will use it with care such that they donâ€™t swamp themselves, and start causing each other to age out back to disk.
Thanks and Regards

How to create variant for table/view ?

Hi,
When I go through SM30, I find a radio button called variant. I don't know the effect.
Can anyone tell me how to create variant for table / view ?
I want to know when we need to create variant for table/view.
Best regards,
Chris Gu

hi ,
Whenever you start a program in which selection screens are defined, the system displays a set of input fields for database-specific and program-specific selections. To select a certain set of data, you enter an appropriate range of values.
For further information about selection screens, refer to Selection Screens in the ABAP User's Guide.
If you often run the same program with the same set of selections (for example, to create a monthly statistical report), you can save the values in a selection set called a variant
Procedure
To create a new variant:
       1.      On the ABAP Editor initial screen, enter the name of the program for which you want to create a variant, select Variants, and choose Change.
       2.      On the variant maintenance initial screen, enter the name of the variant to be created.
Note the naming convention for variants (see below).
       3.      Choose Create.
If the program has more than one selection screen, a dialog box for screen assignment appears. The dialog box does not appear if the program only has one selection screen. The selection screen appears in this case.
       4.      If there is more than one selection screen, select the screens for which you want to create the variant
5.      Choose Continue.
The (first) selection screen for the report appears.
If your program has more than one selection screen, use the scroll buttons in the left-hand corner of the application toolbar to navigate between them and to fill the fields with values. If you keep scrolling forwards, the Continue button appears on the last selection screen.
       6.      Enter the desired selection values, including multiple selection and dynamic selection.
       7.      Choose Continue.

HOW TO create a temp table or a record group at run time

i have a a tabular form and i dont want to allow the user entering duplicate
records while he is in insert mode and the inserted records are new and not exsisting in the database.
so i want to know how to create a temp table or a record group at run time to hold the inserted valuse and compare if they are exsiting in previous rows or no.
please help!

As was stated above, there are better ways to do it. But if you still wish to create a temporary block to hold the inserted records, then you can do this:
Create a non-database block with items that have the same data types as the database table. When the user creates a new record, insert the record in the non-database block. Then, before the commit, compare the records in the non-database block with those in the database block, one at a time, item by item. If the record is not a duplicate, copy the record to the database block. Commit the records, and delete the records in the non-database block.

How to create a booking table (make online reservation)

Hi everyone,
I'm just wondering if any of you know how to create a booking
table, like a booking seat for an airplane... I have to do the
booking table as I'm doing a Japanese Restaurant website for my
project.. At the moment, I'm using PHP, MySQL and HTML..
Could anyone help me, please?
Cheers,
Nova

You first need to check with your host to see which type of
server side
scripting language they support. If they support PHP, try,
http://www.jellyform.com/
Shane H
[email protected]
http://www.avenuedesigners.com
=============================================
Blog:
http://avenuedesigners.com/blog/
Web dev articles, photography, and more:
http://sourtea.com
=============================================
Proud GAWDS member
http://www.gawds.org/showmember.php?memberid=1495
Delivering accessible websites to all ...
=============================================
"mastacraft" <[email protected]> wrote in
message
news:f3pote$d16$[email protected]..
> Hello,
>
> I need to create a booking form for a website- So wen
they fill out form
> for
> bookings. Should have tab for club appearance. Magazine
ads. Etc It needs
> to
> lead to this email : [email protected]
>
> I'm really not sure how the best way is to do this, i
understand it's
> probably
> a really simple process.
>
> Regards,
>

How to create a stored procedure and use it in Crystal reports

Hi All,
Can anyone explain me how to create a stored procedure and use that stored procedure in Crystal reports. As I have few doubts in this process, It would be great if you can explain me with a small stored proc example.
Thanks in advance.

If you are using MSSQL SERVER then try creating a stored procedure like this
create proc Name
select * from Table
by executing this in sql query analyzer will create a stored procedure that returns all the data from Table
here is the syntax to create SP
Syntax
CREATE PROC [ EDURE ] procedure_name [ ; number ]
    [ { @parameter data_type }
        [ VARYING ] [ = default ] [ OUTPUT ]
    ] [ ,...n ]
[ WITH
    { RECOMPILE | ENCRYPTION | RECOMPILE , ENCRYPTION } ]
[ FOR REPLICATION ]
AS sql_statement [ ...n ]
Now Create new report and create new connection to your database and select stored procedure and add it to the report that shows all the columns and you can place the required fields in the report and refresh the report.
Regards,
Raghavendra
Edited by: Raghavendra Gadhamsetty on Jun 11, 2009 1:45 AM

How to create a new variant and a job sheduled to use it for the ......

How to create a new variant and a job sheduled to use it for the exisisting programs

Hi
1. The ALV Grid Control is a tool with which you can output non-hierarchical lists in a
standardized format. The list data is displayed as a table on the screen.
The ALV Grid Control offers a range of interactive standard list functions that users need
frequently (find, sort, filter, calculate totals and subtotals, print, print preview, send list,
export list (in different formats), and so on. These functions are implemented in the
proxy object class. You as the programmer have the possibility to turn off functions not
needed. In most cases the implementations of the standard functions provided by the
control are sufficient. However, if required, you can adjust these implementations to
meet application-specific needs.
You can add self-defined functions to the toolbar, if necessary.
The ALV Grid Control allows users to adjust the layout of lists to meet their individual
requirements (for example, they can swap columns, hide columns, set filters for the
data to be displayed, calculate totals, and so on). The settings (list customizing) made
by a specific user are called a display variant. Display variants can be saved on a userspecific
or on a global basis. If such display variants exist for a list, they can be offered
to the user for selection. If a display variant is set as the default variant, the associated
list is always displayed based on the settings of this variant.
2. REUSE_ALV_LIST_DISPLAY
REUSE_ALV_GRID_DISPLAY
REUSE_ALV_FIELDCATALOG_MERGE
REUSE_ALV_COMMENTARY_WRITE
3. Use of Field Catalog is to determines the technical properties & add formating information of the column.
6. all the definition of internal table, structure, constants are declared in a type-pool called SLIS.
7.fieldcat-fieldname
fieldcat-ref_fieldname
fieldcat-tabname
fieldcat-seltext_m
5. Form user_command using r_ucomm like sy-ucomm rs_selfield type slis_selfield.
Sap provides a set of ALV (ABAP LIST VIEWER) function modules which can be put into use to embellish the output of a report. This set of ALV functions is used to enhance the readability and functionality of any report output. Cases arise in sap when the output of a report contains columns extending more than 255 characters in length.
In such cases, this set of ALV functions can help choose selected columns and arrange the different columns from a report output and also save different variants for report display. This is a very efficient tool for dynamically sorting and arranging the columns from a report output.
The report output can contain up to 90 columns in the display with the wide array of display options.
<b>The commonly used ALV functions used for this purpose are;</b>
1. REUSE_ALV_VARIANT_DEFAULT_GET
2. REUSE_ALV_VARIANT_F4
3. REUSE_ALV_VARIANT_EXISTENCE
4. REUSE_ALV_EVENTS_GET
5. REUSE_ALV_COMMENTARY_WRITE
6. REUSE_ALV_FIELDCATALOG_MERGE
7. REUSE_ALV_LIST_DISPLAY
8. REUSE_ALV_GRID_DISPLAY
9. REUSE_ALV_POPUP_TO_SELECT
Purpose of the above Functions are differ not all the functions are required in all the ALV Report.
But either no.7 or No.8 is there in the Program.
<b>
How you call this function in your report?</b>
After completion of all the data fetching from the database and append this data into an Internal Table. say I_ITAB.
Then use follwing function module.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
I_CALLBACK_PROGRAM = 'Prog.name'
I_STRUCTURE_NAME = 'I_ITAB'
I_DEFAULT = 'X'
I_SAVE = 'A'
TABLES
T_OUTTAB = I_ITAB.
IF SY-SUBRC <> 0.
WRITE: 'SY-SUBRC: ', SY-SUBRC .
ENDIF.
ENDFORM. " GET_FINAL_DATA
The object F_IT_ALV has a field, the activity ACTVT, which can
contain four permitted values: 01, 02, 03 and 70. Each of the
activities 01, 02 and 70 controls the availability of particular
functions (in the menu and the toolbar) of the ALV line item list:
a) 01: "Settings -> Display variant -> Save..."
b) 02: "Settings -> Display variant -> Current..." and
"Settings -> Display variant -> Current header rows "
c) 70: "Settings -> Display variant -> Administration..."
Activity 03 corresponds to the minimum authorization, which is the
most restricted one: The user can only select layouts which have
been configured already. In particular, all of the other functions
named above are inactive with activity 03.
Now if you want to permit a user to change the column selection and
the headers as well as to save the layout thus created, for example,
but if you do not want to permit the user to administrate the
layouts, you grant him or her the authorization for activities 01
and 02.
Check this link it will be mosty usefull for u
http://www.sap-img.com/fu017.htm
Reward all helpfull answers
Regards
Pavan

How to create a dynamic table were the JTable columns keep varying

How to create a dynamic table were the JTable columns keep varying based on the input to the jtable

Oooh, I lied. DefaultTableModel has an API for adding and
removing columns. I didn't know that. You should have read
the API.
As for preferring to extend AbstractTableModel rather than
DefaultTableModel, I think it's more correct. DefaultTableModel
is a simple implementation of Abstract for basic cases. It isn't
intended to be extended. I figure most people extending
DefaultTableModel are also extending JFrame, JPanel, and Thread
instead of encapsulating the first two and implementing
Runnable for the third.

How to create a cluster table and cluster view?

Similar Messages

Maybe you are looking for