Add new field in External Definition

Hi,
I have a scenario where I have to add just one extra field in in the Outbound DT.
In our case we do not have DT, but External Definition say BAPI_XYZ.xsd
I export the .xsd file from Tools --> Export Original Document (Category: xsd, Messages:From All available global elements" )and the BAPI_XYZ.xsd is saved in my desktop.
I just add this piece of code in the place where I need it.
<xsd:element name="PLANNING_VER" minOccurs="0"><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength Value="8"/></xsd:restriction></xsd:simpleType></xsd:element>
After this I import the XSD and save it undre external definition. But when I open this new xsd in the message mapping I get the error "BAPI_XYZ has No messages" and the structure is not loaded.
In the existing External definition when I move to the "Messages" Tab I can see an entry "BAPI_XYZ.Response" . The same is not available when I add the extra field and impor the new XSD
Can some one pls help??
Regards
Prasanna

Hi Prasanna 
There is an issue with XSD. Value = "8" should be small v.
Please insert the below code at correct position.
<xsd:element name="PLANNING_VER" minOccurs="0">
   <xsd:simpleType>
      <xsd:restriction base="xsd:string">
         <xsd:minLength value="8" />
      </xsd:restriction>
   </xsd:simpleType>
</xsd:element>
After that check that XSD is well formed and valied or not. You can use Validator for XML Schema W3C [Link|http://www.w3.org/2001/03/webdata/xsv] , XML editor (XMLspy), Eclipse, NetBeans.
Regards,
Raghu_Vamsee

Similar Messages

  • IDOC - add new field in in existing segment definition

    Hi,
    For segement type say Z1MARA1 if we need to add a new field in segement definition say Z2MARA1 SAP is not allowing to add new field if we tried to cancelled the realsed 30E it not allowing since the SAP realease which we are working is 640 so only we can create new segement defination with version Z2MARA1001 with new field added but issues is that the partner Profile for outbound parameters the Segment release in IDOc Type is 31I so if we change this segment release in IDOC type to new version ie., 640 then it will pick all the new segement associated with it due to which the the format in which we pass the segements to third party will change so is there any way to use the existing segment definition which is release 30E & add addition field to it. Only one way I found is that when i try to cancel the released message is trigger so in the debug if I make it success it allows to add new field in existing segment definition but which is wrong way of doing is there any way we can used same segment definition & add new field without adding new version & new released.
    Thanks in advance.
    Rajeev

    Varma,
    I know that we can add new segement with new version my question is existing segement definition can we add a new filed because in partner profile we specified release 31i so even we create new segement type then version will be 640 so it will not pick the latest version.
    Thanks
    Rajeev

  • How add new field in layout in RDF using XML report definition

    Hi, ALL
    Do you know how add new field in layout of existing report in RDF using XML report definition. If I try change anything in RDF layout, layout which defined in XML override report layout.

    hello,
    in reports 6i we have this limitation, that you can not add a field to a report unless you re-default the whole report, as we do not support positioning-information in the customization file.
    regards,
    the oracle reports team

  • Address book model is not respected when I add new fields

    Hello,
    If I add new fields in the model of my adress book. AddressBook display does not comply with the specified model.
    For example, after father, mother and joint, I added the following fields child 1, grand-child 1, child 2, grand-child 2, child 3, grand-child 3, child 4, grand-child 4, in order to have descendants of my friend or family.
    The result is :
    child 3 : Oscar
    child 4 : Anatole
    child 2 : Victor
    child 5 : Constantin
    child 1 : Aline
    Please note that I entered the 5 children in the good order : Aline, Victor, Oscar, Anatole, Constantin.
    An other example can be completely different with children and grand-children mixed !
    To be complete, I can say that in Mac OS X 10.4 address book was running correctly, but is no longer running in 10.5 nor 10.6.7
    Best regards
    Bergama

    The iPad can't be infected with a virus - by the definition of a virus being a malicious program that replicates itself across your operating system and other programs. It can be infected with malware, however that usually only happens when a user taps on a link, or actively does something.
    Since the iPad can't run flash or java (?)(all or most kinds of java) then it's relatively secure.
    You're probably fine.
    The iPad's operating system is different enough from Mac's or PC's that even if you do tap on a virus it can't run...the malicious code is speaking a language that the iPad can't understand.

  • Urgent :crm_ic web client adding new field - customer external number-BPEXT

    HI
    I want to add the field <b>customer external number(data element- bpext)</b> is available as a standard  field in  <b>bp transaction</b> , under indentification tab I am trying to bring the same field into the <b>identify account-CRM-IC BSP Application</b>
    when I am trying to do this , I nee to know the below information
    <b>Attribute name
    property name
    context class</b>
    can you help me in Identifying this values which I feel is must for adding the field to the bsp application CRM_IC.
    thanks in advance
    Message was edited by: madhu satya rajasekhar bobbadi

    Hi,
    Following are the steps to add new fields to the existing view.
    - Create a new controller class (ZCL..) with original view class as super class
    - Create new BSP application with View and Controller
    - Attach the above Z class to the view and controller created and activate the BSP appln.
    - Go to transaction BSP_WD_WORKBENCH and type your BSP appln.
    - Expand your controller and at the Context class use Wizard to create new context node and bind this to Custom Controller class available.
    This whole process requires complte understanding of View, Controller, Custom controller and basic custom modifications to IC Web Frame work.
    Kunda Krishna Kishore

  • Screen Exit - add new field (VBAK-VBELN)  in VC01N

    hi friends,
    how to add new field (VBAK-VBELN) in VC01N tcode
    Tcode: VC01N Sales Activity
    Table: VBKA
    Field: VBELN
    Requirement: New field in screen ( VC01N )
    Description:
    Prospective projects are to be linked to the sales activities whenever they are created. 
    Prospective Project VA12
    Table: VBAK
    Field: VBELN
    Doc Type: ZPRO
    Doc Category: A
    Place the new field VBAK-VBELN under the u2018Commentu2019n in the VC01N.
    urgent plz reply
    thanks and regards
    Poorna
    Edited by: poornambika sivaramakrishnan on Nov 21, 2008 11:28 AM

    Hi...
    You can definitely do it...provided if screen exit is there ...
    Below is the program to find the exit whether present or not in your transaction,
    Just give your tcode in the program , it will show all the exits in your transaction.
    Regards
    RachelArun
    TABLES : tstc, "SAP Transaction Codes
    tadir, "Directory of Repository Objects
    modsapt, "SAP Enhancements - Short Texts
    modact, "Modifications
    trdir, "System table TRDIR
    tfdir, "Function Module
    enlfdir, "Additional Attributes for Function Modules
    tstct. "Transaction Code Texts
    *& Variables
    DATA : jtab LIKE tadir OCCURS 0 WITH HEADER LINE.
    DATA : field1(30).
    DATA : v_devclass LIKE tadir-devclass.
    *& Selection Screen Parameters
    SELECTION-SCREEN BEGIN OF BLOCK a01 WITH FRAME TITLE text-001.
    SELECTION-SCREEN SKIP.
    PARAMETERS : p_tcode LIKE tstc-tcode OBLIGATORY.
    SELECTION-SCREEN SKIP.
    SELECTION-SCREEN END OF BLOCK a01.
    *& Start of main program
    START-OF-SELECTION.
    u2022     Validate Transaction Code
    SELECT SINGLE * FROM tstc
    WHERE tcode EQ p_tcode.
    u2022     Find Repository Objects for transaction code
    IF sy-subrc EQ 0.
    SELECT SINGLE * FROM tadir
    WHERE pgmid = 'R3TR'
    AND object = 'PROG'
    AND obj_name = tstc-pgmna.
    MOVE : tadir-devclass TO v_devclass.
    IF sy-subrc NE 0.
    SELECT SINGLE * FROM trdir
    WHERE name = tstc-pgmna.
    IF trdir-subc EQ 'F'.
    SELECT SINGLE * FROM tfdir
    WHERE pname = tstc-pgmna.
    SELECT SINGLE * FROM enlfdir
    WHERE funcname = tfdir-funcname.
    SELECT SINGLE * FROM tadir
    WHERE pgmid = 'R3TR'
    AND object = 'FUGR'
    AND obj_name = enlfdir-area.
    MOVE : tadir-devclass TO v_devclass.
    ENDIF.
    ENDIF.
    u2022     Find SAP Modifactions
    SELECT * FROM tadir
    INTO TABLE jtab
    WHERE pgmid = 'R3TR'
    AND object = 'SMOD'
    AND devclass = v_devclass.
    SELECT SINGLE * FROM tstct
    WHERE sprsl EQ sy-langu
    AND tcode EQ p_tcode.
    FORMAT COLOR COL_POSITIVE INTENSIFIED OFF.
    WRITE:/(19) 'Transaction Code - ',
    20(20) p_tcode,
    45(50) tstct-ttext.
    SKIP.
    IF NOT jtab[] IS INITIAL.
    WRITE:/(95) sy-uline.
    FORMAT COLOR COL_HEADING INTENSIFIED ON.
    WRITE:/1 sy-vline,
    2 'Exit Name',
    21 sy-vline ,
    22 'Description',
    95 sy-vline.
    WRITE:/(95) sy-uline.
    LOOP AT jtab.
    SELECT SINGLE * FROM modsapt
    WHERE sprsl = sy-langu AND
    name = jtab-obj_name.
    FORMAT COLOR COL_NORMAL INTENSIFIED OFF.
    WRITE:/1 sy-vline,
    2 jtab-obj_name HOTSPOT ON,
    21 sy-vline ,
    22 modsapt-modtext,
    95 sy-vline.
    ENDLOOP.
    WRITE:/(95) sy-uline.
    DESCRIBE TABLE jtab.
    SKIP.
    FORMAT COLOR COL_TOTAL INTENSIFIED ON.
    WRITE:/ 'No of Exits:' , sy-tfill.
    ELSE.
    FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.
    WRITE:/(95) 'No User Exit exists'.
    ENDIF.
    ELSE.
    FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.
    WRITE:/(95) 'Transaction Code Does Not Exist'.
    ENDIF.
    u2022     Take the user to SMOD for the Exit that was selected.
    AT LINE-SELECTION.
    GET CURSOR FIELD field1.
    CHECK field1(4) EQ 'JTAB'.
    SET PARAMETER ID 'MON' FIELD sy-lisel+1(10).
    CALL TRANSACTION 'SMOD' AND SKIP FIRST SCREEN.

  • How to add new fields in Reduced message ( in BD53 )

    Hi Experts,
    How to add new fields in Reduced message ( in BD53 ), when the required field iis available in Table or Structure and need to be added in BD53 so that we can ALE.
    Thanks,
    Ninad

    Hello,
    I think of something like:
    First, you create extension, with transaction WE30.
    Then, reduce your idoc, your extension should also be proposed.
    Do not forget to add this extension in outbound we82, and/or we57 in inbound, and WE20, and find BTE or exit to populate extension.
    regards.
    F.S.

  • PLz Help me its urgent, how to add new field in mm01 basic data screen

    Hi everyone,
         plz tell me how to add new field in mm01 basic data screen,i added that field in basic data screen but when i create a material the data for that field will not save in database table.
    Thanks,
    murali.

    Hi Murali,
    when created added a field on the screen by using user exit then after that you have add the field in main table where you will be getting these table in the userexit only, please make sure about this. And i am sure defenitly it will get updated in to the table.
    reward if useful.
    thanks
    abdulsamee.

  • Add new field to HR PCR forms

    Hi All,
    We are trying to enhance adobe form for scenario SRQ1.
    We want to add some new fields to tha form.
    For that we have copied the existing standard form to zform.
    We have implemented the zinterface too.
    To add new field on form we created as an import parameter in form interface.
    We added to context of adobe form and on layout.
    But we are not getting that field in 'special_data' table in BADI implementation of SRQ1.
    Please let me know how and where we should write a code to add new field in 'special_data' table.
    Thanks & Regards,
    Nilesh.

    Thanks Suresh,
    We have added it to characteristics of SRQ1 scenario and it's working.
    But now we are facing problem in adding data to additional_data table.
    Can you tell us something about it.
    Actually in set_additional_values method of BADI we are adding data to additional_data table but on form it is not reflecting.
    Please advice.

  • Not able to add new fields in Content cube

    Hi all
    I think I had this post earlier too, but I haven't been able to add new fields in a Business content cube. I added them in the cube but I am not sure how to update the datasource, infosource, update rule etc. in proper manner.
    Please write me the details or send me in my email at
    [email protected] , I would be so happy for your help.
    Thank you in Advance.
    Sajita

    Roberto;
    I am doing the third options. feeding data from source system and I tried to add them into the infosource it didn't work. In this case, do you think I need to update the data sourece too, if so how do I do that it's function module. data source I am using is '0ME_ISM_AM_REV_1'. So please give me some more details. Thank you.
    Sajita

  • I want to add new field to this list

    hi all,
    i want to add new field to this list.
    kostenstelle from table zfmkstel
    *& Report  ZFM_MOBLIST                                                 *
    REPORT  ZFM_MOBLIST.
    TABLES: zfm_handy , pa0002.
    TYPE-POOLS : slis.
    DATA: g_repid LIKE sy-repid,
          gs_print            TYPE slis_print_alv,
          gt_list_top_of_page TYPE slis_t_listheader,
          gt_list_end_of_page TYPE slis_t_listheader,
          gt_events           TYPE slis_t_event,
          gt_sort             TYPE slis_t_sortinfo_alv,
          gs_layout           TYPE slis_layout_alv,
          gt_fieldcat         TYPE slis_t_fieldcat_alv,
          fieldcat_ln LIKE LINE OF gt_fieldcat,
          col_pos TYPE i.
    *DATA : BEGIN OF it_moblist OCCURS 0.
           INCLUDE STRUCTURE zfm_handy.
    *DATA :  nachn  TYPE  pa0002-nachn,     
           vorna TYPE  pa0002-vorna,
         END OF it_moblist.
    DATA : BEGIN OF IT_MOBLIST OCCURS 0,
           TELNUM TYPE ZFM_HANDY-TELNUM,
           KARTNR TYPE ZFM_HANDY-KARTNR,
           ZUTART TYPE ZFM_HANDY-ZUTART,
           PERNR TYPE ZFM_HANDY-PERNR,
           nachn  TYPE pa0002-nachn,
           VORNA TYPE pa0002-vorna,
           ZDATE TYPE ZFM_HANDY-ZDATE,
           PINNR TYPE ZFM_HANDY-PINNR,
           PUKNR TYPE ZFM_HANDY-PUKNR,
           TARIF1 TYPE ZFM_HANDY-TARIF1,
           TARIF2 TYPE ZFM_HANDY-TARIF2,
           TARIF3 TYPE ZFM_HANDY-TARIF3,
           GTYPE TYPE ZFM_HANDY-GTYPE,
           IMEI TYPE ZFM_HANDY-TARIF1,
            twincard type zfm_handy-twincard,
            twinbill type zfm_handy-twinbill,
            einbau type zfm_handy-einbau,
            beschr type zfm_handy-beschr,
            text1 type zfm_handy-text1,
             text2 type zfm_handy-text2,
              text3 type zfm_handy-text3,
              end of it_moblist.
    DATA : BEGIN OF IT_zfm_handy OCCURS 0,
         TELNUM TYPE ZFM_HANDY-TELNUM,
         KARTNR TYPE ZFM_HANDY-KARTNR,
         ZUTART TYPE ZFM_HANDY-ZUTART,
         PERNR TYPE ZFM_HANDY-PERNR,
         ZDATE TYPE ZFM_HANDY-ZDATE,
         PINNR TYPE ZFM_HANDY-PINNR,
         PUKNR TYPE ZFM_HANDY-PUKNR,
         TARIF1 TYPE ZFM_HANDY-TARIF1,
         TARIF2 TYPE ZFM_HANDY-TARIF2,
         TARIF3 TYPE ZFM_HANDY-TARIF3,
         GTYPE TYPE ZFM_HANDY-GTYPE,
         IMEI TYPE ZFM_HANDY-TARIF1,
          twincard type zfm_handy-twincard,
          twinbill type zfm_handy-twinbill,
          einbau type zfm_handy-einbau,
          beschr type zfm_handy-beschr,
          text1 type zfm_handy-text1,
           text2 type zfm_handy-text2,
            text3 type zfm_handy-text3,
            end of it_zfm_handy.
    *DATA : BEGIN OF it_zfm_handy OCCURS 0.
           INCLUDE STRUCTURE zfm_handy.
    *DATA END OF it_zfm_handy.
    DATA : BEGIN OF it_pa0002 OCCURS 0,
            pernr TYPE pa0002-pernr,
            nachn   TYPE pa0002-nachn,     
           vorna     TYPE pa0002-vorna,
           pernr TYPE pa0002-pernr,
           END OF it_pa0002.
    INITIALIZATION.
      g_repid = sy-repid.
      PERFORM print_build USING gs_print.      "Print PARAMETERS
    START-OF-SELECTION.
      PERFORM data_selection.
      PERFORM build_fieldcat.
      PERFORM eventtab_build CHANGING gt_events.
      PERFORM comment_build  CHANGING gt_list_top_of_page.
      PERFORM call_alv.
    *&      Form  TOP_OF_PAGE
    FORM top_of_page.
      CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
        EXPORTING
          it_list_commentary = gt_list_top_of_page.
      WRITE: sy-datum, 'Page No', sy-pagno RIGHT-JUSTIFIED.
    ENDFORM.                    "TOP_OF_PAGE
    *&      Form  END_OF_PAGE
    FORM end_of_page.
      WRITE: /.
      WRITE AT (sy-linsz) sy-pagno CENTERED.
    ENDFORM.                    "END_OF_PAGE
    ### PRINT SETTINGS
    FORM print_build USING ls_print TYPE slis_print_alv.
      ls_print-print              = ' '. "PRINT IMMEDIATE
      ls_print-no_print_selinfos  = 'X'. "NO SELECTION INFO
      ls_print-no_coverpage       = ' '. "NO COVER PAGE
      ls_print-no_new_page        = ' '. "NO NEW PAGE
      ls_print-no_print_listinfos = 'X'. "NO PRINT LIST INFO
      ls_print-reserve_lines      = 2.   " FOOTERLINE
    ENDFORM.                    "PRINT_BUILD
    *&      Form  data_selection
          text
    -->  p1        text
    <--  p2        text
    FORM  data_selection .
      data : n(8) type n.
      SELECT * FROM
                 zfm_handy
           INTO CORRESPONDING FIELDS OF TABLE it_zfm_handy where pernr ne space.
      IF NOT it_zfm_handy[] IS INITIAL.
        loop at it_zfm_handy.
          n = it_zfm_handy-pernr.
          it_zfm_handy-pernr = n.
          modify it_zfm_handy.
        endloop.
        SELECT  pernr  nachn        
               vorna     
         FROM  pa0002
         INTO TABLE it_pa0002
         FOR ALL ENTRIES IN it_zfm_handy
         WHERE pernr = it_zfm_handy-pernr and endda = '99991231'.
       SELECT  pernr  nachn        
              vorna     
        FROM  pa0002
        INTO TABLE it_pa0002
        FOR ALL ENTRIES IN it_zfm_handy
        WHERE pernr = it_zfm_handy-pernr and begda le sy-datum and endda ge sy-datum.
      ENDIF.                              " not it_zfm_handy
      LOOP AT it_zfm_handy.
        MOVE-CORRESPONDING  it_zfm_handy TO it_moblist.
        clear it_pa0002.
        READ TABLE it_pa0002  WITH KEY pernr = it_zfm_handy-pernr.
        if sy-subrc = 0.
          move it_pa0002-nachn to it_moblist-nachn.
          move it_pa0002-vorna to it_moblist-vorna.
          move it_pa0002-pernr to it_moblist-pernr.
        ENDIF.
        APPEND  it_moblist.
        CLEAR   it_moblist.
    *endif.
      ENDLOOP.
    ENDFORM.                    " data_selection
    *&      Form  BUILD
          text
    -->  p1        text
    <--  p2        text
    FORM build_fieldcat .
    Explain Field Description to ALV
      DATA: fieldcat_in TYPE slis_fieldcat_alv.
      CLEAR fieldcat_in.
      fieldcat_ln-fieldname = 'TELNUM'.
      fieldcat_ln-tabname   = 'IT_MOBLIST'.
      fieldcat_ln-no_out    = ' '.
      fieldcat_ln-seltext_l = 'TELNUM'.
      APPEND fieldcat_ln TO gt_fieldcat.
      CLEAR fieldcat_in.
      fieldcat_ln-fieldname = 'KARTNR'.
      fieldcat_ln-tabname   = 'IT_MOBLIST'.
      fieldcat_ln-no_out    = ' '.
      fieldcat_ln-seltext_l = 'KARTNR'.
      APPEND fieldcat_ln TO gt_fieldcat.
      CLEAR fieldcat_in.
      fieldcat_ln-fieldname = 'ZUTART'.
      fieldcat_ln-tabname   = 'IT_MOBLIST'.
      fieldcat_ln-no_out    = ' '.
      fieldcat_ln-seltext_l = 'ZUTART'.
      APPEND fieldcat_ln TO gt_fieldcat.
      CLEAR fieldcat_in.
      fieldcat_ln-fieldname     = 'PERNR'.
      fieldcat_ln-tabname       = 'IT_MOBLIST'.
      fieldcat_ln-no_out        = ' '.
      fieldcat_ln-seltext_l = 'PERNR'.
      APPEND fieldcat_ln TO gt_fieldcat.
      CLEAR fieldcat_in.
      fieldcat_ln-fieldname     = 'NACHN'.
      fieldcat_ln-tabname       = 'IT_MOBLIST'.
      fieldcat_ln-no_out        = ' '.
      fieldcat_ln-seltext_l =  'NACHN'.
      APPEND fieldcat_ln TO gt_fieldcat.
      CLEAR fieldcat_in.
      fieldcat_ln-fieldname     = 'VORNA'.
      fieldcat_ln-tabname       = 'IT_MOBLIST'.
      fieldcat_ln-no_out        = ' '.
      fieldcat_ln-seltext_l = 'VORNA'.
      APPEND fieldcat_ln TO gt_fieldcat.
      CLEAR fieldcat_in.
      fieldcat_ln-fieldname     = 'ZDATE'.
      fieldcat_ln-tabname       = 'IT_MOBLIST'.
      fieldcat_ln-no_out        = ' '.
      fieldcat_ln-seltext_l = 'ZDATE'.
      APPEND fieldcat_ln TO gt_fieldcat.
      CLEAR fieldcat_in.
      fieldcat_ln-fieldname     = 'PINNR'.
      fieldcat_ln-tabname       = 'IT_MOBLIST'.
      fieldcat_ln-no_out        = ' '.
      fieldcat_ln-seltext_l = 'PINNR'.
      APPEND fieldcat_ln TO gt_fieldcat.
      CLEAR fieldcat_in.
      fieldcat_ln-fieldname     = 'PUKNR'.
      fieldcat_ln-tabname       = 'IT_MOBLIST'.
      fieldcat_ln-no_out        = ' '.
      fieldcat_ln-seltext_l = 'PUKNR'.
      APPEND fieldcat_ln TO gt_fieldcat.
      CLEAR fieldcat_in.
      fieldcat_ln-fieldname     = 'TARIF1'.
      fieldcat_ln-tabname       = 'IT_MOBLIST'.
      fieldcat_ln-no_out        = ' '.
      fieldcat_ln-seltext_l = 'TARIF1'.
      APPEND fieldcat_ln TO gt_fieldcat.
      CLEAR fieldcat_in.
      fieldcat_ln-fieldname     = 'TARIF2'.
      fieldcat_ln-tabname       = 'IT_MOBLIST'.
      fieldcat_ln-no_out        = ' '.
      fieldcat_ln-seltext_l = 'TARIF2'.
      APPEND fieldcat_ln TO gt_fieldcat.
      CLEAR fieldcat_in.
      fieldcat_ln-fieldname     = 'TARIF3'.
      fieldcat_ln-tabname       = 'IT_MOBLIST'.
      fieldcat_ln-no_out        = ' '.
      fieldcat_ln-seltext_l = 'TARIF3'.
      APPEND fieldcat_ln TO gt_fieldcat.
      CLEAR fieldcat_in.
      fieldcat_ln-fieldname     = 'GTYPE'.
      fieldcat_ln-tabname       = 'IT_MOBLIST'.
      fieldcat_ln-no_out        = ' '.
      fieldcat_ln-seltext_l = 'GTYPE'.
      APPEND fieldcat_ln TO gt_fieldcat.
      CLEAR fieldcat_in.
      fieldcat_ln-fieldname     = 'IMEI'.
      fieldcat_ln-tabname       = 'IT_MOBLIST'.
      fieldcat_ln-no_out        = ' '.
      fieldcat_ln-seltext_l = 'IMEI'.
      APPEND fieldcat_ln TO gt_fieldcat.
      CLEAR fieldcat_in.
      fieldcat_ln-fieldname     = 'TWINCARD'.
      fieldcat_ln-tabname       = 'IT_MOBLIST'.
      fieldcat_ln-no_out        = ' '.
      fieldcat_ln-seltext_l = 'TWINCARD'.
      APPEND fieldcat_ln TO gt_fieldcat.
      CLEAR fieldcat_in.
      fieldcat_ln-fieldname     = 'TWINBILL'.
      fieldcat_ln-tabname       = 'IT_MOBLIST'.
      fieldcat_ln-no_out        = ' '.
      fieldcat_ln-seltext_l = 'TWINBILL'.
      APPEND fieldcat_ln TO gt_fieldcat.
      CLEAR fieldcat_in.
      fieldcat_ln-fieldname     = 'EINBAU'.
      fieldcat_ln-tabname       = 'IT_MOBLIST'.
      fieldcat_ln-no_out        = ' '.
      fieldcat_ln-seltext_l = 'EINBAU'.
      APPEND fieldcat_ln TO gt_fieldcat.
      CLEAR fieldcat_in.
      fieldcat_ln-fieldname     = 'BESCHR'.
      fieldcat_ln-tabname       = 'IT_MOBLIST'.
      fieldcat_ln-no_out        = ' '.
      fieldcat_ln-seltext_l = 'BESCHR'.
      APPEND fieldcat_ln TO gt_fieldcat.
      CLEAR fieldcat_in.
      fieldcat_ln-fieldname     = 'TEXT1'.
      fieldcat_ln-tabname       = 'IT_MOBLIST'.
      fieldcat_ln-no_out        = ' '.
      fieldcat_ln-seltext_l = 'TEXT1'.
      APPEND fieldcat_ln TO gt_fieldcat.
      CLEAR fieldcat_in.
      fieldcat_ln-fieldname     = 'TEXT2'.
      fieldcat_ln-tabname       = 'IT_MOBLIST'.
      fieldcat_ln-no_out        = ' '.
      fieldcat_ln-seltext_l = 'TEXT2'.
      APPEND fieldcat_ln TO gt_fieldcat.
      CLEAR fieldcat_in.
      fieldcat_ln-fieldname     = 'TEXT3'.
      fieldcat_ln-tabname       = 'IT_MOBLIST'.
      fieldcat_ln-no_out        = ' '.
      fieldcat_ln-seltext_l = 'TEXT3'.
      APPEND fieldcat_ln TO gt_fieldcat.
    DATA SORTING
      DATA: gs_sort TYPE slis_sortinfo_alv.
      CLEAR gs_sort.
      gs_sort-fieldname = 'TELNUM'.
      gs_sort-spos      = 1.
      gs_sort-up        = 'X'.
    GS_SORT-SUBTOT    = 'X'.
      APPEND gs_sort TO gt_sort.
    CLEAR GS_SORT.
    GS_SORT-FIELDNAME = 'KARTNR'.
    GS_SORT-SPOS      = 2.
    GS_SORT-UP        = 'X'.
    *GS_SORT-SUBTOT    = 'X'.
      APPEND gs_sort TO gt_sort.
    ENDFORM.                    " BUILD
    *&      Form  EVENTTAB_BUILD
          text
         <--P_GT_EVENTS  text
    FORM eventtab_build  CHANGING lt_events TYPE slis_t_event.
      CONSTANTS:
    gc_formname_top_of_page TYPE slis_formname VALUE 'TOP_OF_PAGE',
    gc_formname_end_of_page TYPE slis_formname VALUE 'END_OF_PAGE'.
      DATA: ls_event TYPE slis_alv_event.
      CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
        EXPORTING
          i_list_type = 0
        IMPORTING
          et_events   = lt_events.
      READ TABLE lt_events WITH KEY name =  slis_ev_top_of_page
                               INTO ls_event.
      IF sy-subrc = 0.
        MOVE gc_formname_top_of_page TO ls_event-form.
        APPEND ls_event TO lt_events.
      ENDIF.
    define END_OF_PAGE event
      READ TABLE lt_events WITH KEY name =  slis_ev_end_of_page
                               INTO ls_event.
      IF sy-subrc = 0.
        MOVE gc_formname_end_of_page TO ls_event-form.
        APPEND ls_event TO lt_events.
      ENDIF.
    ENDFORM.                    " EVENTTAB_BUILD
    *&      Form  COMMENT_BUILD
          text
         <--P_GT_LIST_TOP_OF_PAGE  text
    FORM comment_build  CHANGING gt_top_of_page TYPE slis_t_listheader.
      DATA: gs_line TYPE slis_listheader.
      DATA: today_date(10) TYPE c.
      CONCATENATE
      sy-datum+6(2) '.'
      sy-datum+4(2) '.'
      sy-datum(4) INTO today_date.
      CLEAR gs_line.
      gs_line-typ  = 'H'.
      gs_line-info = 'MOBLIST DETAILS'.
      APPEND gs_line TO gt_top_of_page.
      CLEAR gs_line.
      gs_line-typ  = 'S'.
      gs_line-key  = 'Date:'.
      gs_line-info = today_date.
      APPEND gs_line TO gt_top_of_page.
    GS_LINE-KEY  = 'User:'.
    GS_LINE-INFO = sy-uname.
      APPEND gs_line TO gt_top_of_page.
      CLEAR gs_line.
      gs_line-typ  = 'A'.
      gs_line-info = 'ACTION'.
      APPEND gs_line TO  gt_top_of_page.
    ENDFORM.                    " COMMENT_BUILD
    *&      Form  CALL_ALV
          text
    -->  p1        text
    <--  p2        text
    FORM call_alv .
      CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
       EXPORTING
       i_callback_program = g_repid
    I_CALLBACK_PF_STATUS_SET = ' '
    I_CALLBACK_USER_COMMAND = ' '
       is_layout =  gs_layout
       it_fieldcat = gt_fieldcat
         it_sort = gt_sort
         it_events = gt_events
         is_print = gs_print
       TABLES
         t_outtab = IT_MOBLIST
       EXCEPTIONS
         program_error = 1
       OTHERS = 2.
    ENDFORM.                    "CALL_ALV.

    Hi,
    add:
    1) to IT_MOBLIST
    text3 type zfm_handy-text3,
    kostl type csks-kostl,
    end of it_moblist.
    2)...
    CLEAR fieldcat_in.
    fieldcat_ln-fieldname = 'KOSTL'.
    fieldcat_ln-tabname = 'IT_MOBLIST'.
    fieldcat_ln-no_out = ' '.
    fieldcat_ln-seltext_l = 'KOSTL'.
    APPEND fieldcat_ln TO gt_fieldcat.

  • Report RCATS_DISPLAY_ACTIVITIES to add new fields

    Hi  SAP Gurus ,
    I have a req to add new fields from a table ZCS_ENGINE to the report RCATS_DISPLAY_ACTIVITIES . 
    I copied the program and create a Z report ZRCATS_DISPLAY_ACTIVITIES , but i am facing difficulties to add new fields
    to the fieldcatalog.
    Can u please tell the procedure to add fields into the layout and show the output ..
    Advance Thanks,
    Thanks,
    AMS
    Moderator message: too vague, please describe problems in all technical detail when posting again, what is "difficulties", is it classical, ALV, class based ALV, what have you tried so far, please search for available information on fieldcatalog and layouts before asking.
    Edited by: Thomas Zloch on Oct 19, 2010 3:28 PM

    hi,
    as per your requirement (3 fields you mentioned )not inthe standard .you have to contact technical team for new report or enhance ment.
    regards
    muthuramand

  • How to add New field in SMART forms.

    How to add new field in the SMART FORMS. Please know me the step.
    Please help me soon.
    Moderator message: Welcome to SCN!
    Moderator message: please search for available information/documentation, do not use a priority higher than normal (no "soon", "ASAP", "earliest" etc.).
    [Rules of engagement|http://wiki.sdn.sap.com/wiki/display/HOME/RulesofEngagement]
    [Asking Good Questions in the Forums to get Good Answers|/people/rob.burbank/blog/2010/05/12/asking-good-questions-in-the-forums-to-get-good-answers]
    Edited by: Thomas Zloch on Jun 17, 2011 12:31 PM

    How to add new field in the SMART FORMS. Please know me the step.
    Please help me soon.
    Moderator message: Welcome to SCN!
    Moderator message: please search for available information/documentation, do not use a priority higher than normal (no "soon", "ASAP", "earliest" etc.).
    [Rules of engagement|http://wiki.sdn.sap.com/wiki/display/HOME/RulesofEngagement]
    [Asking Good Questions in the Forums to get Good Answers|/people/rob.burbank/blog/2010/05/12/asking-good-questions-in-the-forums-to-get-good-answers]
    Edited by: Thomas Zloch on Jun 17, 2011 12:31 PM

  • Add new field in OAF Page.

    I want to personalize a OAF page. My question is, Can i add new field in OAF page linked with database field and some calculations.
    I am trying to add new field in Termination page of Self service HR which will show the hiredate of employee and number of year served.

    Hi,
    As already specified by Kali..
    Step 1 - Create a new Field of type MessageStyledText using Personalization Link.
    Step 2 - Set the corresponding VO Attribute, which will fetch Hire Date.
    Step 3 - Extend the CO and calculate the Served Year, using Java Code.
    Step 4- Set the same value over the bean manually.
    Regards,
    Gyan

  • Add new field in Web UI

    Hi
    I want add new field in view GS_CM/AddDoc.
    I have studied a documentation http://www.sdn.sap.com/irj/scn/elearn?rid=/library/uuid/509a21a9-24be-2b10-d39b-de4c6b3fc222
    but for a component GS_CM the button "Create New Field" is inactive.
    Can I add the my field in views GS_CM/AddDoc ?

    Hi,
    open component GS_CM in tx BSP_WD_CMPWB.
    Here open your view AddDoc.
    Before you will be able to add new fields you have to enhance this view (right mouseclick on view).
    Now navigate to the context nodes. This view has 3 context nodes. Decide where to add your and add it using the assistant by right click on "Attributes". Before you do this check in the UI configuration the available fields. Maybee there is already the field available you require.
    I hope this helps.
    Regards
    Manfred

Maybe you are looking for