Following IMG doc - Field Catalog Add

Hi! all..
We added a new pricing field, DESTINATION CITY, field - ORT01 from table KNA1.
I am listing out the steps below what we did. Please look for it's 'correctness' and let me know the missing steps and mistakes.
1. Create a data element ZZORT01 and choose TEXT35 as its domain. Save, check and activate ZZORT01.
(ORT01_GP is the data element of ORT01 and it's domain is TEXT35.)
2. Extend structure KOMP by including ZZORT01 to KOMPAZ. Also allocate the data element ORT01_GP to ZZORT01. Again save, check and activate.
3. Assign a value to the new field in the FORM routines for sales order processing using the user exit.The code look like this:
FORM USEREXIT_PRICING_PREPARE_TKOMP.
MOVE KNA1-ORT01 TO TKOMP-ZZORT01.
ENDFORM.
4. Finally, allocate the specifications in table T681F.
( what does this 4th point refer to ? Allocate specification in table T681F????
Should i ask the ABAP person to include this New field in this TABLE directly or is there any other IMG option available to input this field???)
Please help me in understanding this???/
Thanks and i appreciate your help.

Hi,
go in your IMG, Sales&Distribution -> BasicFunction -> Pricing -> Pricing Control -> Define Condition Table -> Conditions: Allowed fields
Click the button "new entries" and the F4 in the open field - Here you shoud find your new field in the sector of KOMP
Greetings
Bernd

Similar Messages

Field Catalog Add/Change for Inbound Delivery.

Hello
I did try to add a field "ZZZ" into field catalog of Inbound delivery. I did add the same in KOMKBE1 & KOMB for output determination during Inbound Delivery.
Still, i couldn't get the field for creating condition table in Output Determination of Inbound Del.
Any suggestions?
Thanks

Add your new field to field catalogue. Path: SPRO - > LE -> Shipping->Basic shipping functions -> output control ->Output determination -> Maintain Output determination for outbound delivery -> Maintain cond table ->Field catalog: Output for deliveries
Then you can see your field to add in cond table

Problem with Field catalog

Hi,
I am trying to create a condition table for inventory management. I require it at material group / movement type level. I added the fields ZZMATKL (type MATKL) and ZZBWART (type BWART) in the structure KOMPBZ2 (which is present in in the include of structure KOMPBME).
I also added the two above custom fields in table V_T161F. But when I try to create a condition table I dont find the above two fields in the field catalog.
Please help.
Am I using an incorrect structure?
Thanks!!
Aroop

Hi Friend,
Looking at your code, I found that you have not the fieldcatalog at all.
You need to fill the fieldcatalog with all the fields you want to display in the alv.
Check the following links regarding field catalog:
http://abap-gallery.blogspot.com/2007/07/field-catalog-in-alv.html
Check this link for sample program:
http://www.****************/Tutorials/ALV/SampleALVGridProgram.htm
Hope this helps you.
Any queries, get back to me.
Regards,
Chandra Sekhar

How to add a field VBKD-IHREZ to field catalog in Output determination?

The requirement is maintaining the condition table using Sales Org/Sales Doc Type/Your reference in output determination process. But the field 'Your reference(VBKD-IHREZ)' is not in the field catalog. Can someone tell me how to add the VBKD-IHREZ to field catalog?
Thanks in Advance.

Hi
See SAP Note 21040 - Allowed Fields not appearing for condition table
Regards
Eduardo
PD: I forgot, go to IMG and see the documentation in the path: SD/system modifications / create new fields (using cond.tec) / new fields for output control and read the documentation. It tells us structures and how to populate (exits)
Edited by: E_Hinojosa on May 6, 2011 5:48 PM

After add a field catalog,how can I post the field value to IPC??

Hi,experts,I've created a field catalog "ZPRD_CHANGED"(I ZPRD_CHANGED D D ZCHG_FLAG(CHAR1))in IMG pricing,and also assigned the value to it
in method "ITEM_COMMUNICATION_STRUCTURE" in mplementation "ZCRM_COND_COM_BADI" of BADI "CRM_COND_COM_BADI".
LIke this:
DATA: lr_obj type ref to ZL_BT115IT__ITEMS_CN00.
create object lr_obj.
CS_ACS_I_COM-ZPRD_CHANGED = lr_obj->zprd_chg_flg.
After that,in the java codings of user exit in IPC,I add below codings:
public BigDecimal overwriteConditionValue(
IPricingItemUserExit pricingItem,
IPricingConditionUserExit pricingCondition)
String prodchanged = pricingItem.getAttributeValue("ZPRD_CHANGED");
But it seems that it doesn't work,variable "productchanged" can not get the value posted from method "ITEM_COMMUNICATION_STRUCTURE" in mplementation "ZCRM_COND_COM_BADI".
What's the problem?Can anybody suggest??
Thanks in advance.
Jerry.

Hi Jerry,
did you register the attribute in the customizing for the user exits? Transaction /SAPCND/UEASS. You need to register the attribute on Implementations and Formula level.
Best Regards,
Michael
P.S. Guess you are already aware of the userexit guide attached to note 809820.

Add a custom table for field selection while creating field catalog for LIS

Hi,
I have a requirement to add a Custom table to be available for field selection while creating a field catalog for LIS. Its required as there are many custom fields to be used for field catalog creation and adding them in one of the existing tables listed is not a feasible option for us. Please let me knw if its possible..?? If yes how to get it done..??
Regards,
Akash Sinha

hi,
You need to add your field in the Data Dictionary first. For example, if
you want the new field in the Order Item field catalog do the following.
Look at structure MCVBAPUSR (SE11). If you already have a user structure
appended to this structure then you can add your new field to your existing
structure. If there is no structure already appended to MCVBAPUSR then you
must create a new structure with your field in it and then append the new
structure to this one.
If you look at structure MCVBAP you will see the data appended to the end
of it.
Now you should see it in the field catalog.
regards,
balajia

Add a new field to field catalog in billing output

Hi Experts
can anyone tell me whether I can add 'item category' to field catalog for application V3. and how can I do this? I want to create an access sequence-bill to party/item category, is that possible?
thanks a lot!
elly

Hi..
Below is process of adding filed to catalogue in Pricing..
Follow below procedure as its same as condition technique...
Add a field to a new condition table in Pricing (Condition Technique):-
I will explain you the process with below example...Please follow steps in below sequence-
Try to add the filed from the field catalog. In case the required combination field is not there, you can add the field through the following process to filed catalog and create the condition table. It is most common that one or other time we need to use this function while configuring multi tasking & complex Pricing Architecture.
Here I'm giving a simple guide to add fields to the Pricing Field Catalogues:
For example you want to use field PSTYV ('Sales document item category') that is included in structure KOMP ('Pricing Communication Item') as a key for a condition table.
When you create a condition table (Transaction V/03), however, the system does not propose the field in the field catalog.
Condition access, field catalog, allowed fields, KOMG, KOMK, KOMP, KOMPAZ, KOMKAZ, PSTYV are the other terms which we need to know about, to add Fields.
Reason and Prerequisites:
For technical reasons, field PSTYV was included in structure KOMP, however, not in structure KOMG ('Allowed Fields for Condition Structures').
Proceed as follows:
1. Call up the ABAP Dictionary (Transaction SE11) and create data type ZZPSTYV. Choose PSTYV as a domain.As a short text, you can use, for example, 'ZZ - sales document item category' and as a field label, you can use the field labels of PSTYV.Save, check and activate your entries.
2. Call up structure KOMPAZ in the ABAP Dictionary (Transaction SE11) in the change mode and make the following entry:
Component Component type:
ZZPSTYV ZZPSTYV
Save, check and activate the change you made.
3. Note:Because of the change in structure KOMPAZ, field ZZPSTYV is now known in structures KOMG and KOMP because structure KOMPAZ is included in both structures.
4. Call up Transaction SPRO. Navigate to 'Sales and Distribution -> Basic Functions -> Pricing -> Pricing Control' and execute 'Define Condition Tables'.
Choose 'Conditions: Allowed fields' and include ZZPSTYV as a new entry.
5. Note:Now you can use field ZZPSTYV as a key field when you create a condition table Axxx.
6. Supply the new field you defined by including the following source code line in USEREXIT_PRICING_PREPARE_TKOMP:
MOVE xxxx-PSTYV TO TKOMP-ZZPSTYV.
In order processing you find the user exit in Include MV45AFZZ, and in billing document processing you find it in Include RV60AFZZ.
Consider that you can also use this note as a help if you want to use other customer-specific fields as key fields in a condition table.
For header fields, use structure KOMKAZ instead of structure KOMPAZ and
USEREXIT_PRICING_PREPARE_TKOMK instead of
USEREXIT_PRICING_PREPARE_TKOMP.
For more information, see Transaction SPRO via the path 'Sales and Distribution -> System Modifications -> Create New Fields (Using Condition Technique) -> New Fields for Pricing' and OSS Note 21040.
REWATD IF U FINDS THIS AS HELPFUL..
Regds
MM

How to add standard field in the CRM Pricing field catalog?

Hello All
I am working on CRM 7.0 , I have a problem with the CRM pricing field catalog that when I am trying to add new field in the catalog the system gives me an error message that the entries should be in the allowed namespace (Y Or Z) but the field I am trying to add in the field catalog is standard field. What should I do to add this field in the field catalog?
The field is : BATCH_ID with data element CRMT_BATCH_ID
Thanks in advance
Jacopo Francoise

Follow note : 441083

Add a new field in field catalog of Material exclusion & inclusion.

Hi All,
I want to add a new field in field catlog Material exclusion & inclusion.
Filed to be added-
Field:MVKE-PRAT6.
Please help me ot add the same.
Thank you
RKMACC

Hi,
You need to go for enhancement,use the exit MV45AFZZ to include into the field catalog,take the help of ABAPer.
Regards
Ram

Pricing - Add to Field Catalog

I want to use KDKG1 Condition Group 1 as a Pricing Field. It is listed in Conditions: Allowed Fields, but when I try to create a Pricing Table, that field is not listed. As a matter of fact, about 30 fields are not listed when trying to create a Pricing Table as compared to what is listed in Allowed Fields. When I try to add it as a new field in Conditions:Allowed Fields, it says 'Choose the key from the allowed namespace' and then it says 'An entry alread exists with the same key'. How can I get this existing field to be available when creating my Pricing table? Do I have to create a Z field and add it to the pricing structures?
Thanks,
Karyn

Refer OSS Note 167926 - Condition Group Field not avail for Condition Tables
Per this note append the field with structure KOMG using an append structure.
Also refer the thread Re: wants to add field in field Catlog
Regards,

How to add new field to Field Catalog in Pricing?

I want to create new field in field catalog (i.e. Average Supply Quantity), and then populate it to Web UI (user must enter value in this field for calculate price in opporunity). What actions I need to do for this?

Hi Pavel,
Fields added to field catalog are to define condition table.
Go to SPRO->CRM->BAsic Functions->Pricing->Define Settings for Pricing->Maintain Field Catalog.
Create the attribute in field catalog with below parameters,
Field Type = 'I' ( item field ) if its header field then it should be H and corresponding structure is CRMT_ACS_H_COM
Implementation type = ' '
Enter field name
Virtual = 'C'
Visibility = ' '
Selection type = 'A'
Enter the data element
Now save the field catalog and click generate.
The next step is to pass value to the field in order to do pricing. This should be done in CRM_COND_COM_BADI. If the field is a
header field then assign value to the field in method HEADER_COMMUNICATION_STRUCTURE else use method ITEM_COMMUNICATION STRUCTURE. You will find the attribute in importing structure of the both the methods. Assign value (i.e. Average Supply Quantity) to the field.
Regards,
Arun

Extending field catalog of application ME using transaction NACE

Hello,
I extended the field catalog of application ME using Transaction NACE. I inserted material field as ZZMATNR but I couldn't find this field at IMG->Materials Management->Inventory Management and Physical Inventory->Output Determination->Maintain Condition Tables->Output: Create Conditions Table ->FieldCatalog.
How can I use ZZMATNR?
Thank you.
Yasar Unalp

Follow the OSS note below (OSS note - 39462) you need to follow the same for your field.
Summary
Symptom
In the message determination for purchasing, the field catalog in Transaction M/60 should be enhanced, for example, with a field for the user ID.
Other terms
USNAM, condition table
Reason and Prerequisites
The communication structure to be maintained can be taken from table T681Z. Table T681Z can be displayed with Transaction SE16.Use 'B' for message determination and application EF for purchase order.
Thus the structure for purchase orders to be maintained is KOMKBEA.
The following section describes how to include field 'User ID' in the structure.If other applications or fields are used, the following example can be used in a modified form.
Solution
1. You must include field ZZUSNAM in communication structure KOMKBEA.In this structure there is an include that is provided for additional fields.In this Include KOMKBZ you must include the field with the name ZZUSNAM. ERNAM can be used as the domain in this case.
2. The same field must also be included in structure KOMB in Include KOMBZ (the same procedure as under point 1).
3. In table T681F use Transaction SM31 with key B, EF to add the same field. You can do this by overwriting an existing field.
As of Release 4. 0 you can use view V_T681F in Transaction SM30 for that purpose. Enter usage 'B', your application and field group '001'.
4. In the message determination, the system runs perform USEREXIT_KOMKBEA_FILL. This perform is in program RVCOMFZZ.
The source code should be changed as follows:
FORM_USEREXIT_KOMKBEA_FILL.
COM_KBEA-ZZUSNAM = SY-UNAME.

Field catalog for internal table in ALV

In my program the internal table consists many fields from various tables and structure doesn't belong to a single data table.
In order to get output in ALV grid following FM has been used
REUSE_ALV_GRID_DISPLAY
for field catalog the fields are defined specifically.
l_fieldcat-fieldname = 'VBELN'.
l_fieldcat-outputlen = 10.
l_fieldcat-seltext_l = 'Billing doc'.
l_fieldcat-no_zero = 'X'.
l_fieldcat-hotspot = 'X'.
append l_fieldcat to p_fieldtab.
..............and so on for all the fields.
Just wanted to know is there any other method to display all the fields of this internal table automatically so each field is not specified specifically.
anya

Hi
Try this instead:
*& Form create_fieldcatalog
* Create a field catalogue from any internal table
*      -->PT_TABLE     Internal table
*      -->PT_FIELDCAT Field Catalogue
FORM create_fieldcatalog
       USING     pt_table     TYPE ANY TABLE
       CHANGING pt_fieldcat TYPE lvc_t_fcat.
DATA:
    lr_tabdescr TYPE REF TO cl_abap_structdescr
, lr_data     TYPE REF TO data
, lt_dfies    TYPE ddfields
, ls_dfies    TYPE dfies
, ls_fieldcat TYPE lvc_s_fcat
CLEAR pt_fieldcat.
CREATE DATA lr_data LIKE LINE OF pt_table.
lr_tabdescr ?= cl_abap_structdescr=>describe_by_data_ref( lr_data ).
lt_dfies = cl_salv_data_descr=>read_structdescr( lr_tabdescr ).
LOOP AT lt_dfies
INTO    ls_dfies.
    CLEAR ls_fieldcat.
    MOVE-CORRESPONDING ls_dfies TO ls_fieldcat.
    APPEND ls_fieldcat TO pt_fieldcat.
ENDLOOP.
ENDFORM.                    "create_fieldcatalog

Field Catalogs in ALV

Hi Friends,
Please help me out, I am new to ABAP.
Please anybody explain me the functionality of Field catalogs in ALVs?
How many methods are there to pass data to ALVs, i.e., in how many ways?
Hope u will help me.

hi,
this will be very helpful for ALV REPORTING.....
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 upto 90 columns in the display with the wide array of display options.
The commonly used ALV functions used for this purpose are;
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
The different steps used for getting the above function modules into use are:
Step 1
DATA DECLARATION
Sap standard type pools: SLIS , KKBLO .
Sap standard tables types taken from the type pools are: SLIS_LAYOUT_ALV ,
                                         SLIS_T_FIELDCAT_ALV,
SLIS_T_LISTHEADER,
SLIS_T_EVENT,
SLIS_SELFIELD.
Internal tables to used in the program declared based on the above table types
DATA: I_LAYOUT TYPE SLIS_LAYOUT_ALV,
            I_FIELDTAB TYPE SLIS_T_FIELDCAT_ALV,
           I_HEADING TYPE SLIS_T_LISTHEADER,
I_EVENTS TYPE SLIS_T_EVENT.
TYPES: KKBLO_SELFIELD TYPE SLIS_SELFIELD.
Step 2 (Optional)
SELECTING THE VARIANTS FOR INITIAL LIST DISPLAY (DEFAULT VARIANT)
The variants in the list display can be both user-specific and general. The user can programmatically set the initial (default) variant for list display.
The default variant can be found using the function module 'REUSE_ALV_VARIANT_DEFAULT_GET'.
Sample code:
CALL FUNCTION 'REUSE_ALV_VARIANT_DEFAULT_GET'
       EXPORTING
            i_save     = variant save condition ( A=all, U = user-specific )
       CHANGING
            cs_variant = internal table containing the program name (and the default variant---optional )
       EXCEPTIONS
            not_found = 2.
The user can also choose from the list of existing variants using the function module REUSE_ALV_VARIANT_F4.
Step 3
DEFININING OUTPUT CHARACTERISTICS: PREPARING DISPLAY FIELDS CATALOG
A field catalog is prepared using the internal table (I_FIELDCAT) of type SLIS_T_FIELDCAT_ALV. 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 to add desired functionality (i.e. Key, Hotspot, Specific headings, Justify, Col. position etc) to certain fields of the output. If not mentioned specifically, then the defaults are taken. The possible values and defaults are listed below.
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.
The minimal field catalog is documented below. This can be done in a routine using a local variable. The user can use the other optional parameters to assign output attributes to different fields in the output, which differ from the default.
A field catalog need not be built-up and passed explicitly only under the following conditions:
1.     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. In this case the attributes of the different fields is taken directly from the table and the attributes (key fields, length, texts etc) need to state explicitly.
2.     all fields in this structure are to be output
3.     The structure name is passed to ALV in the parameter I_STRUCTURE_NAME of the function module REUSE_ALV_LIST_DISPLAY.
All the values entered in the catalog is specific to the particular field whose name is entered in the fieldname FIELDNAME of the fieldcat structure. The name of the table is also entered in the corr. Fieldname TABNAME of the structure.
The different possible attributes are:
     Row_pos (row position): Only relevant if the list output is to be multi-line (two or three lines) by default. So, this attribute can be used maintain certain level of alignment in the output.
                     Value set: 0, 1 3
     Col_pos (column position): This parameter is relevant when the fields in the output are to be different from the sequence of the fields in the internal table used for display.       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 internal table field sequence.
Value set: 0, 1 60
     Fieldname (field name): This is the name of the internal table field for which the parameters are passed in the catalog.
Value set: internal output table field name (required parameter)
     Tabname (internal output table): Name of the internal output table that contains the field FIELDCAT-FIELDNAME above.
                     Value set: SPACE, internal output table name.
     Ref_fieldname (reference 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.
    Value set: SPACE, Data Dictionary field name.
     Ref_tabname (reference table/structure field name): 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).
Value set: SPACE, name of a Data Dictionary structure or table
Link to currency unit
     Cfieldname (currency unit field name): This is used for currency fields that have a reference to any unit field. This is only relevant for amount columns with associated unit. This parameter contains the 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.
Value set: SPACE, output table field name
     Ctabname (internal currency unit field output table): Name of the internal output table containing the FIELDCAT-CFIELDNAME field.
Value set: SPACE, output table field name.
        Link to measurement unit
     Qfieldname (measurement unit 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.
Value set: SPACE, output table field name.
     Qtabname (internal measurement unit field output table): Name of the internal output table containing the FIELDCAT-QFIELDNAME field.
Value set: SPACE, output table field name.
     Outputlen (column width): This parameter is used if the desired output length for a field is desired to be different from the internal output table field. 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.
      Value set: 0 (initial), n.
     Key (key column): By default, the system makes some fields in the output as key fields, provided the fields are key fields in their referencing table. Using this parameter, fields other than key fields of the referencing table can be made key field. This parameter is most important if the output needs to contain some field which are not scrollable or cannot be hidden.
If the internal output table contains fields that are key fields from different tables, then all those fields in the report output becomes unscrollable and cannot be hidden. So, the fields in the output internal table should not be referenced from tables in which they are key fields. Instead, they should be referenced to the tables in which they are not key fields, incase they are not desired as key field in the output.
'X' = key field (key field output in color) and Key fields can not be interactively hidden. Parameter FIELDCAT-NO_OUT must be left initial.
      Value set: SPACE, 'X'.
     Key_sel (hideable key column): This parameter is only relevant for the fields which are made key fields using FIELDCAT-KEY = 'X'. Using this parameter the Key field 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.
Value set: SPACE, 'X'.
     No_out (field in field list): This parameter is used to remove certain fields from the output during initial display. The user can however interactively choose the field for output from the field list in the display variant.
            'X' = field is not displayed in the current list.
        Value set: SPACE, 'X'.
     Tech (technical field): This parameter is used to make certain field display only in the field catalog. The fields with this parameter set cannot be output in the list nor can they be displayed interactively from the catalog.
                    'X' = technical field.
       Value set: SPACE, 'X'.
     Emphasize (highlight columns in color): As name suggests, this field parameter is used to highlight certain field with chosen colors.
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): This parameter is used to make certain field appear as hotspot i.e. a hand is displayed if the cursor is positioned on the field value. Single click on such fields cause the PICK OR F2 events to happen.
         Value set: SPACE, 'X'.
                    'X' = column cells are output as hotspots.
     Fix_column (fix column): This parameter is used to fix certain columns in the output. 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.
                     Value set: SPACE, 'X'.
        'X' = column fixed (does not scroll horizontally).
     Do_sum (sum over column): the user can also call this function interactively.
                  Value set: SPACE, 'X'.
'X' = a sum is calculated over this internal output table field.
     No_sum (sums forbidden): No sum can be calculated over this field, although the data type of the field would allow summing.
         Value set: SPACE, 'X'.
     Icon: The parameter displays certain column contents as icons. The internal output table column contents must be valid icon strings.
                    Value set: SPACE, 'X'.
                     'X' = column contents to be output as an icon.
     Symbol: The internal output table column must be a valid symbol character.
Value set: SPACE, 'X'
                    'X' = column contents are to be output as a symbol.
     Just (justification): This parameter is used for alignment of the contents of the output table. This is only relevant for CHAR or NUMC fields in the output internal table. The justification of the column header always follows the justification of the columns. Independent justification of the column header is not possible.
Value set: SPACE, 'R', 'L', and C.
       ' ' = Default justification for this data type
       'R' = right-justified output
       'L' = left-justified output
       'C' = centered output.
     Lzero (leading zeros): By default ALV outputs NUMC fields right-justified without leading zeros. Using this parameter only the NUMC fields can be displayed with leading zeroes.
                   Value set: SPACE, 'X'.
                    'X' = output with leading zeros.
     No_sign (no +/- sign): This parameter is used to suppress the signs of the output fields. It is only relevant for the 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): To apply the report output formatting options same as in the WRITE statement in report writing.
           Value set: SPACE, template.
The following parameters are used for customizing the texts in the heading of the output of the columns. 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. Popup.
     seltext_l (long field label)
     seltext_m (medium field label)
     seltext_s (short field label)
     reptext_ddic(header) Analogous to the Data element main header
     Ddictxt (specify text) : 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.
Value set: SPACE, 'L', 'M', and S.
Sample code:
Suppose I_PO_DETAILS is an internal table containing two fields EBELN (PO number) and EBELP (PO item no).
DATA: L_FIELDCAT TYPE SLIS_FIELDCAT_ALV.     Local variable to hold the parameters
for a particular field of the field catalog
CLEAR L_FIELDCAT.
L_FIELDCAT-TABNAME   = 'I_PO_DETAILS'.
L_FIELDCAT-FIELDNAME = 'EBELN'.
L_FIELDCAT-KEY = 'X'.         The PO no is made the key field,
                      Colored and non scrollable
L_FIELDCAT-HOTSPOT = 'X'.     The po no becomes a hotspot
L_FIELDCAT-SELTEXT_S = P.O No.
L_FIELDCAT-SELTEXT_M = 'P order No'.
L_FIELDCAT-SELTEXT_L = 'Purchase order No'.
APPEND L_FIELDCAT TO I_FIELDTAB.
CLEAR L_FIELDCAT
L_FIELDCAT-TABNAME   = 'I_PO_DETAILS'.
L_FIELDCAT-FIELDNAME = 'EBELN'.
L_FIELDCAT-KEY = 'X'.         The po item no is made the key field,
                           Colored and non scrollable
L_FIELDCAT-SELTEXT_S = 'Item No'.
L_FIELDCAT-SELTEXT_M = 'Item No`.
L_FIELDCAT-SELTEXT_L = 'PO Item No'.
APPEND L_FIELDCAT TO I_FIELDTAB.
CLEAR L_FIELDCAT
Thus the catalog for the report output is prepared.
Step 4
The next step is to build an event table, which are used for firing both user commands and the system dependent events i.e. top of page, end of page etc.
A list of possible events is populated into an event table (I_EVENTS) when this table is passed to the function module REUSE_ALV_EVENT_NAMES_GET. The return table from this function module contains all the possible events.
The function module contains following import and export parameters.
IMPORTING PARAMETERS: I_LIST_TYPE
This parameter has possible values from 0-4.
The parameter I_LIST_TYPE is of TYPE SLIS_LIST_TYPE and is DEFAULT 0 .
EXPORTING PARAMETERS: I_EVENTS table.
This table is of TYPE SLIS_T_EVENT and returns to the program the name of all the possible events.
The table structure contains the fields:
     I_EVENTS-NAME: Name of the Callback event.
I_EVENTS-FORM: Name of the form routine that should be called in the calling program at the event.
Only events with a form routine name are processed.
The I_EVENTS table returns with the following possible constants:
1.     Slis_ev_item_data_expand TYPE slis_formname VALUE 'ITEM_DATA_EXPAND'.
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 that was expanded interactively by the user.
2.     Slis_ev_reprep_sel_modify TYPE slis_formname VALUE 'REPREP_SEL_MODIFY'.
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 that 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.
3.     Slis_ev_caller_exit_at_start TYPE slis_formname VALUE 'CALLER_EXIT'.
Is called at the beginning of the function module to make special settings. It is not usually used.
4.     Slis_ev_user_command TYPE slis_formname VALUE 'USER_COMMAND'.
As this is a frequently-used Callback event, the form routine can also be passed        directly in the interface by passing the user command in the IMPORTING parameter           I_CALLBACK_USER_COMMAND.
5.     Slis_ev_top_of_page TYPE slis_formname VALUE 'TOP_OF_PAGE'.
   Equivalent to the list processing TOP-OF-PAGE event.
6.     Slis_ev_top_of_coverpage TYPE slis_formname VALUE 'TOP_OF_COVERPAGE'.
The selection information and list status are output together (if they exist) on a separate page by default
7.     Slis_ev_end_of_coverpage TYPE slis_formname VALUE 'END_OF_COVERPAGE'.
Analogously to TOP_OF_COVERPAGE the user can add other information
to the information output by ALV (selection information, list status) at this event.
8.     Slis_ev_foreign_top_of_page TYPE slis_formname VALUE FOREIGN_TOP_OF_PAGE'.
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.
9.     Slis_ev_foreign_end_of_page TYPE slis_formname VALUE 'FOREIGN_END_OF_PAGE'.
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.
10.     Slis_ev_pf_status_set TYPE slis_formname VALUE 'PF_STATUS_SET'.
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.
11.     Slis_ev_list_modify TYPE slis_formname VALUE 'LIST_MODIFY'.
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.
12.     Slis_ev_top_of_list TYPE slis_formname VALUE 'TOP_OF_LIST'.
Information output at the start of the list
13.     Slis_ev_end_of_page TYPE slis_formname VALUE 'END_OF_PAGE'.
Information output at the end of a page. This is only called for printing.
14.     Slis_ev_end_of_list TYPE slis_formname VALUE 'END_OF_LIST'.
Information output at the end of the list
15.     Slis_ev_after_line_output TYPE slis_formname VALUE 'AFTER_LINE_OUTPUT'.
Output information after each output line. Should only be used in justified cases because it costs a lot of performance.
16.     Slis_ev_before_line_output TYPE slis_formname VALUE   'BEFORE_LINE_OUTPUT'.
Output information before each output line. Should only be used in justified cases because it costs a lot of performance.
17.     Slis_ev_subtotal_text TYPE slis_formname VALUE 'SUBTOTAL_TEXT'.
This event table (I_EVENTS) is now checked with the desired constants. If the desired constant is found, then the corresponding field for the FORM NAME is populated with the name of the routine containing the corresponding event.
Sample code :
FORMNAME_TOP_OF_PAGE TYPE SLIS_FORMNAME VALUE 'TOP_OF_PAGE',
FORMNAME_END_OF_PAGE TYPE SLIS_FORMNAME VALUE 'END_OF_PAGE', FORMNAME_USER_COMMAND TYPE SLIS_FORMNAME VALUE 'USER_COMMAND'.
DATA: L_I_EVENT TYPE SLIS_ALV_EVENT.
CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
       EXPORTING
           I_LIST_TYPE = 0
       IMPORTING
            ET_EVENTS   = I_EVENTS.
READ TABLE I_EVENTS WITH KEY NAME = SLIS_EV_TOP_OF_PAGE
                           INTO L_I_EVENT.
IF SY-SUBRC = 0.
    MOVE FORMNAME_TOP_OF_PAGE TO L_I_EVENT-FORM.
    APPEND L_I_EVENT TO I_EVENTS.
ENDIF.
READ TABLE I_EVENTS WITH KEY NAME = SLIS_EV_END_OF_PAGE
                           INTO L_I_EVENT.
IF SY-SUBRC = 0.
    MOVE FORMNAME_END_OF_PAGE TO L_I_EVENT-FORM.
    APPEND L_I_EVENT TO I_EVENTS.
ENDIF.
CLEAR L_I_EVENT.
READ TABLE I_EVENTS WITH KEY NAME = SLIS_EV_USER_COMMAND
                           INTO L_I_EVENT.
IF SY-SUBRC = 0.
    MOVE FORMNAME_USER_COMMAND TO L_I_EVENT-FORM.
    APPEND L_I_EVENT TO I_EVENTS.
ENDIF.
This will prepare the events table for the report.
The report will contain three forms for the above events:
1.     FORM TOP_OF_PAGE : This form will contain the top of page event for the report i.e header etc
Using the function module REUSE_ALV_COMMENTARY_WRITE, the internal table containing the headings for top of page event can be passed to the list output. Also, any logo specific to the report can be passed to the function module.
2.     FORM END_OF_PAGE : This form will contain the end of page event for the report i.e footer etc
3.     FORM USER_COMMAND : This form will contain the desired user command i.e pick/line selection
Step 5
A layout is build for the report output list description USING the internal table declared above (I_LAYOUT).
Output list description structure.
     The parameters are described under the following heads:
     Display options
     Exceptions
     Totals
     Interaction
     Detail screen
     Display variants (only for hierarchical-sequential lists)
     Color
     Other
The layout table is of type slis_layout_alv_spec and has the following fields:
Display options
1. Colwidth_optimize (1) TYPE c: This parameter optimizes the length of the different columns in the output. The width of the different col. now depends on the max. Length of the data in the column.
Value set: SPACE, 'X'
'X' = optimizes the column width so that all contents are displayed completely.
2. No_colhead(1) TYPE c : This parameter suppresses the column headings
Value set: SPACE, 'X'.
'X' = column headers are not output
3. No_hotspot(1) TYPE c : The heading of the report output are not output as hotspot.
Value set: SPACE, 'X'.
'X' = column headers are not output as hotspot
4. Zebra(1) TYPE c : The report is output in the striped pattern.
Value set: SPACE, 'X'.
'X' = striped pattern (e.g. for wide lists)
5. No_vline(1) TYPE c : The report output contains columns only separated by space and no lines. It is not relevant for: hierarchical-sequential lists and multiple-line lists.
Value set: SPACE, 'X'.
'X' = columns separated by SPACE
6. No_min_linesize(1) TYPE c : The report line size is equal to the width of the list. It is not relevant for block lists.
Value set: SPACE, 'X.
'X' = line size depends on list width
' ' = Line size is set to 80 or MIN_LINESIZE (if > 0) .
7. Min_linesize LIKE sy-linsz: The report output contains a minimum possible length of line. If initial min_linesize is set to 80 by default, then this parameter is used to customize it. The prerequisite for this is that the parameter no_min_linesize should be ' '.
Value set: 0, 10 - 250
If the list is wider, the format uses the list width (maximum 250 or MAX_LINESIZE (if > 0)).
8. Max_linesize LIKE sy-linsz: The default max. Linesize is 250. To change this default value, this parameter can interactively-define the maximum list width setting.
Value set: 0, 80 - 1020
9. Window_titlebar LIKE rsmpe-tittext: To set the titlebar on the report output.
           10. No_uline_hs(1) TYPE c.
Exceptions
11. Lights_fieldname TYPE slis_fieldname: Internal output table field containing the codes of exceptions to be output.
                  Output table field code: '1' = red traffic light
                                '2' = yellow traffic light
                                     '3' = green traffic light Fieldname for exception
     Value set: SPACE, internal output table field name.
12. Lights_tabname TYPE slis_tabname: Name of the internal output table that contains the field in the parameter LIGHTS_FIELDNAME. If LIGHTS_FIELDNAME is not empty, this field must also be filled for hierarchical-sequential lists. Only relevant for hierarchical-sequential lists.
.     Value set: SPACE, internal output table name.
13. Lights_rollname LIKE dfies-rollname: The documentation of this data element is displayed when you call F1 help for an exception column.
Value set: SPACE, data element name.
           14. Lights_condense(1) TYPE c : If a list record is output with 'red traffic light', each
           Subtotal that includes this record is also output with 'red traffic light'.
           Value set: SPACE, 'X'
           'X' = the 'maximum' exception of the items in the subtotal is output at subtotal level.
Sums
15. No_sumchoice(1) TYPE c : This parameter allows the choice for summing up
Only by fieldcatalog.
Value set: SPACE, 'X'
'X' = fields which are to be summed, passed by the calling program (FIELDCAT-DO_SUM = 'X'). The user should not be able to change this value interactively.
16. No_totalline(1) TYPE c : Removes the option of having totals after sub-totals.
Value set: SPACE, 'X'
'X' = no total record is to be output. Subtotals can still be calculated and output. The fields in the subtotals are flagged DO_SUM = 'X' in the field list.
17. No_subchoice(1) TYPE c : Does not allow the user to interactively change the field chosen for subtotals.
Value set: SPACE, 'X'
'X' = value whose change triggers subtotals, provided by the calling program. The user should not be able to change this value interactively.
18. No_subtotals(1) TYPE c : No subtotals possible
Value set: SPACE, 'X'
'X' = no subtotals.
19. Numc_sum(1) TYPE c : Totals only possible for NUMC-Fields.
20. No_unit_splitting TYPE c: No separate total lines by inh.units
21.totals_before_items TYPE c: Display totals before the items
22. Totals_only(1) TYPE c : Show only totals
Value set: SPACE, 'X'
'X' = only total records are output.
23. Totals_text(60) TYPE c : Text for 1st col. in totals
Value set: SPACE, string (max.60)
' ' = The first column in the total record contains an appropriate number of '*'s to indicate the total by default. If the first column is wide enough, the string 'Total' is output after the asterisks.
'String = The string passed is output after the total indicated by '*', if the column is wide enough.
24. Subtotals_text(60) TYPE c : Texts for subtotals
Value set: SPACE, string (max.60)
' ' = In the first column of subtotal records, the subtotal is indicated by an appropriate number of '*' by default. If the first column is not a subtotal criterion, the string 'Total' is output after the asterisks, if the column is wide enough.
'String = the string passed is output after the subtotal indicated by '*', if the column is wide enough and the first column is not a subtotal criterion. If it is a subtotal criterion, its value is repeated after the total, if the column is wide enough.
Interaction
25. Box_fieldname TYPE slis_fieldname: Fieldname for checkbox in the report output. If the list has checkboxes at the start of records (for selecting several records), this parameter contains the internal output table field name indicated by the checkbox selection column. The field is a checkbox at the start of list records without a list header.
Value set: SPACE, internal output table field name
26. Box_tabname TYPE slis_tabname: Name of the internal output table that contains the field in the parameter BOX_FIELDNAME. If BOX_FIELDNAME is not empty, this field must also be filled for hierarchical-sequential lists.
Value set: SPACE, internal output table name.
27. Box_rollname LIKE dd03p-rollname: rollname for checkbox
28. Expand_fieldname TYPE slis_fieldname: fieldname flag expand. The user can show or hide the items by clicking on the folder symbol (hotspot). If the items for a header entry are only to be read by the calling program and passed to ALV when a header has been expanded interactively, this can be controlled via the CALLBACK event        'ITEM_DATA_EXPAND'.
29. Hotspot_fieldname TYPE slis_fieldname: Used to make the fieldname flag hotspot.
30. No_input(1) TYPE c : The fields are only display fields.
      Value set: SPACE, 'X'
'X' = all ready-for-input fields in a list are displayed as not ready-for-input. (Record selection checkboxes and fields which can be made ready-for-input via the field list parameter FIELDCAT-INPUT = 'X')
31. F2code LIKE sy-ucomm: To assign an ALV standard function code to double-click (F2), assign the function code to this parameter. Ex.: to assign the ALV standard function 'Detail' ('&ETA') to F2.
                  => LAYOUT-F2CODE = '&ETA'.
Value set: SPACE, function code
32. Confirmation_prompt: confirm. Prompt when leaving
Value set: SPACE, 'X'
'X' = if one of the functions Back (F03)', Exit (F15)' or Cancel (F12)' occurs, a confirmation prompt appears.
33. Key_hotspot(1) TYPE c : The key fields are displayed as hotspot. The columns defined in the field catalog as key fields (FIELDCAT-KEY = 'X') are output as hotspots, i.e. clicking on a key column (highlighted in color in the list) calls the function under F2.
Value set: SPACE, 'X'.
34. Reprep(1) TYPE c : report report interface active.
35. Group_buttons(1) TYPE c : group-buttons for COL1 - COL5 . Group output fields via FIELDCAT-SP_GROUP in the field list, and pass the group name to the list module in the interface parameter IT_SPECIAL_GROUPS.
Value set: SPACE, 'X'.
36. No_keyfix(1) TYPE c : Used to make the key fields scrollable.
Value set: SPACE, 'X'.
' ' = The key columns defined in the field catalog by FIELDCAT-KEY = 'X' are fixed in the list output. These columns do not scroll horizontally. The item table key columns are fixed in hierarchical-sequential lists. The header table key fields are not considered here.
'X' = key columns not fixed
37. Get_selinfos(1) TYPE c : To read selection screen.
Value set: SPACE, 'X'.
If the calling program is a report with an ABAP/4 selection screen, setting this parameter makes ALV read the selection screen again. If the selections are read successfully, a pushbutton, via which the user can call a popup which lists the report selections in a simple form, becomes active on the results list output by ALV.
38.     group_change_edit(1) TYPE c : Settings by user for new group
Value set: SPACE, 'X'
'X' = the user can enter a format option for each sort criterion in the sort/subtotal popup, for the list format when this value changes (e.g. new page or underline).
39.     No_scrolling(1) TYPE c : Does not allow scrolling of the list to the right.
Value set: SPACE, 'X'.
40. Expand_all(1) TYPE c : Expand all positions
Detailed screen
40.     Detail_popup(1) TYPE c : show detail in popup.
Value set: SPACE, 'X'
' ' = List record detail display in full-screen mode, with top-of-page.
'X' = list record detail display in popup (without top-of-page).
41. Detail_initial_lines(1) TYPE c : show also initial lines
Value set: SPACE, 'X'
' ' = Only fields whose contents are not initial are output in the detail view.
'X' = initial field contents are also output in detail.
41.     detail_titlebar(30) type c : Titlebar for detail screen
Value set: SPACE, string (max.30)
` ' = ' Detail: Display' is output as the title of the detail window.
              'String = the string passed is output as the title of the detail window.
Display variants
42. Header_text (20) TYPE c: Text for header button. Only relevant for hierarchical-sequential lists. You can toggle between display field and field list views via pushbuttons in the display variant definition popup for hierarchical-sequential lists. The views refer to the hierarchy level of the fields. This is technically a toggle between the header table and item table fields.
Value set: SPACE, CHAR (20)
' ' = The header table field pushbutton text is 'Header' by default.
CHAR (20) = header table field pushbutton text.
43.item_text(20) TYPE c : Text for item button. Only relevant for hierarchical-sequential lists. You can toggle the view between the display fields and the field list via pushbuttons in the display variant definition popup for hierarchical-sequential lists. The views refer to the hierarchy level of the fields. This is technically a toggle between the header table and item table fields.
Value set: SPACE, CHAR (20)
' ' = The pushbutton text for the item table fields is 'Item' by default.
CHAR (20) = item table field pushbutton text.
44.default_ item(1) TYPE c : Items as default. Only relevant for hierarchical-sequential lists.
     Value set: SPACE, 'X'
' ' = The header table fields are displayed by default in the display variant definition popup. The user can switch to the item table fields interactively.
'X' = the item table fields are displayed by default in the display variant Definition Popup.    The user can switch to the header table fields interactively.
Colour
45. Info_fieldname TYPE slis_fieldname: infofield for listoutput. A whole list record can be colored individually using a color code in a column of the internal output table for the record. Assign the name of the field containing the color code to this parameter.
Value set: SPACE, internal output table field name
The internal output table field must be of type CHAR(3).
The code must have the following syntax: 'Cxy':
        C = color (all codes must start with 'C')
        X = color number ('1'-'9')
        Y = bold ('0' = off, '1' = on)
46. Coltab_fieldname TYPE slis_fieldname: Cells can be colored individually using a color code which is contained in a column of the internal output table for the record containing the cell. Assign the name of the field to this parameter.
Others
47. List_append(1) TYPE c : no call screen. It is only useful to output block-lists without specifying the above modules if the number of list blocks exceeds, or may exceed, the maximum number specified in the block module documentation. These operations are not possible for user-defined block lists.
Example code :
       I_LAYOUT-f2code       = ws_fcode.
       I_LAYOUT-zebra        = 'X'.
I_LAYOUT-colwidth_optimize = 'X'.
I_LAYOUT-no_keyfix = 'X'.
I_LAYOUT-get_selinfos = 'X'.
I_LAYOUT-no_hotspot = 'X'.
       I_LAYOUT-no_input = 'X'.
I_LAYOUT-hotspot_fieldname = FIELDNAME.
I_LAYOUT-no_input          = X.
I_LAYOUT-no_vline          = `X.
I_LAYOUT-no_colhead        = .
I_LAYOUT-lights_condense   = ` `.
I_LAYOUT-totals_text       = ` `.
I_LAYOUT-subtotals_text    = ` `.
I_LAYOUT-totals_only       = ` `.
I_LAYOUT-key_hotspot       = X.
I_LAYOUT-detail_popup      = X.
I_LAYOUT-group_change_edit = X.
I_LAYOUT-GROUP_BUTTONS     = X.
Step 6
This step is required to get the selection screen information in the report output.
The prerequisite for this is to set the parameter LAYOUT-GET_SELINFOS of the IMPORTING structure.
The parameters to be passed in the IS_SEL_HIDE table are:
o mode:              'R' = only the entries passed in the internal table IS_SEL_HIDE-T_ENTRIES
Are output in the pop up. Selection info, which the list tool read in the selection screen (when called by a report with a selection screen), is replaced by the values passed.
'S' = the selection info which the list tool read in the selection screen of the calling report are modified by the entries in the table IS_SEL_HIDE-T_ENTRIES.
o t_entries:         Selection info table
o t_entries-mode:   'A' = output the selection info for the current table record in the info popup.
'D' = do not output select option or SELNAME parameter selection info in   the popup.
o t_entries-selname: (only used in t_entries-mode = 'D') : Name of the select option or parameter.
The following table fields are only used in t_entries-mode = 'A'. They contain the selection information to be added.
     t_entries-field: DDIC field name of the field for which selection information is to be output.
     t_entries-table: DDIC table names of t_entries-field.
     t_entries-stext: Field name in info popup.
     If t_entries-field and t_entries-table have been entered, this text is taken from DDIC.
     t_entries-valuf: Selection condition 'from' value (external format)
     t_entries-valut: Selection condition 'to' value (external format)
     t_entries-sign0: (I)nclusive (E)xclusive
     t_entries-option: All values of the select options Option field allowed.
Step 6
The Table IT_SORT is populated with the sort criteria for the different fields.
The caller specifies the sorting and/or subtotaling of the basic list in the internal table IT_SORT.
This internal table has the following fields:
     o spos : Sort sequence
     o fieldname : Internal output table field name
     o tabname : Only relevant for hierarchical-sequential lists. Name of the internal output table.
     o up : 'X' = sort in ascending order
     o down : 'X' = sort in descending order
     o subtot : 'X' = subtotal at group value change
     o group : '* ' = new page at group value change ,'UL' = underline at group value change
                         Step 7
The final step in the output of the report is the use of two ALV functions modules.
1.     REUSE_ALV_FIELDCATALOG_MERGE
2.     REUSE_ALV_LIST_DISPLAY
The first function module is used to pass the field catalog to the report output and merge it with the internal output table.
FUNCTION reuse_alv_fieldcatalog_merge.
""Lokale Schnittstelle:
* IMPORTING
*"             VALUE(I_PROGRAM_NAME) LIKE SY-REPID OPTIONAL
*"             VALUE(I_INTERNAL_TABNAME) TYPE SLIS_TABNAME OPTIONAL
*"             VALUE(I_STRUCTURE_NAME) LIKE DD02L-TABNAME OPTIONAL
*"             VALUE(I_CLIENT_NEVER_DISPLAY) TYPE SLIS_CHAR_1
*"                             DEFAULT 'X'
*"             VALUE(I_INCLNAME) LIKE TRDIR-NAME OPTIONAL
*"       CHANGING
*"             VALUE(CT_FIELDCAT) TYPE SLIS_T_FIELDCAT_ALV
*"       EXCEPTIONS
*"              INCONSISTENT_INTERFACE
*"              PROGRAM_ERROR
Import parameters
I_PROGRAM_NAME: Program in which the internal output table is declared and populated
I_INTERNAL_TABNAME: Internal output table name
I_STRUCTURE_NAME: Structure name (structure, table, and view)
I_CLIENT_NEVER_DISPL: Hide client fields default X
I_INCLNAME: Data declarations include name
CHANGING parameter
CT_FIELDCAT: Field catalog with field descriptions
The variant based on a program-internal table should only be used for rapid prototyping since the following restrictions apply:
1.   Performance is affected since the code of the table definition must always be read and interpreted at runtime.
2.   Dictionary reference are only considered if the keywords LIKE or INCLUDE STRUCTURE (not TYPE) are used.
Step 8
The other function module is used to display the internal output table with the contents
FUNCTION reuse_alv_list_display.
""Lokale Schnittstelle:
* IMPORTING
*"             VALUE(I_INTERFACE_CHECK) DEFAULT SPACE
*"             VALUE(I_CALLBACK_PROGRAM) LIKE SY-REPID DEFAULT SPACE
*"             VALUE(I_CALLBACK_PF_STATUS_SET) TYPE SLIS_FORMNAME
*"                             DEFAULT SPACE
*"             VALUE(I_CALLBACK_USER_COMMAND) TYPE SLIS_FORMNAME
*"                             DEFAULT SPACE
*"             VALUE(I_STRUCTURE_NAME) LIKE DD02L-TABNAME OPTIONAL
*"             VALUE(IS_LAYOUT) TYPE SLIS_LAYOUT_ALV OPTIONAL
*"             VALUE(IT_FIELDCAT) TYPE SLIS_T_FIELDCAT_ALV OPTIONAL
*"             VALUE(IT_EXCLUDING) TYPE SLIS_T_EXTAB OPTIONAL
*"             VALUE(IT_SPECIAL_GROUPS) TYPE SLIS_T_SP_GROUP_ALV
*"                             OPTIONAL
*"             VALUE(IT_SORT) TYPE SLIS_T_SORTINFO_ALV OPTIONAL
*"             VALUE(IT_FILTER) TYPE SLIS_T_FILTER_ALV OPTIONAL
*"             VALUE(IS_SEL_HIDE) TYPE SLIS_SEL_HIDE_ALV OPTIONAL
*"           VALUE(I_DEFAULT) DEFAULT 'X'
"             VALUE(I_SAVE) DEFAULT SPACE
"             VALUE(IS_VARIANT) LIKE DISVARIANT
"                             STRUCTURE DISVARIANT DEFAULT SPACE
"             VALUE(IT_EVENTS) TYPE SLIS_T_EVENT OPTIONAL
"             VALUE(IT_EVENT_EXIT) TYPE SLIS_T_EVENT_EXIT OPTIONAL
"             VALUE(IS_PRINT) TYPE SLIS_PRINT_ALV OPTIONAL
"             VALUE(IS_REPREP_ID) TYPE SLIS_REPREP_ID OPTIONAL
"             VALUE(I_SCREEN_START_COLUMN) DEFAULT 0
"             VALUE(I_SCREEN_START_LINE) DEFAULT 0
"             VALUE(I_SCREEN_END_COLUMN) DEFAULT 0
"             VALUE(I_SCREEN_END_LINE) DEFAULT 0
"       EXPORTING
"             VALUE(E_EXIT_CAUSED_BY_CALLER)
"             VALUE(ES_EXIT_CAUSED_BY_USER) TYPE SLIS_EXIT_BY_USER
"       TABLES
"              T_OUTTAB
"       EXCEPTIONS
"              PROGRAM_ERROR
Import parameters
I_INTERFACE_CHECK: Interface consistency check log output.
I_CALLBACK_PROGRAM: Name of the calling program
I_CALLBACK_PF_STATUS_SET: Set EXIT routine to status.
I_CALLBACK_USER_COMMAND: EXIT routine for command handling
I_STRUCTURE_NAME: Internal output table structure name
IS_LAYOUT: List layout specifications
IT_FIELDCAT: Field catalog with field descriptions
IT_EXCLUDING: Table of inactive function codes
IT_SPECIAL_GROUPS: Grouping fields for column selection
IT_SORT: Sort criteria for first list display
IT_FILTER: Filter criteria for first list output
IS_SEL_HIDE     : Selection information modification
I_DEFAULT:      Initial variant active/inactive logic
I_SAVE: Variants can be saved
IS_VARIANT     : Variant information
IT_EVENTS: Table of events to perform IT_EVENT_EXIT : Standard fcode exit requests table
IS_PRINT: Print information
IS_REPREP_ID: Initialization keys for Re/Re interface
I_SCREEN_START_COLUMN: Coordinates for list in dialog box
I_SCREEN_START_LINE: Coordinates for list in dialog box
I_SCREEN_END_COLUMN: Coordinates for list in dialog box
I_SCREEN_END_LINE: Coordinates f

New field catalog VOLEH does not display while creating a new table

Dear Gurus,
I added new field as VOLEH in field catalog. However while I am creating a new table, new field (VOLEH) does not showed in field catalog...
How can I fix this error?
Kind Regards,

HI
Check once again in IMG>SD>Basic func>Pricing >Pricing control>define condition table>conditions : allowed fields> go to new entries then press F4
check here newly created field is there or not
(or) when creation of condition table check properly next page button in menu bar
still if its not found
Note 21040 - Allowed Fields not appearing for condition table
or check this link
http://www.sap-basis-abap.com/sd/how-to-add-new-fields-to-field-catalog.htm
Regards,
Krishna.

Following IMG doc - Field Catalog Add

Similar Messages

Maybe you are looking for