INVALID_VARIABLE_VALUES error for drill down/up

Hello ,
I have created a VC model corresponding to a BI query. The query has 3 variables of which one is mandatory the value for which i am hardcoding.In the output table we have a heirarchy variable for
which I wish to use the drill up and drill down features.But after applying these features, and running
the application ,on clicking the drill down/up buttons i get the following error
Nested Exception. Failure to execute native function. Nested Exception. INVALID_VARIABLE_VALUES
The variable format seems to be fine as I have tried it from the BI side and it also generates the output in the VC output table.Following is the webapi used for drill down .
'FILTER_IOBJNM=YGL_ACCNT;FILTER_NODE_IOBJNM=0HIER_NODE;FILTER_VALUE='&#ID[ACC40T]@G_L_Account&';FILTER_COLLAPSE= ;FILTER_IOBJNM=YGL_ACCNT;CMD_1=CMD%3DDRILL_TO_LEVEL%26LEVEL%3D2%26IOBJNM%3DYGL_ACCNT%26DATA_PROVIDER%3DDP;'
Any help would be most appreciated.
BI 7.0,VC 7.0
PS: have already gone through the wiki link for this error
Thank You
Rgds

Vineeth,
Please see my comments below:
1)The complete web api command is in the above thread, the mandatory variable is the fiscal year.
I don't see where you have defined the fiscal year in the web API command below:
'FILTER_IOBJNM=YGL_ACCNT;FILTER_NODE_IOBJNM=0HIER_NODE;FILTER_VALUE='&#IDACC40T@G_L_Account&';
FILTER_COLLAPSE= ;FILTER_IOBJNM=YGL_ACCNT;
CMD_1=CMD%3DDRILL_TO_LEVEL%26LEVEL%3D2%26IOBJNM%3DYGL_ACCNT%26DATA_PROVIDER%3DDP;'
2)am not too sure about your question.
Is the hierarchy for YGL_ACCNT defined as a text hierarchy or characteristic hierarchy?  If it is a characteristic hierarchy, you should specifiy the parameter FILTER_NODE_IOBJNM=YGL_ACCNT instead of FILTER_NODE_IOBJNM=0HIER_NODE.
3)the command is as intended as per the sap documentation
If you are following the SAP documentation, the first occurrence of FILTER_IOBJNM=YGL_ACCNT should be removed as it is already defined after the FILTER_COLLAPSE parameter.
Regards,
Mustafa.

Similar Messages

  • Set headers for drill-down reports.

    Hi!!!
    The problem we have by now is when printing a report, selected characteristis are showed in header as "multiple values" instead of showing the real values that user have choose.
    Does anybody knows how to set headers for drill-down reports in order to see selected characteristics?
    Thanks in advance...
    Adela Cambiasso.

    Sorry, me again...
    I have found yet they way to show in the header the report parameters, I mean, the selection criterias that user used when execute the report... I was able to show selected characteristics inside de report but not the selection criteria...
    Do you know what I have lost? or what to use for this?
    Thanks again.
    Adela.

  • KCA0 - Convert Aspect for drill-down report in ECC6

    Hello experts,
    Do you know the steps to convert an aspect (for drill-down reports) from 3.0 to ECC6? And how to add it to the list in transaction KCR0 (Execute Drill-down report). SAP has mentioned transaction KCA0 for doing a conversion after the upgrade but I am not familiar with this transaction. Please help!
    Thanks and Best regards,
    Chuong

    Hi,
    You can use all the statements in HR also.
    For getting the AB values,there are macros and function modules available.
    Macros:
    rp-imp-c2-b2.
    You need to pass b2 key values before calling macro.For eg,
      MOVE pernr-pernr  TO b2-key-pernr.(since u r using LDB)
      MOVE year         TO b2-key-pabrj. (year you need to pass)
      MOVE period       TO b2-key-pabrp. (month)
      MOVE '1'          TO b2-key-cltyp.
    have a look at these Function Modules also.
    HR_WORK_SCHEDULE_TIMES
    HR_TIME_RESULTS_GET
    HR_TIME_RESULTS_IN_INTERVAL
    HR_WORK_SCHEDULE_TIMES
    Reward points if helpful.
    Regards,
    Manoj.

  • Error while drilling down the data from reports

    Hi friends,
    I have created dimension hierarchies in rpd for drilling down the data.. While i drill down its showing no results at some level when i am clicking on the data.. but when i am clicking on the same levels column header its drilling down properly and i can view the next level for the data item which has shown no results while clicked on it.. Please help me and helps will be appreciated..

    Hi,
    >when i click on 2000 results displaying is no results
    but when i click on the header year its showing the results with 3 for 2000.
    So you are able to drill when you click on header..Go to column properties and make heading interaction to no interaction under column format,put value interaction to default and try to drill clicking on value.
    in RPD i have some derived columns like month .I created month as derived column from date using logical formula and i used this derived columns as the key.. Is it a problem?No I dont think its a problem
    Regards,
    Srikanth

  • Error in summation of Actuals for Drill Down Reports(SAP Standard Reports)

    While executing the Drill Down report (for e.g S_ALR_87013558) for a particular Project (e.g DWRES-C2005) it is observed that the Actual costs booked on the WBS element (DWRES-C2005-502) does not get rolled up to its higher level WBS Element(DWRES-C2005-501).
    This also does not get rolled up to the top WBS element (DWRES-C2005-500).As this is the case the summation for Actuals columns shows incorrect result.Result should have been (Actuals of DWRES-C2005-500 = Actuals of DWRES-C2005-501 + Actuals of DWRES-C2005-502 ).I have also tried the formatting of the Actuals columns in the Form of the report but I could not find any answer.Can anybody help me in this regard.

    Sorry, me again...
    I have found yet they way to show in the header the report parameters, I mean, the selection criterias that user used when execute the report... I was able to show selected characteristics inside de report but not the selection criteria...
    Do you know what I have lost? or what to use for this?
    Thanks again.
    Adela.

  • Javascript Problem for Drill Down Action in SSRS Report when integrated to PPS 2010

    Hi all,
    I have a SSRS report which is integrated to PPS 2010(Performance Point Services) and it is having a drill down action through Go to URL action(I wrote javascript:void(window.open('xxxxx')) to open drill down report in new window).
    This report has 5 parameters and all are multiple valued. Drill down report is opening very well when I open the report form Report Manager for any number of parameters values selected. But when I integrate the same report is PPS and deployed to SharePoint
    then it is working only for 23 parameter values selected in PPS filters. If I select more the 23 values in PPS filters then the drilldown report is not opening.
    But it is working well in Chrome, I verified in IE and Mozilla, both browsers are having problem.
    When I look at Error Console of Mozilla, it is showing a javascript error as "Error: uncaught exception: ReferenceError: window is not defined" but the same report is working well if I select less than 24 filter values.
    Please provide me the solution
    Thanks in advance

    Hi Vasu,
    The issue might occur due to the Microsoft security update MS11-100 which limits the maximum number of form keys, files, and JSON members to 1000 in an HTTP request. Here, I suggest that you modify the Web.config file of the SharePoint site as follows:
    <appSettings>
    <add key="aspnet:MaxHttpCollectionKeys" value="10000" />
    </appSettings>
    If the SharePoint site uses the port 80, the web.config file of the SharePoint site is located in the C:\inetpub\wwwroot\wss\VirtualDirectories\80 folder.
    Reference:
    An ASP.NET request that has lots of form keys, files, or JSON payload members fails with an exception
    If the issue persist, please check whether there are any related errors in the Reporting Services log file which is located in <Drive>:\Program Files\Microsoft SQL Server\MSRSXX.<Instance Name>\Reporting Services\LogFiles.
    Regards,
    Mike Yin
    TechNet Community Support

  • Crystal Help for drill down

    I am trying to figure out what I have wrong... The below formula allows me to drill down (little yellow arrow beside my doc type column) and see journal entries, and incoming payments, but I get errors for Credit Memos and Invoices.
    Both the Doc Type and Doc # are string fields so it should be working......
    So can anyone give me some help as to why it works for two of the four ?
    THANKS
    Select {Command.Doc Type}
    Case "AR Invoice":'http://$b1$/link?table=OINV&key='+ {Command.Doc #}
    Case "AR Credit Memo":'http://$b1$/link?table=ORIN&key='+{Command.Doc #}
    Case "Incoming Payment":'http://$b1$/link?table=ORCT&key='+{Command.Doc #}
    Default: 'http://$b1$/link?table=OJDT&key='+{Command.Doc #}

    Hi Dayton
    The drilldown needs the docentry  rather than docnum so you may need to add this field to your command as an extra field if it is not already there.  It does not need to be printed.
    Once you gave the docentry set up the formula as
    'http://$b1$/link?table=OINV&key=' & totext({Command.DocEntry},0,u201Du201D,u201Du201D)
    so that any decimals, separators etc are removed.
    Hope this helps
    Rob

  • Strange behavior with hidden text field for drill down

    Hi All,
    I am pretty sure I know the cause, just not sure how to work around...
    I am trying to create a drill down report just like in the App Dev guide, and I have done everything the same as the example (2 times, once to follow the guide, and now on my app). The only difference is that I am using a text field rather than a numeric field as the link. This shouldn't be a problem (I wouldn't think) except that the text I NEED to use has '<==' in the middle. So when I check my session state var's, this is what I see:
    CHPAG0SC_MAILCDN_000000047_ CHPAG0SC_MAILCDN_000000047_ <==20060525101642
    When what I should see is:
    CHPAG0SC_MAILCDN_000000047_ <==20060525101642
    So I think that I am gettting duplication because of the characters, but again I don't know how to solve it.
    Any thoughts would be appreciated.
    Corey

    Hi Scott,
    I am trying to create a drill down report similar to the one in the app developers guide. I have a query on pg 1 that includes the required text field as the link. When I click the link, I get an error on pg 2 - which is trying to use the value from pg 1. I did check and saw that even though I set this value in session state (I thought that was what happened when I assigned the 'name' and 'value' in the column link), it is passed in the url, which is where I figured it was breaking. As stated, I need to use this text value as it is the only unique key for the data (currently - this is a data validation step (not an ApEx validation), where users are handling issues with data uploaded from a csv).
    My current process is as follows:
    1. User uploads 2 csv's
    2. Proc moves (from wwv_flow_files) and parses csv back into records and inserts into temp (all varchar2) table(s).
    3. User is displayed 3 'reports' - for each type of validation required - from the stage/temp table
    4. User would click on the 'Edit' link (like the drill down sample) to see more details about the record.
    5. Once the user is done with these reports, they would click another button to 'process' the data (move it into base tables)
    Because the text field is always unique, I figured I wouldn't create a sequence for this like I have for the 'base' (destination) tables.
    I didn't know that I was using a 'get' rather than a 'post', but of course it is a link, not a button - so I should ahve known better.
    Is there a way to do this without adding a sequence generated id for each, or is that just the quickest way?
    Thanks again,
    Corey

  • Error while Drilling down across sheets

    Hi ,
    I am using the new BI 7.0 Bex Analyzer as forntend to my BI 7.0.
    While navigating in BI Bex Analyzer, when I select the the drill down accross sheet from the context menu of any characteristics, i get an error message  as follows.
    "*A Critical program error occurred. The program has to be clos. Please refer the trace for furhter inforamtion*."
    My SAP GUI version is 7.10 and the patch level 5.0
    Can any body suggest some solution on this.
    Thanks in advance.
    Nilesh Labde

    I know it is too late to reply back on this error.
    However, the query which you have already saved, You save it with a different technical name & then execute it, it works.
    It worked for me.
    Thanks,
    Pradip.

  • Error when Drill down on top level of hierarchy node

    Hi Gurus,
    The following error occurs when I drill down to a "Actual Line items sub report" using the "top node" of an hierarchy based report .
    But, the same drill down works fine when I drill down using the very sub level of the same hierarchy (without any further levels of hierarchies).
    System error in program SAPLRRK0 and form NACHLESEN_INIT_NODE-01-
    Any help or work around suggestion would be highly appreciated.
    Thanks
    Ajay

    Hi,
    Thanks for the start.
    But, My Hierarchy is already active.
    Any other place to check for?

  • Error using drill down function on receiving transaction in GL

    "The Receiving Accounting Events function is not available under General Ledger Super User" is received when attempting to drill down on a receiving transaction through GL. I have searched for any missing roles/responsibilities under GL super user and attempted the same process with GL Manager and sysadmin roles without success.

    Please see these docs.
    GL Drilldown for SLA Transactions for Period End Accrual Error: Receiving Accounting Events Function & FRM-40010 CSTFQRAE [ID 1289612.1]
    The Receiving Accounting Events function is not available under the General Ledger Super User responsibility. [ID 1318147.1]
    Cannot Drilldown to GL Account Details For Cost Management Source - 'No Available Transaction for this Line' [ID 1316330.1]
    Thanks,
    Hussein

  • ORA-01722 Error while drill down

    Hi all,
    I have one EUL created with the join of two difference views. In order to join this two view, two id is needed to be joined. I have create a item class whereby it has been joins for this two views. Eg. I got view A with id1 & id2 link to view B with id1 & id2 as well. If I drill down from id1 or id2 column, the screen able to open up the new sheet which will show me the details information that I want.
    However, if try to drill down from item code then, the scren has prompted me the above error. What's wrong with this code ?
    Rgds
    Lim

    Hi,
    Check this note:
    794661
    or try searching OSS with that error.
    Hope this helps.
    Regards,
    Diego

  • OBIEE error on Drill-down : Unable to navigate requested expression

    Hi Gurus,
    While trying out drill-down, am facing the folllowing error message - State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 14026] Unable to navigate requested expression: XXX Time.YYY Month. Please fix the metadata consistency warnings. (HY000)
    I searched for the solution and found that we need to define an aggregated measure of a dimension table. But I dont know how to do it as I have very less hands-on in OBI Admin Tool. Kindly help me by explaining in detail to solve this issue.
    Thanks in advance.

    Hi,
    To define an aggregated measure of a dimension table, complete the following steps:
    *1.Create a new fact logical table with the physical dimension table as source.*
    *2.Include all fields that should be aggregated as a measure of this new fact object.*
    *3.Add an aggregation rule to the column*
    *4.set the logical level of the other dimensions to the grand total level.*
    Below, a sum aggregation rule :
    for more info:
    i.e:
    put the measure indicated by the error message in a fact table object.
    To define an aggregated measure of a dimension table, complete the following steps:
    a) Create a new fact logical table with the physical dimension table as source.
    b) Include all fields that should be aggregated as a measure of this new fact object.
    http://gerardnico.com/wiki/dat/obiee/dimension_measure
    Thanks
    Deva
    Edited by: Devarasu on Sep 29, 2011 7:02 PM

  • Pre-requisites for Drill-Down from Hyperion Planning to Oracle GL

    I am using Hyperion Planning 11.1.2 for maintaining budgets. I do comparison of actual vs budget in Hyperion. I export actual results from Oracle General Ledger (11.5.10) in flat file and upload to Hyperion planning using FDM. I maintain mapping in FDM for flat file and the Hyperion members.
    Q1) Is it possible to drill down actual numbers from Hyperion planning to Oracle General Ledger via FDM?
    Q2) If yes, what are prerequisites for using drill-down functionality?
    Can anyone please answer and refer some link/material that may help me in setting this up?
    Thanks in advance.

    Thanks
    But when i try to log in i m getting error bellow"
    Failure of server APACHE bridge: No backend server available for connection: timed out after 10 seconds or idempotent set to OFF."
    So do u have any other reference plz
    thanks

  • Error in Drilled down ALV Report.

    Hi all
    i am creating a single level drilled down report , in that in the first screen i am displaying the header detials , in the second level i am displaying the item detial of the particular line..
    While processing the second level i am getting a dump like
    A PERFORM was used to call the routine "USER_COMMAND" of the program
    "SAPLSLVC_FULLSCREEN".
    This routine contains exactly 1 formal parameters, but the current
    call contains 2 actual parameters.
    parameters.
    here is my code :
    FORM USER_COMMAND USING R_UCOMM LIKE SY-UCOMM.
    CASE R_UCOMM.
    WHEN '&IC1'.
    PERFORM BUILD_CATALOG_EKPO.
    PERFORM EVENT_EKPO.
    PERFORM POPULATE_EVENT_EKPO.
    PERFORM DATA_EKPO.
    PERFORM BUILD_LIST.
    PERFORM DISPLAY_EKPO.
    ENDCASE.
    ENDFORM.
    *&      Form  BUILD_CATALOG_EKPO
          text
    -->  p1        text
    <--  p2        text
    FORM BUILD_CATALOG_EKPO .
      WA_FIELDCAT-TABNAME = 'ITAB_EKPO'.
      WA_FIELDCAT-FIELDNAME = 'EBELN'.
      WA_FIELDCAT-SELTEXT_M = 'PO NO.'.
      APPEND WA_FIELDCAT TO I_FIELDCAT.
      CLEAR WA_FIELDCAT.
      WA_FIELDCAT-TABNAME = 'ITAB_EKPO'.
      WA_FIELDCAT-FIELDNAME = 'EBELP'.
      WA_FIELDCAT-SELTEXT_M = 'Item No.'.
      APPEND WA_FIELDCAT TO I_FIELDCAT.
      CLEAR WA_FIELDCAT.
        WA_FIELDCAT-TABNAME = 'ITAB_EKPO'.
      WA_FIELDCAT-FIELDNAME = 'MATNR'.
      WA_FIELDCAT-SELTEXT_M = 'Material NO.'.
      APPEND WA_FIELDCAT TO I_FIELDCAT.
      CLEAR WA_FIELDCAT.
        WA_FIELDCAT-TABNAME = 'ITAB_EKPO'.
      WA_FIELDCAT-FIELDNAME = 'WERKS'.
      WA_FIELDCAT-SELTEXT_M = 'PLANT.'.
      APPEND WA_FIELDCAT TO I_FIELDCAT.
      CLEAR WA_FIELDCAT.
        WA_FIELDCAT-TABNAME = 'ITAB_EKPO'.
      WA_FIELDCAT-FIELDNAME = 'LGORT'.
      WA_FIELDCAT-SELTEXT_M = 'Storage Loc.'.
      APPEND WA_FIELDCAT TO I_FIELDCAT.
      CLEAR WA_FIELDCAT.
        WA_FIELDCAT-TABNAME = 'ITAB_EKPO'.
      WA_FIELDCAT-FIELDNAME = 'MENGE'.
      WA_FIELDCAT-SELTEXT_M = 'Quantity.'.
      APPEND WA_FIELDCAT TO I_FIELDCAT.
      CLEAR WA_FIELDCAT.
        WA_FIELDCAT-TABNAME = 'ITAB_EKPO'.
      WA_FIELDCAT-FIELDNAME = 'MEINS'.
      WA_FIELDCAT-SELTEXT_M = 'UNIT.'.
      APPEND WA_FIELDCAT TO I_FIELDCAT.
      CLEAR WA_FIELDCAT.
    ENDFORM.                    " BUILD_CATALOG_EKPO
    *&      Form  EVENT_EKPO
          text
    -->  p1        text
    <--  p2        text
    FORM EVENT_EKPO .
    CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
    EXPORTING
      I_LIST_TYPE           = 0
    IMPORTING
       ET_EVENTS             = V_EVENTS
    EXCEPTIONS
      LIST_TYPE_WRONG       = 1
      OTHERS                = 2
    IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    ENDFORM.                    " EVENT_EKPO
    *&      Form  POPULATE_EVENT_EKPO
          text
    -->  p1        text
    <--  p2        text
    FORM POPULATE_EVENT_EKPO .
    READ TABLE V_EVENTS INTO WA_EVENT WITH KEY NAME = 'TOP_OF_PAGE'.
    IF SY-SUBRC EQ 0.
    WA_EVENT-FORM = 'TOP_OF_PAGE'.
    MODIFY V_EVENTS FROM WA_EVENT TRANSPORTING FORM WHERE NAME = WA_EVENT-FORM.
    ENDIF.
    ENDFORM.                    " POPULATE_EVENT_EKPO
    FORM F_TOP_OF_PAGE.
      CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
        EXPORTING
          IT_LIST_COMMENTARY       = IT_LISTHEADER
       i_logo                   =
       I_END_OF_LIST_GRID       =
    ENDFORM.
    *&      Form  DATA_EKPO
          text
    -->  p1        text
    <--  p2        text
    FORM DATA_EKPO .
    DATA:RS_SELFIELD TYPE SLIS_SELFIELD.
    READ TABLE ITAB_EKKO INTO WA_EKKO INDEX RS_SELFIELD-TABINDEX.
    SELECT EBELN EBELP MATNR WERKS LGORT MENGE MEINS
    FROM EKPO
    INTO CORRESPONDING FIELDS OF TABLE ITAB_EKPO
    WHERE EBELN = WA_EKKO-EBELN.
    DATA :ID_ITEM_COLOR.
    LOOP AT ITAB_EKPO INTO WA_EKPO.
    ID_ITEM_COLOR = ID_ITEM_COLOR + 1.
    IF ID_ITEM_COLOR = 8.
       ID_ITEM_COLOR = 1.
    ENDIF.
    CONCATENATE 'C' ID_ITEM_COLOR '10' INTO WA_EKPO-LINE_COLOR_ITEM.
    MODIFY ITAB_EKPO FROM WA_EKPO TRANSPORTING LINE_COLOR_ITEM.
    ENDLOOP.
    ENDFORM.                    " DATA_EKPO
    *&      Form  DISPLAY_EKPO
          text
    -->  p1        text
    <--  p2        text
    FORM DISPLAY_EKPO .
    CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
    EXPORTING
      I_INTERFACE_CHECK                 = ' '
      I_BYPASSING_BUFFER                = ' '
      I_BUFFER_ACTIVE                   = ' '
       I_CALLBACK_PROGRAM                 = V_REPID
      I_CALLBACK_PF_STATUS_SET          = ' '
      I_CALLBACK_USER_COMMAND           = 'USER_COMMAND '
      I_CALLBACK_TOP_OF_PAGE            = 'TOP_OF_PAGE'
      I_CALLBACK_HTML_TOP_OF_PAGE       = ' '
      I_CALLBACK_HTML_END_OF_LIST       = ' '
      I_STRUCTURE_NAME                  =
      I_BACKGROUND_ID                   = ' '
       I_GRID_TITLE                      = I_TITLE_EKPO
      I_GRID_SETTINGS                   =
      IS_LAYOUT                         =
       IT_FIELDCAT                       = I_FIELDCAT[]
      IT_EXCLUDING                      =
      IT_SPECIAL_GROUPS                 =
      IT_SORT                           =
      IT_FILTER                         =
      IS_SEL_HIDE                       =
      I_DEFAULT                         = 'X'
      I_SAVE                            = ' '
      IS_VARIANT                        =
       IT_EVENTS                         = V_EVENTS
      IT_EVENT_EXIT                     =
      IS_PRINT                          =
      IS_REPREP_ID                      =
      I_SCREEN_START_COLUMN             = 0
      I_SCREEN_START_LINE               = 0
      I_SCREEN_END_COLUMN               = 0
      I_SCREEN_END_LINE                 = 0
      IT_ALV_GRAPHICS                   =
      IT_HYPERLINK                      =
      IT_ADD_FIELDCAT                   =
      IT_EXCEPT_QINFO                   =
      I_HTML_HEIGHT_TOP                 =
      I_HTML_HEIGHT_END                 =
    IMPORTING
      E_EXIT_CAUSED_BY_CALLER           =
      ES_EXIT_CAUSED_BY_USER            =
      TABLES
        T_OUTTAB                          = ITAB_EKPO
    EXCEPTIONS
      PROGRAM_ERROR                     = 1
      OTHERS                            = 2
    IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    ENDFORM.                    " DISPLAY_EKPO
    *&      Form  BUILD_LIST
          text
    -->  p1        text
    <--  p2        text
    FORM BUILD_LIST .
      gd_layout-no_input          = 'X'.
      gd_layout-colwidth_optimize = 'X'.
      gd_layout-totals_text       = 'Totals'(201).
    Set layout field for row attributes(i.e. color)
      gd_layout-info_fieldname =      ' LINE_COLOR_ITEM'.
    ENDFORM.                    " BUILD_LIST
    Arun Joseph

    The form USER_COMMAND should have 2 changing/actual parameters which is standard.
    Ex:
    FORM user_command USING r_ucomm LIKE sy-ucomm 
    rs_selfield TYPE slis_selfield.
    ENDFORM.

Maybe you are looking for