ALV drilldown not possible in report once i apply layout save option

Hi All,
I have developed one ALV report.
Firstly i use drill down in the report means call transaction by double click event.
Then i apply layout save option in same report.
But as soon as i apply layout save option the call transaction is not possible.
How to resolve this problem.
Regards,
Deepak.

Hi,
when you applied save button did you use any other PF status apart froms standard ALV pf-status..
if so...
go to the pf-status which you have declared ...
then go to the function keys...
under Recommended Function Key Settings for the F2 key set the function code as
&IC1
this will resolve your issue
Regards,
Siddarth

Similar Messages

Layout save option in VA05 not active

Dear all,
I have little problem in VA05,
in this report layout save option is not active ,
can anyone guide how to activate it.
Regards,
Talwinder

Hi,
Firstly you should save your layout as system-specific, then you have to go menu>Settings>Layouts-->Administration... to define your layout as default settings.
As thus, when you execute VA05, the new layout will be applied correctly.
Good luck
Z.T

Alv drilldown-fields are hiding in secondary list-when layout option used

hey guys,
i displayed alv grid using fms.
the basic list has default layout option.
but when user gives a deault layout,and try to see secondary list,the fields appear as hidden.
one has to unhide them manualy to see.

Kumar,
Check the Field catalog Before displaying Secondary list, If NO_OUT is set for Hidden fields.
Thanks,
Kishore

Multiple selection in the ALV is not possible after system upgrade

Hi Colleague,
I had been using an ALV, which was performing as desired before, but recently we had a system upgrade to NW7.0 and after that in this ALV multiple selection of records/rows is not allowed.
The colleagues who upgraded the system suggested that this may be because this ALV is instantiated at many places. I would request you to kindly provide a solution for the same ASAP, as I am not able to proceede ahead.
Warm regards,
Roopesh

Hi all,
Thanks for your replies, I had figured out the actual problem. The reason was, the referance of the selected rows was lost as I was doing bind elements to the context after moving to wddomodify.
So I figured out an alternative solution to avoid binding on selection of records.
Best regards,
Roopesh
Edited by: Roopesh Dolle on Apr 14, 2011 7:04 AM
Edited by: Roopesh Dolle on Apr 14, 2011 7:05 AM

Issue is TEXT_IO application API is not working in report builder 10g.

Issue is TEXT_IO application API is not working in report builder 10g.
TEXT_IO application api is working in report builder 6i. (Not working in upgrade from Oracle EBiz 11i to Oracle Ebiz R12)
I saw that details in some forums, client_text_io is available for form builder 10g.
Is any other api available for report builder 10g?
If it is available what steps we need to do?

All the CLIENT_% procedures are part of webutil in Forms. Forms uses the Java applet on the client PC to perform actions on the local PC via webutil. This is not possible for Reports.
You can still use text_io on the server, but you need some other way to copy the files to/from the client PC.
I wonder how you used the functionality in EBS R11. Even R11 uses web reports, so text_io already worked on the server, not the client PC.

BDC transaction "The function is not possible"

Dear Experts,
I have made a BDC transaction program according to recording from SHDB in order to have batch transaction for FB50.
However, when I run the program. It shows an error "The function is not possible". But when I press the "Save" button manually, the function passed and result is saved. Just do not know what happens.
report YFB50 no standard page heading line-size 255.
include bdcrecx1.
type-pools : TRUXS.
data : rawdata type TRUXS_T_TEXT_DATA.
parameters: sfile TYPE localfile default 'C:\fb50.txt'.
parameters: plant like BKPF-BUKRS default '1000'.
data: pfile type string.
data: post_date(8) type c.
data: record_count(2) type c.
data: v_HKONT(19) type c.
data: v_SHKZG(19) type c.
data: v_WRBTR(19) type c.
data: v_SGTXT(19) type c.
data: v_KOSTL(19) type c.
***    DO NOT CHANGE - the generated data section - DO NOT CHANGE    ***
*   If it is nessesary to change the data section use the rules:
*   1.) Each definition of a field exists of two lines
*   2.) The first line shows exactly the comment
*       '* data element: ' followed with the data element
*       which describes the field.
*       If you don't have a data element use the
*       comment without a data element name
*   3.) The second line shows the fieldname of the
*       structure, the fieldname must consist of
*       a fieldname and optional the character '_' and
*       three numbers and the field length in brackets
*   4.) Each field must be type C.
*** Generated data section with specific formatting - DO NOT CHANGE ***
data: begin of record occurs 0,
* data element: HKONT
        HKONT(010),
* data element: SHKZG
        SHKZG(007),
* data element: WRBTR
        WRBTR(017),
* data element: SGTXT
        SGTXT(050),
* data element: KOSTL
        KOSTL(010),
      end of record.
*** End generated data section ***
start-of-selection.
pfile = sfile.
concatenate sy-datum+6(2) sy-datum+4(2) sy-datum+0(4) into post_date.
CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
     FILENAME                = pfile
TABLES
     DATA_TAB                = rawdata
EXCEPTIONS
     CONVERSION_ERROR        = 1
     FILE_OPEN_ERROR         = 2
     FILE_READ_ERROR         = 3
     INVALID_TYPE            = 4
     NO_BATCH                = 5
     UNKNOWN_ERROR           = 6
     INVALID_TABLE_WIDTH     = 7
     GUI_REFUSE_FILETRANSFER = 8
     CUSTOMER_ERROR          = 9
     OTHERS                  = 10.
IF SY-SUBRC <> 0.
     WRITE:/ 'SY-SUBRC:', SY-SUBRC.
ENDIF.
CALL FUNCTION 'TEXT_CONVERT_CSV_TO_SAP'
EXPORTING
     I_FIELD_SEPERATOR = ';'
     I_TAB_RAW_DATA = rawdata
TABLES
     I_TAB_CONVERTED_DATA = record
EXCEPTIONS
     CONVERSION_FAILED = 1
     OTHERS = 2.
perform bdc_dynpro      using 'SAPMF05A' '1001'.
*Input header information
perform bdc_field       using 'BDC_OKCODE'
                              '/00'.
*Document Date
perform bdc_field       using 'ACGL_HEAD-BLDAT'
                              post_date.
*Posting Date
perform bdc_field       using 'ACGL_HEAD-BUDAT'
                              post_date.
perform bdc_field       using 'BDC_OKCODE'
                              '/ECCDE'.
perform bdc_dynpro      using 'SAPLACHD' '1000'.
perform bdc_field       using 'BDC_OKCODE'
                              '=ENTR'.
*Company Code
perform bdc_field       using 'BKPF-BUKRS'
                              plant.
perform bdc_dynpro      using 'SAPMF05A' '1001'.
*Input header information
perform bdc_field       using 'BDC_OKCODE'
                              '/BU'.
*Document Date
perform bdc_field       using 'ACGL_HEAD-BLDAT'
                              post_date.
*Posting Date
perform bdc_field       using 'ACGL_HEAD-BUDAT'
                              post_date.
*Input item text
loop at record.
*write sy-tabix to record_count.
*concatenate 'ACGL_ITEM-HKONT(' record_count ')' into v_HKONT.
*concatenate 'ACGL_ITEM-SHKZG(' record_count ')' into v_SHKZG.
*concatenate 'ACGL_ITEM-WRBTR(' record_count ')' into v_WRBTR.
*concatenate 'ACGL_ITEM-SGTXT(' record_count ')' into v_SGTXT.
*concatenate 'ACGL_ITEM-KOSTL(' record_count ')' into v_KOSTL.
perform bdc_field       using v_HKONT
                              record-HKONT.
perform bdc_field       using v_SHKZG
                              record-SHKZG.
perform bdc_field       using v_WRBTR
                              record-WRBTR.
perform bdc_field       using v_SGTXT
                              record-SGTXT.
perform bdc_field       using v_KOSTL
                              record-KOSTL.
endloop.
perform bdc_transaction using 'FB50'.
Here is my input:
206090203;H;41.74;abc;MISHK
206090203;H;14.36;abc;FACHK
206100100;S;41.74;def;MISHK
206070100;S;14.36;def;FACHK
Regards,
Cato

Make your LOOP.... ENDLOOP... Like this
LOOP AT RECORD.
perform bdc_dynpro      using 'SAPMF05A' '1001'.
*Input header information
perform bdc_field       using 'BDC_OKCODE'
                              '/00'.
*Document Date
perform bdc_field       using 'ACGL_HEAD-BLDAT'
                              post_date.
*Posting Date
perform bdc_field       using 'ACGL_HEAD-BUDAT'
                              post_date.
perform bdc_field       using 'BDC_OKCODE'
                              '/ECCDE'.
perform bdc_dynpro      using 'SAPLACHD' '1000'.
perform bdc_field       using 'BDC_OKCODE'
                              '=ENTR'.
*Company Code
perform bdc_field       using 'BKPF-BUKRS'
                              plant.
perform bdc_dynpro      using 'SAPMF05A' '1001'.
*Input header information
perform bdc_field       using 'BDC_OKCODE'
                              '/BU'.
*Document Date
perform bdc_field       using 'ACGL_HEAD-BLDAT'
                              post_date.
*Posting Date
perform bdc_field       using 'ACGL_HEAD-BUDAT'
                              post_date.
*Input item text
**loop at record.
*write sy-tabix to record_count.
*concatenate 'ACGL_ITEM-HKONT(' record_count ')' into v_HKONT.
*concatenate 'ACGL_ITEM-SHKZG(' record_count ')' into v_SHKZG.
*concatenate 'ACGL_ITEM-WRBTR(' record_count ')' into v_WRBTR.
*concatenate 'ACGL_ITEM-SGTXT(' record_count ')' into v_SGTXT.
*concatenate 'ACGL_ITEM-KOSTL(' record_count ')' into v_KOSTL.
perform bdc_field       using v_HKONT
                              record-HKONT.
perform bdc_field       using v_SHKZG
                              record-SHKZG.
perform bdc_field       using v_WRBTR
                              record-WRBTR.
perform bdc_field       using v_SGTXT
                              record-SGTXT.
perform bdc_field       using v_KOSTL
                              record-KOSTL.
**endloop.
perform bdc_transaction using 'FB50'.
ENDLOOP.
Now should work fine..

Error when save project Access via 'NULL' object reference not possible PLM

Dear All,
we are using cProject (PLM)4.0
When i create project & try to save ,system gives me error 'Access via 'NULL' object reference not possible'
Steps
1.Create project & element
2.save
showing below error
Note
The following error text was processed in the system PLD : Access via 'NULL' object reference not possible.
The error occurred on the application server Ndimdev_PLD_20 and in the work process 0 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Error code: ICF-IE-http -c: 300 -u: PLMUSER1 -l: E -s: PLD -i: Ndimdev_PLD_20 -w: 0 -d: 20090702 -t: 164926 -v: RABAX_STATE -e: OBJECTS_OBJREF_NOT_ASSIGNED
Please do needful
Regards
Ravindra

Hi,
Put a break point and check whther ur node and
element instantiation is properly done.
Thanks,
Divya.S

Payment not possible because of reported error Message no. FZ311

i am a fresher in FI module... kidly give the solution how to solve the error in automatic payment program..f110...
i have attached my log here....
Job log overview for job:
F110-20140315-A1    -X / 13365701
Date
Time
Message text
Message class
Message no.
Message type
ABAP program
Screen no.
15.03.2014
13:36:59
Job started
     00
    516
     S
15.03.2014
13:36:59
Step 001 started (program SAPF110S, variant &0000000002023, user ID RAGU)
     00
    550
     S
15.03.2014
13:37:00
Log for proposal run for payment on 15.03.2014, identification A1
     FZ
    402
     S
15.03.2014
13:37:04
>
     FZ
    693
     S
15.03.2014
13:37:04
> Additional log for vendor 100263 company code ALRF
     FZ
    691
     S
15.03.2014
13:37:04
>
     FZ
    693
     S
15.03.2014
13:37:04
>
Due date determination additional log
     FZ
    799
     S
15.03.2014
13:37:04
>
Document 6
004 line item 001 via INR      200.000,00-
     FZ
    700
     S
15.03.2014
13:37:04
> Terms of payment: 15.03.2014    0 0,000 % 0 0,000 %    0
     FZ
    701
     S
15.03.2014
13:37:04
> 00 days grace period is being considered
     FZ
    726
     S
15.03.2014
13:37:04
>   Payment must take place before 15.03.2014; next payment on 16.03.2014
     FZ
    728
     S
15.03.2014
13:37:04
> Item is due with 0,000 % cash discount
     FZ
    721
     S
15.03.2014
13:37:04
>
     FZ
    693
     S
15.03.2014
13:37:04
>
Payment method selection additional log
     FZ
    699
     S
15.03.2014
13:37:04
>
Payment me
thod selection for items due now to the amount of INR      200.000,00-
     FZ
    601
     S
15.03.2014
13:37:04
> Payment method "C" is being checked
     FZ
    603
     S
15.03.2014
13:37:04
> Street or P.O. box entry is missing
     FZ
    617
     S
15.03.2014
13:37:04
> No permitted payment method exists
     FZ
    608
     S
15.03.2014
13:37:04
Information re. vendor 100263 / paying company code ALRF ...
     FZ
    305
     S
15.03.2014
13:37:04
... payment not possible because of reported error
     FZ
    311
     S
15.03.2014
13:37:05
End of log
     FZ
    398
     S
15.03.2014
13:37:06
Job finished
     00
    517
     S

Hello Experts,
I am blocked with a strange issue which is similar to FZ311 mentioned above.
Enclosing the screenshot for your reference.
I am bit confused whether anything needs to be configured within the FBZP or it is purely the vendor master data .
Any help will be appreciated.
Kind Regards,
Sanjay

Backorder report, not possible to print Cardname

Hello,
in the PLD template for the backorder report it is not possible to inlcude the Cardname, there is no system variable available.
Does anyone have a workaround for this?
Thank you in advance.
Best regards,
Anton Wieser.

Hi,
Were you able to figure out solution for this.
I tried this out by processing a backorder goods delivery. The system is still taking the delivery PLD. So, I am getting the Cardname (Customer Name).
Try out using Advanced print layout. Probably that will help in finding out a solution.
Assign points if useful.
Thanks,
Srikanth

The reporting point backflush is not possible for make-to-stock repetitive

Hi All,
we are using the assembly backflush in the MTS REM process. we are need to do the reporting point backflush
if we tick against the RP backflush. what will be the effect in the process while confirmation.
i read the sap library . it say like
The reporting point backflush is not possible for make-to-stock repetitive manufacturing.
is it correct.
Thanks
VRaj

Hi mangal,
i did all the setting as you said. but when click on the reporting point.
system thru error
Error reading reporting point information
Message no. RM111
Diagnosis
The repetitive manufacturing profile is set for the reporting point procedure. However, either no reporting points exist for the material or they are incorrect. Two common reasons for this are:
The repetitive manufacturing profile has been changed in the current session.
You have not defined any milestone operations in the routing.
When creating the product cost collector, no reporting points were created.
Procedure
Two alternative solutions are possible:
Assign a repetitive manufacturing profile with no reporting point procedure to the material in the material master record.
Recreate the reporting points by recosting the product cost collector. To do this, the following prerequisites must be met:
In the material master record, in the production version, you must enter a routing under either detailed planning (first priority) or under rate-based planning (second priority).
Milestone operations must exist in this routing. The system ususally automatically creates the reporting points from these milestones when creating a product cost collector or when creating a production version.
how to create the REPORTING POINT

Document is in transfer for PO, creation not possible

Hi
We are using SRM 4.0 EC scenario. Recently we have been facing the subjected error 'Document is in transfer for PO, creation not possible' while making the confirmation in SRM. It is observed that this is happening mostly in case once we make GR and cancel and repost. Thru some other thread posted in forum, came to know taht we need to delete the entries in table "BBP_DOCUMENT_TAB" via FM ''BBP_DELETE_FROM_DOCUMENT_TAB''. I ran thei FM but found NO poitive results. Hope somebody can help me out. This error became very common in our production system
Thanks
Kiran

Hi Kiran,
Please, use the report CLEAN_REQREQ_UP to clear the entry made for the GR in BBP_DOCUMENT_TAB. The problem comes because there is an entry for the GR in the table probably from the previous creation.
Regards
Saravanan.
Please award if useful

6301 & PC Suite - "Data transfer not possible. Che...

Well, as the title says really.
Upgraded from 6280 -> 6301.
I use Outlook 2003 and sync contacts & calendar.
Sync'd the 6280 before finalising upgrade, plugged in the 6301 with a mini-usb cable (All driver reports it installed new hardware fine) once it had fully come into service and it wouldn't sync.
The phone displays "Data transfer not possible. Check connection" and Nokia PC Sync shows the warning "The mobile phone as not responded". It's solution is "Please ensure your phone is in the standby mode, then restart the Synchronisation. "
Have updated to latest version of PC Suite 6.85.
A bit annoying, as I no longer have any contacts info on the new phone...
Running XP, AMD 3ghz, 4gb ram.

Having spent many hours on this I have now got it working...
This is how :
1. On the phone go to : Settings: Sync and Backup: Server Sync: PC Syncronisation and enter a username and password.
2. Select Synchronise in Nokia PC Suite, in the Connected to 6301 window click the spanner (settings) icon. Now click the Adjustable wrench (Advanced) Icon and go to the sync profile tab and enter the same username and password that you used on the phone. Click OK twice and sync away...
Message Edited by kage64 on 05-May-2008 11:04 PM

ALV function module usages in report

Hi All,
I am writing an ALV report and would like to know whether the following function modules can add some value for my report. The report displays in Grid format using ALV_GRID_DISPLAY.
REUSE_ALV_EVENTS_GET
REUSE_ALV_COMMENTARY_WRITE
REUSE_ALV_VARIANT_F4
REUSE_ALV_VARIANT_EXISTENCE
REUSE_ALV_VARIANT_DEFAULT_GET
I got some example programs for this from the forum but did not quite understand the need of this. So please explain in a simple way how to use this in reports.
Thanks
Ricky

Hi,
SAP provides a set of ALV (ABAP LIST VIEWER) function modules which can be put into use to beautify 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 are 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 for list

Assignment of single Sales group to multiple Sales offices not possible

Hi all,
We need to assign single sales group to multiple sales offices in CRM. When we try to assign a Sales group to more than one Sales office the first assignment between Sales group and Sales office is removed. Only the new assignment is available.
Instead of having two assignments I still only get one.
First I transfered the ECC organization as Standard backend integration. When I realize I needed multiple backend assignment I ran the Conversion to multiple assignments. However, I am not able to realize multiple assignments.
Is it not possible to realize multiple assignment if you first transfered the ECC organization as standard (single) assignment?
Please let me know how to overcome this problem.
Regards
Anders

Hello Anders,
Starting CRM 4.0 multiple hierarchy with this enhanced org data model
works the following way:
- 1 R/3 org data mapped to ONLY 1 CRM org unit.
- multiple hierarchy (1 sales office assigned to several sales org,
1 sales group assigned to several sales office) is managed in the detail
of the org unit with tab Function and with sub tab sales office
and sales group.
For example if you have following R/3 org structure:
Sales org SOr1
_ Sales office Sof1
_ Sales Group Sg1
_ Sales office Sof2
_ Sales Group Sg1
Sales org SOr2
_ Sales office Sof1
In PPOMA_CRM you have to do the following:
For the R3 mapping :
Sor1 mapped to org unit 50000001
Sor2 mapped to org unit 50000002
Sof1 mapped to org unit 50000003
Sof2 mapped to org unit 50000004
Sg1 mapped tp org unit 50000005
And for the multiple assignment
- For sales org 50000001 and 50000002 you just have to maintain in tab
function, sub tab Sales org the Distribution channel division values
- For sales office 50000003 in sub tab Sales office the assignment to
sales org Sor1 and Sor2
- For sales office 50000004 in sub tab Sales office the assignment to
sales org Sor1
- For sales group 50000005 in sub tab sales group the assignment to
sales office Sof1 and Sof2.
If you have different division distribution channel on sales office sale
group compared to the sales org you can maintain manually the values.
Or if is it always the same values you can use * value for distribution
channel division (in that case please read carefully notes
691015 and 735020 if needed)
In addition regarding report CRMC_R3_ORG_GENERATE I would like to
clarify that this report can only be used for initial download, as
written in the customzing documentation of this report (spro-CRM -
master data - org management - data transfer - Copy SAP R/3 sales
structure ) it can only be executed once and so following org
modifications have to be done manually in PPOMA_CRM.
So for this report the correct way to use it is to create all the R/3
org data in 1 shot.
If only 1 R/3 org data is already mapped to a CRM org unit in ppoma_Crm
you will have red light and so it will be impossible to create all
dependent org data.
Hoping i have been able to clarify how it works.
Regards, Gerhard

ALV selection in Cliam Recon report

Hello All,
In Cliam Recon report ( RPCLMSU0 ), we are not able to select the ALV type from the ALV selection field in the report selection screen.
We are in ECC 5.0.
Thanks for any responses.
Chakri.

The same thing happens for us, and we are on ECC 6.0. However, you can run the program without selecting anything for that field. Once you are in the report, go to the top menu and choose "Settings -> Layout -> Choose...". This will give you a pop-up with selections. You can choose All, Global, or User-specific for the Layout Setting and then choose a layout from the table below. I hope this helps.
Actually, it looks like there might be a coding error in the program. The same form is used for the value request on that field as is used to check whether an entered variant exists. That form doesn't fill anything in if the field is initial, it just looks to see if something that was entered already exists. If you look at the source code you will see that the same form is used for "AT SELECTION-SCREEN ON VALUE-REQUEST FOR sv_alvar" as is used for "AT SELECTION-SCREEN". You may want to consider opening a note with SAP about this.
- April King
Message was edited by:
April King

ALV drilldown not possible in report once i apply layout save option

Similar Messages

Maybe you are looking for