WHAT ARE THE FORMS (SCRIPTS) WHICH ARE NOT PROVIDED BY STANDARD SAP?

WHAT ARE THE FORMS (SCRIPTS) WHICH ARE NOT PROVIDED BY STANDARD SAP?

Hi Pravin
For a beginner in CRM - Sales would be a right choice to understand how CRM behaves when integrated with backend R/3.
Still as far as CRM goes, most of the components are not exposed to their fullest potential and that is why its not outshining the competitors in market.

Similar Messages

  • How to clear the form fields which are not rendered

    I have a creation form. There is a document_type list set up as a partial triger. When user change the document type, only the filed related to that document type will be rendered. This caused a problem when we need to clear the form . The input in the field which is not render won't be cleared when reset button is pressed. Can anybody give a sugestion on how to handle this?
    I tried to use the following function to clear the fields. It does not work since it get the list value before the list value change and clear the fields after the new field rendered.
    public void clear_action(ValueChangeEvent valueChangeEvent) {
    // Add event code here...
    System.out.println("test1");
    String coutcase = null;
    if(EL.get("#{bindings.Proxy.inputValue}") != null){
    coutcase = EL.get("#{bindings.Proxy.inputValue}").toString();
    System.out.println(coutcase);
    AttributeBinding a11= (AttributeBinding)getBindings().getControlBinding("INT_FNAM");
    AttributeBinding a12 = (AttributeBinding)getBindings().getControlBinding("INT_LNAM");
    AttributeBinding a13 = (AttributeBinding)getBindings().getControlBinding("TIT_PROG");
    AttributeBinding a14 = (AttributeBinding)getBindings().getControlBinding("T_OF_INT");
    AttributeBinding a15 = (AttributeBinding)getBindings().getControlBinding("NETWORK");
    AttributeBinding a16 = (AttributeBinding)getBindings().getControlBinding("IN_DATE");
    AttributeBinding a17 = (AttributeBinding)getBindings().getControlBinding("PE_FNAM");
    AttributeBinding a18 = (AttributeBinding)getBindings().getControlBinding("PE_IN_LNAM");
    AttributeBinding a19 = (AttributeBinding)getBindings().getControlBinding("WEBSITE");
    AttributeBinding a20 = (AttributeBinding)getBindings().getControlBinding("URL");
    AttributeBinding a21 = (AttributeBinding)getBindings().getControlBinding("INT_DATA");
    AttributeBinding a22 = (AttributeBinding)getBindings().getControlBinding("D_ACCESS");
    AttributeBinding a23 = (AttributeBinding)getBindings().getControlBinding("CASE_NUM");
    AttributeBinding a24 = (AttributeBinding)getBindings().getControlBinding("COURT");
    AttributeBinding a25 = (AttributeBinding)getBindings().getControlBinding("PLAIN");
    AttributeBinding a26 = (AttributeBinding)getBindings().getControlBinding("DEFEN");
    if(coutcase.equals("Interview")) {
    a11.setInputValue(null);
    a12.setInputValue(null);
    a13.setInputValue(null);
    a14.setInputValue(null);
    a15.setInputValue(null);
    a16.setInputValue(null);
    a17.setInputValue(null);
    a18.setInputValue(null);
    /*a19.setInputValue(null);
    a20.setInputValue(null);
    a21.setInputValue(null);
    a22.setInputValue(null);
    a23.setInputValue(null);
    a24.setInputValue(null);
    a25.setInputValue(null);
    a26.setInputValue(null);*/
    } else if(coutcase.equals("Internet")){
    /*a11.setInputValue(null);
    a12.setInputValue(null);
    a13.setInputValue(null);
    a14.setInputValue(null);
    a15.setInputValue(null);
    a16.setInputValue(null);
    a17.setInputValue(null);
    a18.setInputValue(null);*/
    a19.setInputValue(null);
    a20.setInputValue(null);
    a21.setInputValue(null);
    a22.setInputValue(null);
    /*a23.setInputValue(null);
    a24.setInputValue(null);
    a25.setInputValue(null);
    a26.setInputValue(null);*/
    } else{
    /*a11.setInputValue(null);
    a12.setInputValue(null);
    a13.setInputValue(null);
    a14.setInputValue(null);
    a15.setInputValue(null);
    a16.setInputValue(null);
    a17.setInputValue(null);
    a18.setInputValue(null);
    a19.setInputValue(null);
    a20.setInputValue(null);
    a21.setInputValue(null);
    a22.setInputValue(null);*/
    a23.setInputValue(null);
    a24.setInputValue(null);
    a25.setInputValue(null);
    a26.setInputValue(null);
    }else{
    System.out.println("coutcase is null");
    }

    Hi,
    The easiest way to modify the screens in the Std transactions using ITS is to modify the ITS templates corresponding to that transaction.
    E.g In you case,there will be a ITS service corresponding to the ESS transaction.This ITS service will have  number of HTML templates which will actually correspond to the diffrent screens in the Trascn.What you need to do is find out the HTML template in the ITS service which corresponds to the screen(which you want to modify) in the STd transacn.To do this ,the easiest way is to right click on that Web page and say VIEW SOURCE.It will show you a HTML code with the ITS service name and the template which is being used for that particular screen.
    So after you find out the correct HTML template to be modified,you can simply hide the fields by putting the HTML code lines in between the symbols
      <!   and  -->
    BR,
    Disha.
    <b>Pls reward points for useful answers.</b>

  • URGENT: Where are the upgrade scripts for Tier1 ?

    I found the upgrade scripts for 3.0.6/3.0.7 to 3.0.8 for Windows NT and Solaris here on Technet, but where are the upgrade scripts for the Tier 1 platforms ? I urgently need the ugrade script for Tru64. Please help.

    Sorry for the confusion - the page should be updated very
    shortly. In the meantime, you can download the 3.0.6/3.0.7/3.0.8
    to 3.0.9 scripts for NT/2000 at:
    http://download.oracle.com/otn/nt/portal/p1831355_309_WINNT.zip
    and 3.0.6/3.0.7/3.0.8 to 3.0.9 scripts for UNIX at:
    http://download.oracle.com/otn/solaris/portal/p1831348_309_UNIX.z
    ip
    Note that these are the same scripts that are accessible from
    Metalink (NT/2000 - Patch:1831355) and (UNIX - Patch:1831348)

  • How can i find all included pictures in the Online-Library which are not in a album?

    Hi
    I use Adobe Photoshop Elements 13 with (Revel). My question ist how can i find all included pictures in the Online-Library which are not in a album? I would like only to have pictures in Library which are included in a online album.

    Hi there,
    I'm afraid I don't quite understand your question. All images are in your Library and only those you specifically select from that Library would be in an Album. What platform are you using? Revel Mac, Elements, web browser, etc?
    Here is a link with some helpful information:
    FAQ: File Basics: How do I Upload, Download, Share, and Delete files in Revel?
    Thank you,
    Glenyse

  • Whats are the Forms and Reports in QM?and what is differece betwwen them?

    whats are the Forms and Reports in QM?and what is differece betwwen them?

    Hi,
    1. Forms are like templates.Forms define the text format and page layout of documents, which can be formatted (in accordance with the definitions) for display on the screen or for output to a printer.
    2. Executable program that allows users to read and evaluate data in the database.
    You can either display the output of a report on the screen or send it to a printer. You can also save it, so that it can be displayed as often as you like. It is important to be able to do this, because reading large volumes of original data can impair performance.
    Examples of reports are ABAP reports, queries, and drilldown reports.
    In short, forms are only templates and reports will retrive the data from system in certain format.
    Vishal

  • What exactly are the cron scripts doing?

    Hi,
    Hope the subject says it all: I have searched but not found a detailed explanation as what the cron scripts (daily, weekly, monthly) actually do, and if the utilities (Onyx, Cocktail, Xupport, etc) are doing exactly the same.
    Can someone point to a site or explain?
    TIA
    Dan

    Hi Dan,
    (in addition to Barry's reply)
    Yes,
    1) running the Daily, the Weekly and the Monthly tasks manually with an utility, or
    2) running them yourself with the
    sudo periodic daily
    sudo periodic weekly
    sudo periodic monthly
    Terminal commands
    (or this one: sudo periodic daily weekly monthly), or
    3) leaving your computer running 24/7/365 so that they run automatically,
    all three ways do exactly the same thing.
    --> To see what they do exactly, the best way is to open Console, and in the /var/log section, look for "daily.out", "weekly.out" and "monthly.out".
    What exactly are the "cron scripts" doing?
    (Periodic tasks)
    In Console, you'll find a lot of different files that grow with more and more information every minute, even every second for some of them.
    The three Periodic tasks regularly rearrange them and compresses them so that they don't take too much disk space.
    They also rebuild some system database so that the data never gets unusable by the system.
    HTH
    Axl
    201

  • How an i compare the two forms ( script) that are in two systems ?

    Hi,
    How can I compare the two forms(sap script)  which are in different versions  or systems? One form is in D22 and other form is P22 .
    My requirement is to change the form when they are different.
    Thanks,
    Suresh.

    Hi,
    You can download the form info for each script and compare these two files.
    In the SAPscript choose Utilities -> Form info and save this as a file.  As they are structured in the same format you can then look for differences in these files rather than having to look through the form window by window.
    Regards,
    Nick

  • What are the following script doing?

    What are the following script doing? What does symbol *<* stand for?
    protected Map<Member, List<String>> divideWork(Set members, List<String>
    fileNames)
    Thank you

    su_penguin wrote:
    Side note: http://en.wikipedia.org/wiki/Operator_overloading
    Extra credit: What trick does Java's syntax use to allow Generics to compile with or without whitespace between the angle brackets? Ex: Map< Member, List< String > >
    Why doesn't it work in C++?Does this have something to do with the comment "Note that it is not an LL(1) grammar"? [http://java.sun.com/docs/books/jls/third_edition/html/syntax.html]

  • I have just updated to LR5.  I also have a new Camera.  Nikon D800.  Trying to import directly (from camera) into LR.  But unsuccessful. Getting the following message.  "The files are from a camera which is not recognised by the raw format support in Ligh

    I have just updated to LR5.  I also have a new Camera.  Nikon D800.  Trying to import directly (from camera) into LR.  But unsuccessful. Getting the following message.  "The files are from a camera which is not recognised by the raw format support in Lightroom."  How can I import please?

    Hi,
    I assume you mean the Nikon D810 because D800/800E support has been there since Lightroom 4.1
    Currently, because it is a new camera (D810) the only support is in a RC of ACR 8.6 for Photoshop CS6 and CC, as the RC runs out on 31 August it is expected support will be there in the next dot release of Lightroom.
    Current limitations are that only full sized NEF is supported.
    If you wish to import to Lightroom 5.5. you will need to download the DNG Converter v8.6RC and convert the NEF files (full size RAW ony) to DNG then import into Lightroom 5.5

  • What are the modules in which we can create a party site?

    Hi Gurus,
    I would like to know, what are the modules from which we can create a party site.
    Please repond.
    Thanks,
    Venkatesh

    Hi,
    There can be numerous modules which create party sites , Leads/Quotes/Order/Recievable/HR/IB/ISupport etc.
    Actual number of modules depend on the kind of implementation.
    Run this query in your Oracle instance , to get an idea of various modules which has created Party sites in your system.
    SELECT meaning,
    description
    FROM fnd_lookup_values
    WHERE lookup_type = 'HZ_CREATED_BY_MODULES'
    AND lookup_code IN (SELECT DISTINCT created_by_module
    FROM hz_party_sites)
    -Idris

  • I have put several clips with transitions into the timeline in final cut pro. There are two clips which are followed by transitions which do not play at the right speed. It is extremely frustrating, can anyone help?

    I have put several clips with transitions into the timeline in final cut pro X. There are two separate clips which are followed by transitions which do not play at the right speed. I'm at a loss as to why this is happening - any thoughts/help?

    The two HD clips were purchased from itunes (MPEG - 4) and converted to .mov for use in Final Cut Pro. Project properties - 720p HD 1280x720 (60p)
    Is this enough information?

  • How can we restrict the absence status (Which are not yet to be approved)in team calendar(MSS)

    How can we restrict the absence status (Which are not yet to be approved)in team calendar(MSS)

    Hi user570596,
    I think there is no method to actually restrict the date picker popup, but you can use the ApexLib Framework (http://apexlib.sourceforge.net/) to define a min/max value for your date field. This will prevent the user from submitting the page when the date value is outside the defined range.
    See http://inside-apex.blogspot.com/2007/03/min-max-value-validation-in-browser.html
    for details.
    Patrick
    Check out my APEX-blog: http://inside-apex.blogspot.com
    Check out the ApexLib Framework: http://apexlib.sourceforge.net

  • Deduplication: how to identify which files are "in-policy" (and which are not)?

    Dear experts,
    in eventlog I find the following information for one of my deduplicated volumes:
    Volume: F: (\\?\Volume{9794e270-fb08-487e-979b-8a08fa9ca311}\)
    Error code: 0x0
    Error message:
    Savings rate: 24
    Saved space: 853327714684
    Volume used space: 2681869406208
    Volume free space: 66771247104
    Optimized file count: 1199618
    In-policy file count: 1188049
    Job processed space (bytes): 0
    Job elapsed time (seconds): 2
    Job throughput (MB/second): 0
    Some things look strange to me: 
    - The savings rate is only 24% which looks odd because I get about 40% on other file shares with similar characteristics.
    - The "Optimized file count" is higher than the "in-policy" file count.
    - The volume has about 3.5 million files but only 1.1 million files are "in-policy".
    My understanding of "in-policy" files is that all files are in-policy which are older than 3 days (if not configured different, which is not the case) and which are not contained in an excluded folder (nothing configured here) and which have no
    excluded file extension (nothing configured here apart from the default). Right?
    I'm sure that only a small fraction of the files on this volume are younger than three days, so something seems to be wrong there, but I have no idea how to find the cause of the problem.
    Is there any way to identify the files (full path) which are considered to be not "in-policy"?
    How can I find out if the optimization process really looks at all files - and doesn't skip a million?
    Thanks!
    Regards
    Christoph

    Mandy, thanks for your feedback! I've read these technet articels, but I couldn't learn something really helpfull related to my problem there. To make investigation of the problem easier I did the following:
    - created a brand new empty volume (x:) on the same server
    - enabled data deduplication on that volume with a minimal file age of 0 days
    - copied about 2GB of data from the problem-volume in 15450 files to this new volume
    - started "Start-DedupJob x: -Type Optimization -Memory 50"
    After a few seconds that job completed and I got the following result:
    Volume: X: (\\?\Volume{d1ba9ed8-28f1-44d1-9535-fe603d6a70c6}\)
    Error code: 0x0
    Error message:
    Savings rate: 0
    Saved space: 12360718
    Volume used space: 3091664896
    Volume free space: 7610097664
    Optimized file count: 153
    In-policy file count: 153
    Job processed space (bytes): 46095214
    Job elapsed time (seconds): 9
    Job throughput (MB/second): 4.88
    The question is: why are only 153 files in-policy?
    All files (of more than 15000) are of course "older than 0 days", there are no excluded folders configured, there are no excluded extensions configured, no file has one of the default excluded extensions and more than 1000 files are bigger than 100kB
    (minimal size for deduplication is 32kB). So what makes only 153 files qualify for deduplication?
    My impression is that there are further undocumented requirements which have to be met by a file to qualify for deduplication. But if there's no detailed log of an optimization run available how to find out what's going on?
    (Or is something going wrong on my server?)
    Kind Regards
    Christoph

  • How do you fill in a form that was saved as a template? When I try, the "template" shifts, which is not how a template should work!

    How do you fill in a form that was saved as a template? When I try, the "template" shifts, which is not how a template should work!
    Templates, as I understand them, are fixed; you can "fill them in" without shifting them. Yet, I've saved doc as a template AND it shifts. Argh!

    Thanks for your response.
    I've managed to fix it but I wouldn't recommend the following as I'm sure its unsupported and I'll probably have problems down the line
    On the host
    * mv /etc/zones /etc/zones.bak
    * reboot single user
    * apply kernel patch (the one that ultimately I had to get on and which was giving pre-req dependency errors when running zones)
    * create a new zone now that host system is all up to date
    * Copy the operating system directories of the new zone (the one that's all patched) over the troublesome zone (the one that can't take the patch). Take backups first
    * cd /zones/new-zone/root
    * find sbin -print | cpio -pudm /zones/bad-zone/root
    * find usr -print | cpio -pudm /zones/bad-zone/root
    * find lib -print | cpio -pudm /zones/bad-zone/root
    * cd /zones/new-zone/root/var
    * find sadm -print | cpio -pudm /zones/bad-zone/root/sadm (this copies patches and pkgs directories and I'm sure a lot of other stuff that I didn't want)
    * mv /etc/zones.bak /etc/zones
    * reboot host
    * boot the old zone up. It should now have up to date patches
    I'm sure there are real no-no's in taking this approach but it seems to have worked for me. I'll update if I find there are some horrors down the line
    Edited by: paul_xedos on Mar 25, 2010 4:07 AM

  • What are the main events that are used in an alvreport?

    hi
    experts can u help me for this

    Hi
    REUSE_ALV_EVENTS_GET
    Description
    This table tells ALV which events are processed by the caller by CALLBACK.
    The table of possible events per list type can be initialized using the module REUSE_ALV_EVENTS_GET.
    You can display the names of the constants in the type pools SLIS which represent the individual events using the individual test function in the function module
    REUSE_ALV_EVENT_NAMES_GET. Only events with a form routine name are processed.
    The table structure contains the fields:
    •     IT_EVENTS-NAME
    Name of the Callback event.
    Possible Callback events:
    •     Action
    USER_COMMAND USING R_UCOMM LIKE SY-UCOMM RS_SELFIELD TYPE SLIS_SELFIELD
    Process actions on the list
    As this is a frequently-used Callback event, the form routine can also be passed directly in the interface in the IMPORTING parameter I_CALLBACK_USER_COMMAND.
    PF_STATUS_SET USING RT_EXTAB TYPE SLIS_T_EXTAB
    If a user list status is to be set, it must be done in the form routine assigned to this event. The ALV function codes, which must not be active, are in the Parameter RT_EXTAB. This table must be passed with the SET PF-STATUS command (with inactive user function codes as well, if necessary).
    The STANDARD status of the function group SALV should be used as a template for a user-specific status.
    As this is a frequently-used Callback event, its form routine can also be passed directly in the interface in the IMPORTING parameter I_CALLBACK_PF_STATUS_SET.
    ITEM_DATA_EXPAND USING RS_SELFIELD TYPE SLIS_SELFIELD RFLG_ALL TYPE C
    Only relevant for hierarchical-sequential lists using the layout parameter IS_LAYOUT-EXPAND_FIELDNAME of the structure IS_LAYOUT.
    Exit for passing item entries (ITEM table) for a header record which was expanded interactively by the user.
    RS_SELFIELD-TABINDEX contains the header table index for which the item entries are to be put in the global item output table (T_OUTTAB_SLAVE). The Callback is only called if ALV has no items for a header which is to be expanded.
    RFLG_ALL is passed with 'X' if the user shows all items. The application must ensure that entries are not repeated in the item table. RS_SELFIELD is initial in this case.
    CALLER_EXIT USING RS_DATA Is called at the beginning of the function module to make special settings. It is not usually used.
    •     List processing events
    IMPORTANT: The application Callback routine must not manipulate the internal output table and/or its header record. This restriction applies to all Callbacks which are called in the list output and run under the 'List processing events'.
    TOP_OF_LIST no USING parameter. Information output at the start of the list
    END_OF_LIST no USING parameter. Information output at the end of the list
    TOP_OF_PAGE no USING parameter
    Equivalent to the list processing TOP-OF-PAGE event
    END_OF_PAGE no USING parameter. Not available for hierarchical-sequential lists.
    Information output at the end of a page. This is only called for printing.
    TOP_OF_COVERPAGE no USING parameter
    The selection information and list status are output together (if they exist) on a separate page by default. See also the documentation of the parameters:
    IS_PRINT-NO_COVERPAGE
    IS_PRINT-NO_PRINT_SELINFOS
    IS_PRINT-NO_PRINT_LISTINFOS
    IS_LAYOUT-GET_SELINFOS
    The user can format the header area of the 'cover page' himself or herself by specifying a Callback routine for this event.
    END_OF_COVERPAGE no USING parameter
    Analogously to TOP_OF_COVERPAGE the user can add other information to the information output by ALV (selection information, list status) at this event.
    FOREIGN_TOP_OF_PAGE no USING parameter
    The Top-of-page event is always processed in ALV and is only passed to the caller via the Callback mechanism. This is still the case if the caller, e.g. by a user action, processes a branch list which was not formatted by ALV (e.g. a popup with additional information about the list record selected and displayed by ALV).
    In this case, top-of-page cannot be formatted by ALV analogously to the basic list, it must be handled completely by the caller. The event top-of-page still occurs in ALV. When ALV notices a top-of-page which was not caused by an ALV output, the form routine in FOREIGN_TOP_OF_PAGE is called.
    FOREIGN_END_OF_PAGE no USING parameter
    The event end-of-page is always processed in ALV and only passed to the caller via callback. This is still the case, e.g. when the caller processes a details list which was not formatted by ALV (e.g. a popup with further information about selected list records which were displayed by ALV).
    In this case, end-of-page cannot be formatted by ALV analogously to the basic list, it must be handled completely by the caller. The event end-of-page still occurs in ALV. When ALV notices an end-of-page that was not caused by an ALV output, the form routine in FOREIGN_END_OF_PAGE is called.
    BEFORE_LINE_OUTPUT USING RS_LINEINFO TYPE SLIS_LINEINFO
    Output information before each output line. Should only be used in justified cases because it costs a lot of performance.
    AFTER_LINE_OUTPUT USING RS_LINEINFO TYPE SLIS_LINEINFO
    Output information after each output line. Should only be used in justified cases because it costs a lot of performance.
    •     Internal use only
    LIST_MODIFY USING R_TABNAME TYPE SLIS_TABNAME
    R_INDEX LIKE SY-TABIX
    R_INDEX_ITEM LIKE SY-TABIX
    R_INDEX_SUM LIKE SY-TABIX
    •     IT_EVENTS-FORM
    Name of the form routine which should be called in the calling program at the event.
    Field_catalog:
    Field catalog with field descriptions
    2.7.1.     Description
    Field catalog containing descriptions of the list output fields (usually a subset of the internal output table fields). A field catalog is required for every ALV list output.
    The field catalog for the output table is built-up in the caller's coding. The build-up can be completely or partially automated by calling the REUSE_ALV_FIELDCATALOG_MERGE module
    See also the documentation of the function module REUSE_ALV_FIELDCATALOG_MERGE.
    The minimal field catalog is documented under 'default'. The caller can use the other optional parameters to assign output attributes to a field which differ from the default.
    A field catalog need not be built-up and passed explicitly only under the following conditions:
    •     The internal table to be output has the same structure as a Data Dictionary structure which is referred to in the internal table declaration using LIKE or INCLUDE STRUCTURE.
    •     all fields in this structure are to be output
    •     the structure name is passed to ALV in the parameter I_STRUCTURE_NAME.
    See also the documentation of the IMPORTING paramter I_STRUCTURE_NAME.
    Positioning
    •     row_pos (row position)
    value set: 0, 1 - 3
    Only relevant if the list output is to be multi-line (two or three lines) by default.
    A multi-line list can also be defined by the user interactively if the default list is one-line.
    The parameter specifies the relative output line of the column in a multi-line list.
    •     col_pos (column position)
    value set: 0, 1 - 60
    only relevant when the default relative column positions differ from the field catalog field sequence. The parameter specifies the relative column position of the field in the list output. The column order can be changed interactively by the user. If this parameter is initial for all field catalog entries, columns appear in the field catalog field sequence.
    Identification
    •     fieldname (field name)
    value set: internal output table field name (required parameter)
    Name of the internal output table field which is described by this field catalog entry
    •     tabname (internal output table)
    value set: SPACE, internal output table name
    This parameter is used in 'manual' field catalog build-up only for hierarchical-sequential lists.
    Name of the internal output table which contains the field FIELDCAT-FIELDNAME.
    Data Dictionary reference
    •     ref_fieldname (reference field name)
    value set: SPACE, Data Dictionary field name
    Name of the Data Dictionary field referred to.
    This parameter is only used when the internal output table field described by the current field catalog entry has a reference to the Data Dictionary (not a program field), and the field name in the internal output table is different from the name of the field in the Data Dictionary. If the field names are identical, naming the Data Dictionary structure or table in the FIELDCAT-REF_TABNAME parameter is sufficient.
    •     ref_tabname (reference table/structure field name)
    value set: SPACE, name of a Data Dictionary structure or table
    Structure or table name of the referred Data Dictionary field.
    This parameter is only used when the internal output table field described by the current field catalog entry has a Data Dictionary reference (not a program field).
    Reference to fields with currency/measurement unit
    Each internal output table sum or quantity field whose decimal places are to be formatted appropriately for the unit in the list must follow the convention:
    •     the field is of data type QUAN or CURR (internal type P) (the field must really have this physical data type. Overwriting the physical data type with the parameter FIELDCAT-DATATYPE has no effect)
    •     There is a field in the internal output table which contains the associated unit.
    •     There is also an entry in the field catalog for the unit field.
    (If the unit is not to appear as a column in the list, and cannot be interactively displayed as a column, e.g. because it is always unambiguous and is therefore explicitly output by the caller in the list header, the field catalog units field entry can take the parameter FIELDCAT-TECH = 'X'.
    The association of a value field to a unit affects the output as follows:
    •     appropriate decimal places display for the unit
    •     an initialized field with a link to a non-initial unit is output as '0' for the unit (if FIELDCAT-NO_ZERO is initial). When this field is summed, this unit affects whether the units are homogeneous.
    •     an initialized field with a link to an initial unit is output as SPACE. When this field is summed, the unit SPACE does not affect the homogeneity of the units.
    •     When non-initial fields with an initial unit are summed, the unit SPACE is considered to be a unit.
    Link to currency unit
    •     cfieldname (currency unit field name)
    value set: SPACE, output table field name
    Only relevant for amount columns with associated unit.
    Name of the internal output table field containing the currency unit associated with the amount field FIELDCAT-FIELDNAME. The field in FIELDCAT-CFIELDNAME must have its own field catalog entry.
    •     ctabname (internal currency unit field output table)
    value set: SPACE, output table field name
    only relevant for hierarchical-sequential lists
    Name of the internal output table containing the FIELDCAT-CFIELDNAME field.
    Link to measurement unit
    •     qfieldname (measurement unit field name)
    value set: SPACE, output table field name
    only relevant for quantity columns with unit link.
    Name of the internal output table field containing the measurement unit associated with the quantity field FIELDCAT-FIELDNAME.
    The field in FIELDCAT-QFIELDNAME must have its own field catalog entry.
    •     qtabname (internal measurement unit field output table)
    value set: SPACE, output table field name
    only relevant for hierarchical-sequential lists
    Name of the internal output table containing the FIELDCAT-QFIELDNAME field.
    Column output options
    •     outputlen (column width)
    value set: 0 (initial), n
    For fields with a Data Dictionary link this parameter can be left initial.
    For fields without a Data Dictionary link (program field) the parameter must be given the value of the desired field list output length (column width).
    initial = column width is the output length of the referred Data Dictionary field (domain).
    n = column width is n characters
    •     key (key column)
    value set: SPACE, 'X'           'X' = kex field (key field output in color)
    Key fields can not be interactively hidden. Parameter FIELDCAT-NO_OUT must be left initial.
    For exceptions see the documentation of the FIELDCAT-KEY_SEL parameter.
    •     key_sel (hideable key column)
    value set: SPACE, 'X'
    only relevant when FIELDCAT-KEY = 'X'
    Key field which can be hidden interactively.
    The key column sequence cannot be changed interactively by the user.
    The output is controlled by the FIELDCAT-NO_OUT parameter analogously to non-key fields.
    •     no_out (field in field list)
    value set: SPACE, 'X'          'X' = field is not displayed in the current list.
    The user can interactively choose the field for output from the field list.
    The user can display the contents of these fields at line level using the 'Detail' function.
    See also the 'Detail screen' documentation of the parameter IS_LAYOUT.
    •     tech (technical field)
    value set: SPACE, 'X'          'X' = technical field
    Field cannot be output in the list and cannot be displayed interactively.
    Field can only be used in the field catalog (not in IT_SORT, ...).
    •     emphasize (highlight columns in color)
    value set: SPACE, 'X' or 'Cxyz' (x:'1'-'9'; y,z: '0'=off '1'=on)
    'X' = column is colored with the default column highlight color.
    'Cxyz' = column is colored with a coded color:
    •     C: Color (coding must begin with C)
    •     x: color number
    •     y: bold
    •     z: inverse
    •     hotspot (column as hotspot)
    value set: SPACE, 'X'
    'X' = column cells are output as hotspots
    •     fix_column (fix column)
    value set: SPACE, 'X'
    Not relevant for block lists (output of several lists consecutively)
    'X' = column fixed (does not scroll horizontally)
    All columns to be fixed must have this flag, starting from the left. If a column without this flag is output, only the columns to the left of this column are fixed. The user can change the column fixing interactively. See also the documentation of the Layout parameter
    IS_LAYOUT-NO_KEYFIX of the IMPORTING paramter IS_LAYOUT.
    •     do_sum (sum over column)
    value set: SPACE, 'X'           'X' = a sum is to be calculated over this internal output table field.
    This function can also be called by the user interactively.
    •     no_sum (sums forbidden)
    value set: SPACE, 'X'          'X' = no sum can be calculated over this field, although the data type of the field would allow summing.
    •     input (column ready for input)
    Function not available
    Format column contents
    •     icon
    value set: SPACE, 'X'           'X' = column contents to be output as an icon.
    The caller must consider the printability of icons.
    •     symbol
    value set: SPACE, 'X'          'X' = column contents are to be output as a symbol.
    The internal output table column must be a valid symbol character.
    The caller must consider the printability of symbols.
    Symbols can usually be printed, but may not always be output correctly, depending on the printer configuration.
    •     just (justification)
    value set: SPACE, 'R', 'L', 'C'
    Only relevant for fields of data type CHAR or NUMC
    ' ' = default justification for this data type
    'R' = right-justified output
    'L' = left-justified output
    'C' = centered output
    The justification of the column header always follows the justification of the columns. Independent justification of the column neader is not possible.
    •     lzero (leading zeros)
    value set: SPACE, 'X'
    Only relevant for fields of data type NUMC
    ALV outputs NUMC fields right-justified without leading zeros by default.
    'X' = output with leading zeros
    Note: If a NUMC field is output left-justified or centered by FIELDCAT-JUST, leading zeros are output. If the output of leading zeros is suppressed by a Data Dictionary reference ALPHA conversion exit, the output is always left-justified.
    •     no_sign (no +/- sign)           Only relevant for value fields
    value set: SPACE, 'X'     'X' = value output without +/ sign
    •     no_zero (suppress zeros)           Only relevant for value fields
    value set: SPACE, 'X'          'X' = suppress zeros
    •     edit_mask (field formatting)
    value set: SPACE, template
    template = see documentation of WRITE formatting option USING EDIT MASK template
    The output conversion conv can be made by template = '== conv'.
    Texts
    The following text parameters should be specified for program fields without a Data Dictionary reference. The texts are taken from the Data Dictionary for fields with a Data Dictionary reference. If this is not desired, the text parameters can also be specified. The Data Dictionary texts are then ignored. If the user changes the column width interactively, the column header text with the appropriate length is always used. The interactive function 'Optimize column width' takes account of both the field contents and the column headers: if all field contents are shorter than the shortest column header, the column width depends on the column header.
    The 'long field label' is also used in display variant definition, sort, etc. popups.
    •     seltext_l (long field label)
    •     seltext_m (medium field label)
    •     seltext_s (short field label)
    •     reptext_ddic (header)
    analogous to the Data element maintenance 'Header'
    The specified text is not necessarily output in the list, an optimum among all texts is sought.
    •     ddictxt (specify text)
    value set: SPACE, 'L', 'M', 'S'
    You can specify with values 'L', 'M', and 'S', the keyword that should always be used as column header. If the column width changes, no attempt is made in this case to find an appropriate header for the new output width.
    Parameters for program fields without Data Dictionary reference
    see also 'Text' parameters
    •     datatype (data type)
    value set: SPACE, Data Dictionary data type (CHAR, NUMC,...)
    Only relevant for fields without Data Dictionary reference
    Program field data type
    •     ddic_outputlen (external output length)
    value set: 0 (initial), n
    Only relevant for fields without Data Dictionary reference whose output is nevertheless to be modified by a conversion exit.
    Prerequisites:
    •     FIELDCAT-EDIT_MASK = '==conv'
    see also the documentation of the parameter FIELDCAT-EDIT_MASK
    •     FIELDCAT-INTLEN = n
    see also the documentation of the parameter FIELDCAT-INTLEN
    n = external format field output length
    The column width FIELDCAT-OUTPUTLEN need not be the same as the external format output length (FIELDCAT-DDIC_OUTPUTLEN).
    •     intlen (internal output length)
    value set: 0 (initial), n
    Only relevant for fields without Data Dictionary reference whose output is nevertheless to be modified by a conversion exit.
    Prerequisites:
    •     FIELDCAT-EDIT_MASK = '==conv'
    see also the documentation of the parameter FIELDCAT-EDIT_MASK
    •     FIELDCAT-DDIC_OUTPUTLEN = n
    see also the documentation of the parameter FIELDCAT-DDIC_OUTPUTLEN
    n = internal format field output length
    •     rollname (data element)
    value set: SPACE, Data Dictionary data element name
    F1 help can be provided for a program field without a Data Dictionary reference, or F1 help which differs from the Data Dictionary help can be provided for a field with a Data Dictionary reference, using this parameter.
    When F1 help is called for this field, the documentation of the specified data element is displayed.
    If the FIELDCAT-ROLLNAME is initial for fields with a Data Dictionary reference, the documentation of the data element of the referred Data Dictionary field is output.
    Others
    •     sp_group (field group key)
    value set: SPACE, CHAR(1)
    Field group key.
    Keys are assigned to group names in the IT_SPECIAL_GROUPS parameter (see also the documentation of the parameter IT_SPECIAL_GROUPS).
    When such an assignment is made in the field catalog and in IT_SPECIAL_GROUPS, the fields are grouped correspondingly in the display variant popup.
    •     reprep (Report/Report interface selection criterion)
    value set: SPACE, 'X'
    Prerequisites:
    •     The system contains the Report/Report interface (function group RSTI, table TRSTI)
    •     Parameter LAYOUT-REPREP = 'X'
    (see also the documentation of the parameter LAYOUT-REPREP of the IMPORTING parameter IS_LAYOUT )
    'X' = When the Report/Report interface is called, the value of this field is passed in the selected interface start record as a selection criterion.
    2.7.2.     Default
    •     The following entries are usually sufficient for internal table fields with a reference to a field defined in the Data Dictionary :
    •     fieldname
    •     ref_tabname
    Notes:
    ALV gets the remaining information from the Data Dictionary.
    If no relative column position (COL_POS) is specified, the fields are output in the list in the order in which they were added to the field catalog.
    REF_FIELDNAME need only be specifid when the name of the internal table field differs from the name of the referred Data Dictionary field.
    Information which is explicitly entered in the field catalog is not overwritten by information from the Data Dictionary.
    Priority rule:
    Entries in the field catalog have priority over differing entries in the Data Dictionary.
    •     The following entries are usually sufficient for internal table fields without a reference to the Data Dictionary (program fields):
    •     fieldname
    •     outputlen
    •     datatype
    •     seltext_s
    •     seltext_m
    •     seltext_l
    Notes:
    F1 help can be provided for program fields by assigning a data element to the parameter ROLLNAME.
    If the parameters SELTEXT_S, SELTEXT_M, SELTEXT_L, and REPTEXT_DDIC contain appropriate field labels, the program field column headers are also adjusted appropriately when the column width changes.
    <b>Reward points for useful Answers</b>
    Regards
    Anji

Maybe you are looking for