The Report Abuse Function

Has anyone else had trouble with the Report Abuse function?
Recently I attempted to write an abuse report, but received an error message upon submission.
How does one report abuse in this forum?
Roddy

Questions usually remain unanswered if no one knows the answer. It would appear that you are the only person who has felt it necessary to use the Report Abuse button in this forum. If that's the case, no one can verify whether there's a problem.
Thank you for responding, but I disagree with your suggested solution to the problem:
This question can be easily answered by anyone, who might be inclined to seek a moderator's support either now or in the future.  They have merely to
1) Click on the appropriate button.
2) Enter a brief test message.
3) Verify whether it is sent.
4) Report their finding to this discussion.
I have now tried to send three messages using the Report Abuse function.  Two of them failed outright, and the only test message sent went through unacknowledged.
Before I register a formal complaint with Adobe I would like to gather evidence to support my case.
Roddy

Similar Messages

  • Is there any why to check that the reports are functioning well in Webanaly

    Hi Experts,
    is there any why to check that the reports are functioning well in Webanalysis?
    any Help in this issue ASAP is highly appreciated
    Kind Regards,
    Vam-c

    What do you mean by checking whether they are working?
    You can always open the report and see whether everything is working ;)
    Regards
    Celvin
    http://www.orahyplabs.com

  • The report abuse icon

    Hey Mods
    can the "report abuse" icon be used to report very elementary questions that have been asked several times in the past and are only a simple search away?
    no matter how many times we say,people just post these baby questions and expect us to spend our time searching and replying
    Thanx
    Aamir

    One of my favorite Despair.com t-shirts....
    "There are no stupid questions, but there are a LOT of inquisitive idiots."
    hehe

  • How can I change the position of the page footer when using the report generation functions of LabView 6.1.

    At present my page footer is printing too far up from the bottom of the page. I have been unable to find a property that enables the position to be changed.

    Use the Set Report Margin.vi to set the bottom margin to something less than the default 1. I got a standard report to print a footer .2 inches from the bottom of the paper.

  • The only working print-related function in BioBench1.2 on my PC is the "Print Report", all the other "Print" functions gave me "Error, the printer is not set up correctly".

    I used to print all my BioBench data by first exporting them to Excel and then print from there. Recently I need to print some of the screen shots and some data directly from array analysis, but when I click on the "print" buttons, the "Error, the printer is not set up correctly" message occurs. The only thing I can print from BB without this error is the report printing function. I have a postcript printer and I have set the postscript option to be "true"... Thanks !

    This problem is a result of a limitation in Windows 9x regarding the size of an image that you can send to the printer. The problem does not occur on Windows 2000/NT. This problem appeared with the increased color options of LabVIEW 6.0 on which the BB1.2 is based.Although it is not immediately obvious, your video driver and settings play a role in printing.
    1. Try adjusting the color palette your driver uses (i.e., 256 color, high olor, true color). The error may occur only in one of these modes. Also, change the resolution (number of pixels) to represent the Screen Area; e.g., change from a 1024 x 768 display to an 800 x 600 pixel display.
    2.Certain video drivers also support "acceleration" modes. Using a non-accelerated mode often eliminates the error. For
    Windows 95/98, right-click on your My Computer icon and select "Properties" from the pop-up
    menu. On the Performance tab, click the Graphics button and change the Hardware Acceleration (e.g., if it is set to "Full", lower the setting a notch or two); for Windows 2000/NT, right-click on your Desktop and select "Properties" from the pop-up menu. On the Settings tab, click the Advanced button and go to
    Troubleshooting.
    3.In Windows, the standard VGA driver provided by the operating system is very stable. Try using this driver in place of the specific one written for your video hardware. If the error is eliminated, there is likely a problem with your vendor-provided video driver.
    4.These errors are most often fixed with the latest
    video/printer driver. Be sure to contact your hardware manufacturer and install the latest driver. An easy way to determine if your error is "driver-related" is to move your code to another machine (and hopefully a different set of drivers) and see if th
    e error persists. If the problem is printer related, try another printer.
    5.Make sure there are at least 100M avalible space in your C: drive. If not, set the virtual memory to the other drive which has larger available space.

  • Application Builder for labVIEW 7 Doesn't support any report generation function

    I'm Using LabVIEW 7.0 to build an application My Application is exporting data to an excel report. the vis were working great until i tried to creat an .EXE file. The application is working fine but when i try to generate the report nothing happens.
    So, I decided to test the report generation functions alone (New Report.vi, Append report text.vi and Dispose Report.vi). The Problem Still there, the .EXE file takes no action when i attend to generate a report. any suggetions please.

    Shady Yehia wrote:
    > I'm Using LabVIEW 7.0 to build an application My Application is
    > exporting data to an excel report. the vis were working great until i
    > tried to creat an .EXE file. The application is working fine but when
    > i try to generate the report nothing happens.
    >
    > So, I decided to test the report generation functions alone (New
    > Report.vi, Append report text.vi and Dispose Report.vi). The Problem
    > Still there, the .EXE file takes no action when i attend to generate a
    > report. any suggetions please.
    Another possible reason besides of possible path problems: Are you
    running that application on the same computer? If not you need not only
    to install the Runtime-Engine (automatic when you create an installer)
    but also the Report Active X support.
    To include that into the installer
    you go into the Installer Settings Tab, then press the Advanced button
    and make sure that you check the NI Reports Support checkbox before
    creating an application build.
    Rolf Kalbermatter
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

  • How to check the report builder version from the rdf file

    Hi,
    I have a rdf file but I don't the developer using which version of report builder to develop the rdf file. So, does anyone knows how to check the rdf file is developed by which version of report builder?
    When I try to use the notepad to open the rdf file, it shows the string "ROS.60050". So, does it means that the rdf file is developed by Oracle report 6i?
    Besides, do anyone knows if Oracle report 6i are still offer from Oralce (as I know, the latest verison of oracle report is 11g). So, in case Oralce not offer oracle 6i and I need to buy oracle report 11g, do u know it is compatiable or I need to do the migration from 6i to 11g?
    Thanks!

    Hi,
    The ROS version you are seeing in the RDF file does not mean the version where that RDF was developed. I am not aware of a way to check this but something that may help is that when you try to open a RDF developed in a higher version
    of Reports with a lower version of Reports builder the following warning will be displayed
    Warning. Opening a report saved with a newer version of Reports Builder.
    Functionality may be lost. Continue?
    "You tried to open a report with a version of Reports Builder older than the version used to
    create the report. If the report uses functionality unavailable in the older version, that
    functionality will be eliminated from the report.
    Regarding Oracle Developer 6i. This version is not supported any more. Regarding how to upgrade Reports 6i to 11g and what to have in mind during the upgrade please review the following documentation.
    References
    http://docs.oracle.com/cd/E24269_01/doc.11120/e24478/toc.htm
    How To Migrate Forms and Reports From 6i and/or 9i To 11g? (Doc ID 1275515.1)
    Hope it helps.
    Regards, RZ

  • How to edit ALV report using function modules

    I have a ALV report , i want to edit the report
    using function modules.
    how can i do that...
    Edited by: ms kumar on Mar 6, 2008 3:24 PM

    hi i had used this report with the check box,
    using the fm of alvs.....
    *& Report  ZZZ00
    REPORT  ZPR_02.
    TYPE-POOLS: SLIS.
    TABLES:pa0002,pa0008.
    data:begin of it_pa0002 occurs 0,
         checkbox,
         pernr like pa0002-pernr,
         begda like pa0002-begda,
         endda like pa0002-endda,
         vorna like pa0002-vorna,
         nachn like pa0002-nachn,
         end of it_pa0002.
    data:begin of it_pa00021 occurs 0,
         pernr like pa0002-pernr,
         begda like pa0002-begda,
         endda like pa0002-endda,
         vorna like pa0002-vorna,
         nachn like pa0002-nachn,
         expand TYPE xfeld value 'X',
         end of it_pa00021.
    data:begin of it_pa0008 occurs 0,
         pernr like pa0008-pernr,
         begda like pa0008-begda,
         endda like pa0008-endda,
         ANSAL like pa0008-ANSAL,
         LGA01 like pa0008-LGA01,
         BET01 LIKE PA0008-BET01,
         end of it_pa0008.
    DATA: IT_FIELD_CAT TYPE SLIS_T_FIELDCAT_ALV,
          IT_FIELD_CAT1 TYPE SLIS_T_FIELDCAT_ALV,
          IT_LAYOUT1 TYPE SLIS_LAYOUT_ALV,
          WA_FIELD_CAT TYPE SLIS_FIELDCAT_ALV,
          WA_FIELD_CAT1 TYPE SLIS_FIELDCAT_ALV,
          IT_LAYOUT TYPE SLIS_LAYOUT_ALV,
          IT_EVENTS TYPE SLIS_T_EVENT,
          WA_EVENTS TYPE SLIS_ALV_EVENT,
          IT_HEADER TYPE SLIS_T_LISTHEADER,
          WA_HEADER TYPE SLIS_LISTHEADER,
          wa_keyinfo TYPE slis_keyinfo_alv.
    CONSTANTS:c VALUE 'X'.
    SELECT-OPTIONS: S_pernr FOR pa0002-pernr.
    START-OF-SELECTION.
      SET PF-STATUS 'DATA' .
      PERFORM GET_DATA.
      PERFORM BUILD_FIELD_CAT.
      PERFORM GET_EVENTS.
      PERFORM DISPLAY_DATA.
    *&      Form  get_data
          text
    FORM GET_DATA .
      SELECT pernr
             begda
             endda
             vorna
             nachn
             FROM pa0002
             INTO CORRESPONDING FIELDS OF TABLE IT_pa0002
             WHERE pernr IN S_pernr.
    ENDFORM.                    " get_data
    *&      Form  build_field_cat
          text
    FORM BUILD_FIELD_CAT .
        wa_field_cat-tabname = 'PA0002'.
      WA_FIELD_CAT-FIELDNAME = 'CHECKBOX'.
      wa_field_cat-ref_tabname = 'IT_PA0002'.
      WA_FIELD_CAT-REPTEXT_DDIC = 'Check Box'.
      APPEND WA_FIELD_CAT TO IT_FIELD_CAT.
      CLEAR WA_FIELD_CAT.
        wa_field_cat-tabname = 'PA0002'.
      WA_FIELD_CAT-FIELDNAME = 'PERNR'.
        wa_field_cat-ref_tabname = 'IT_PA0002'.
      WA_FIELD_CAT-REPTEXT_DDIC = 'Personnel no'.
      APPEND WA_FIELD_CAT TO IT_FIELD_CAT.
      CLEAR WA_FIELD_CAT.
        wa_field_cat-tabname = 'PA0002'.
      WA_FIELD_CAT-FIELDNAME = 'BEGDA'.
      wa_field_cat-ref_tabname = 'IT_PA0002'.
      WA_FIELD_CAT-REPTEXT_DDIC = 'Start date'.
      APPEND WA_FIELD_CAT TO IT_FIELD_CAT.
      CLEAR WA_FIELD_CAT.
        wa_field_cat-tabname = 'PA0002'.
      WA_FIELD_CAT-FIELDNAME = 'ENDDA'.
      wa_field_cat-ref_tabname = 'IT_PA0002'.
      WA_FIELD_CAT-REPTEXT_DDIC = 'End date'.
      APPEND WA_FIELD_CAT TO IT_FIELD_CAT.
      CLEAR WA_FIELD_CAT.
        wa_field_cat-tabname = 'PA0002'.
      WA_FIELD_CAT-FIELDNAME = 'VORNA'.
      wa_field_cat-ref_tabname = 'IT_PA0002'.
      WA_FIELD_CAT-REPTEXT_DDIC = 'First name'.
      APPEND WA_FIELD_CAT TO IT_FIELD_CAT.
      CLEAR WA_FIELD_CAT.
        wa_field_cat-tabname = 'PA0002'.
      WA_FIELD_CAT-FIELDNAME = 'NACHN'.
        wa_field_cat-ref_tabname = 'IT_PA0002'.
      WA_FIELD_CAT-REPTEXT_DDIC = 'Last name'.
      APPEND WA_FIELD_CAT TO IT_FIELD_CAT.
      CLEAR WA_FIELD_CAT.
        wa_field_cat1-tabname = 'PA0002'.
      WA_FIELD_CAT1-FIELDNAME = 'PERNR'.
        wa_field_cat1-ref_tabname = 'IT_PA00021'.
      WA_FIELD_CAT1-REPTEXT_DDIC = 'Personnel no'.
      APPEND WA_FIELD_CAT1 TO IT_FIELD_CAT1.
      CLEAR WA_FIELD_CAT1.
        wa_field_cat1-tabname = 'PA0002'.
      WA_FIELD_CAT1-FIELDNAME = 'BEGDA'.
        wa_field_cat1-ref_tabname = 'IT_PA00021'.
      WA_FIELD_CAT1-REPTEXT_DDIC = 'Start date'.
      APPEND WA_FIELD_CAT1 TO IT_FIELD_CAT1.
      CLEAR WA_FIELD_CAT1.
        wa_field_cat1-tabname = 'PA0002'.
      WA_FIELD_CAT1-FIELDNAME = 'ENDDA'.
        wa_field_cat1-ref_tabname = 'IT_PA00021'.
      WA_FIELD_CAT1-REPTEXT_DDIC = 'End date'.
      APPEND WA_FIELD_CAT1 TO IT_FIELD_CAT1.
      CLEAR WA_FIELD_CAT1.
        wa_field_cat1-tabname = 'PA0002'.
      WA_FIELD_CAT1-FIELDNAME = 'VORNA'.
        wa_field_cat1-ref_tabname = 'IT_PA00021'.
      WA_FIELD_CAT1-REPTEXT_DDIC = 'First name'.
      APPEND WA_FIELD_CAT1 TO IT_FIELD_CAT1.
      CLEAR WA_FIELD_CAT.
        wa_field_cat1-tabname = 'PA0002'.
      WA_FIELD_CAT1-FIELDNAME = 'NACHN'.
        wa_field_cat1-ref_tabname = 'IT_PA00021'.
      WA_FIELD_CAT1-REPTEXT_DDIC = 'Last name'.
      APPEND WA_FIELD_CAT1 TO IT_FIELD_CAT1.
      CLEAR WA_FIELD_CAT1.
        wa_field_cat1-tabname = 'PA0008'.
        wa_field_cat1-fieldname = 'PERNR'.
          wa_field_cat-ref_tabname = 'IT_PA0008'.
        wa_field_cat1-REPTEXT_DDIC = 'personnelno'.
        APPEND wa_field_cat1 TO it_field_cat1.
       CLEAR WA_FIELD_CAT1.
        wa_field_cat1-tabname = 'PA0008'.
        wa_field_cat1-fieldname = 'BEGDA'.
          wa_field_cat-ref_tabname = 'IT_PA0008'.
        wa_field_cat1-REPTEXT_DDIC = 'begindate'.
        APPEND wa_field_cat1 TO it_field_cat1.
        CLEAR WA_FIELD_CAT1.
        wa_field_cat1-tabname = 'PA0008'.
        wa_field_cat1-fieldname = 'ENDDA'.
          wa_field_cat-ref_tabname = 'IT_PA0008'.
        wa_field_cat1-REPTEXT_DDIC = 'enddate'.
        APPEND wa_field_cat1 TO it_field_cat1.
        CLEAR WA_FIELD_CAT1.
        wa_field_cat1-tabname = 'PA0008'.
        wa_field_cat1-fieldname = 'ANSAL'.
          wa_field_cat-ref_tabname = 'IT_PA0008'.
        wa_field_cat1-REPTEXT_DDIC = 'annualsalary'.
        APPEND wa_field_cat1 TO it_field_cat1.
        CLEAR WA_FIELD_CAT1.
        wa_field_cat1-tabname = 'PA0008'.
        wa_field_cat1-fieldname = 'LGA01'.
          wa_field_cat-ref_tabname = 'IT_PA0008'.
        wa_field_cat1-REPTEXT_DDIC = 'wagetype'.
        APPEND wa_field_cat1 TO it_field_cat1.
        CLEAR WA_FIELD_CAT1.
        wa_field_cat1-tabname = 'PA0008'.
        wa_field_cat1-fieldname = 'BET01'.
          wa_field_cat-ref_tabname = 'IT_PA0008'.
        wa_field_cat1-REPTEXT_DDIC = 'Amount'.
        APPEND wa_field_cat1 TO it_field_cat1.
        CLEAR WA_FIELD_CAT1.
    ENDFORM.                    " build_field_cat
    *&      Form  display_data
          text
    FORM DISPLAY_DATA .
    it_layout-box_fieldname = 'CHECKBOX'.
    it_layout-EDIT = 'X'.
      CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'
        EXPORTING
          I_CALLBACK_PROGRAM             = SY-REPID
          I_CALLBACK_PF_STATUS_SET       = 'PF_STATUS'
          I_CALLBACK_USER_COMMAND        = 'USER_COMMAND'
          IT_FIELDCAT                    = IT_FIELD_CAT
          IS_LAYOUT                      = IT_LAYOUT
          IT_EVENTS                      = IT_EVENTS
        TABLES
          T_OUTTAB           = IT_pa0002.
    ENDFORM.                    " display_data
    *&      Form  get_events
          text
    FORM GET_EVENTS .
      CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
       IMPORTING
         ET_EVENTS             = IT_EVENTS .
      READ TABLE IT_EVENTS INTO WA_EVENTS
                           WITH KEY NAME = SLIS_EV_TOP_OF_PAGE.
      IF SY-SUBRC = 0.
        WA_EVENTS-FORM = 'TOP_OF_PAGE'.
        MODIFY IT_EVENTS FROM WA_EVENTS INDEX SY-TABIX.
      ENDIF.
    ENDFORM.                    " get_events
    *&      Form  top_of_page
          text
    FORM TOP_OF_PAGE.
      WA_HEADER-TYP = 'H'.
      WA_HEADER-INFO = 'EMPLOYEE DATA'.
      APPEND WA_HEADER TO IT_HEADER.
      CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
        EXPORTING
          IT_LIST_COMMENTARY       = IT_HEADER
    ENDFORM. "top_of_page
    *&      Form  GUI_SET
    FORM GUI_SET USING RT_EXTAB TYPE SLIS_T_EXTAB .
      SET PF-STATUS 'DATA' .
    ENDFORM.                    "GUI_SET
    *&      Form  USER_COMMAND
    FORM USER_COMMAND USING R_UCOMM LIKE SY-UCOMM
                            R_SELFIELD TYPE SLIS_SELFIELD.
    DATA:V_PERNR LIKE PA0002-PERNR.
      CASE R_UCOMM.
        WHEN 'DET'.
    DATA: V_FLAG.
      clear : v_flag.
    LOOP AT IT_PA0002.
         if it_PA0002-checkbox =  'X'.
                   v_flag = 'X'.
              v_pernr = IT_PA0002-PERNR.
    SELECT  PERNR
            BEGDA
            ENDDA
            VORNA
            NACHN
            FROM PA0002
            INTO CORRESPONDING FIELDS OF TABLE IT_PA00021
            WHERE PERNR = V_PERNR.
    SORT IT_PA00021 BY PERNR.
    DELETE ADJACENT DUPLICATES FROM IT_PA00021 COMPARING PERNR.
    READ TABLE IT_PA00021 INDEX 1.
    SELECT PERNR
           BEGDA
           ENDDA
           ANSAL
           LGA01
           BET01
           FROM PA0008
           INTO TABLE IT_PA0008
           FOR ALL ENTRIES IN IT_PA00021
           WHERE PERNR = IT_PA00021-PERNR.
              if not it_PA0008[] Is initial.
              SORT IT_PA0008 BY PERNR.
             delete adjacent duplicates from  it_PA0008 comparing pernr.
              READ TABLE IT_PA0008 INDEX 1.
              endif.
            endif.
         enddo.
      it_layout1-group_change_edit = c.
      it_layout1-colwidth_optimize = c.
      it_layout1-zebra             = c.
      it_layout1-detail_popup      = c.
      it_layout1-get_selinfos      = c.
      it_layout-expand_fieldname  = 'EXPAND'.
      wa_keyinfo-header01 = 'PERNR'.
      wa_keyinfo-item01 = 'PERNR'.
    IF NOT V_FLAG IS INITIAL.
    CALL FUNCTION 'REUSE_ALV_HIERSEQ_LIST_DISPLAY'
      EXPORTING
       I_CALLBACK_PROGRAM             = SY-REPID
        IS_LAYOUT                      = IT_LAYOUT1
       IT_FIELDCAT                    =  IT_FIELD_CAT1
        I_TABNAME_HEADER               = 'PA0002'
        I_TABNAME_ITEM                 = 'PA0008'
        IS_KEYINFO                     = wa_keyinfo
        TABLES
        T_OUTTAB_HEADER                = IT_PA00021
        T_OUTTAB_ITEM                  = IT_PA0008.
    ENDIF.
    CLEAR: IT_PA00021,IT_PA0002,IT_PA0008.
    ENDLOOP.
    WHEN 'BACK'.
    EXIT.
    ENDCASE.
    ENDFORM.                    "USER_COMMAND
    reward points if useful,
    venkat.

  • EPMCOPYRANGE displays formulas outside the report on expanding

    Hi Experts,
    I am facing issue with EPMCOPYRANGE function as follows:
    I have an EPMCOPYRANGE function with certain formulas and save comment in Column M, N, O
    When i execute the report this function works fine (Example: it expands for 100 rows with correct calculations)
    When i refresh it again for a lesser data (Example: with data upto 50 rows) the rest of the 50 cells still contains the formula from previous EPM COPYRANGE and i get error as #REF
    Same is the case when i run the report for a period with no data, i can still see the formulas in the cells in column M, N, O
    is there any settings to be maintained for EPMCOPYRANGE function which i am missing?
    Regards,
    Shweta Salpe

    Hi Vadim,
    Here, when i select period 1 and refresh the report the report has 400 rows populated. With Variance ($) and Variance (%) as caluclated members through EPMCOPYRANGE function.
    When i refresh the report for period 2 the report has rows till 327 and the rest of the rows 328 to 400 still contains the formula for variance but since there are no refrence values it shows as #REF.
    When i refresh the report again for period 3 it will have 450 rows and when i go back to period 2 now, the rows 327 to 450 will contain unwanted formula in the variance column.
    Thanks,
    Shweta Salpe

  • ABAP Query- Report Assignment functionality

    Dear Collages,
    I am using SQ01 for reporting materials data information.
    Also I am using the Report Assignment functionality to call transaction MM02
    In the drill down mode expecting to change materials according to the ALV list after selecting double click on one material out from list.
    The problem is that the material I am getting after moving to transaction MM02 is the last in Memory Id not the one I want to get fro ALV list.
    Is this functionality I am expecting is available in ABAP Query??
    If so how!
    Many Thanks in advance
    Oren

    You need to clear the parameter id MAT , Try to use some events or using free coding clear the MAT
    SET PARAMETER ID: 'MAT' FIELD space.
    a®

  • Is it just me, or has 'Report Abuse' disappeared??

    Hi guys
    Whatever happened to the 'Report Abuse' button at the bottom of each thread page?
    I know it was there yesterday...
    Maybe Sun is just sick with all the abuse reports, and doesn't want to hear them anymore??
    cheers guys :)
    lutha

    Hey, it's back again!
    In both Firefox and IE, the button had simply
    vanished!!
    I really am not making this up. I thought they had
    messed up the forum code or something like that...
    weird...
    luthaI'm using Mozilla, so you could be right :)I just switched to Firefox yesterday. One of the best things I've done this year, for sure...
    I'm still riding the wave, man! It is so cool! Just loving it... :)
    lutha

  • Reporting agent functions

    can any body xplain how to schedule tasks thru "reporting agent". pls xplain in detailed steps.

    Hi,
    The functions of the reporting agent are triggered by Information Broadcasting.
    The Reporting Agent was not developed any further. It was removed from the current version of the Data Warehousing Workbench. You can now only reach the Reporting Agent using transaction code REPORTING_AGENT.
    Effects on the Dataset
    A migration of Reporting Agent settings and Reporting Agent packages by broadcast settings is not planned.
    No more new developments are being made for the Reporting Agent. The Reporting Agent functions are now covered by Information Broadcasting, SAP NetWeaver Portal and the Alert Framework. The Reporting Agent has been removed from the Data Warehousing Workbench. You can still maintain the Reporting Agent settings using the REPORTING_AGENT transaction. These settings can be maintained for queries and Web templates from SAP BW 3.x only.
    General Practices with Migration
    The system does not support the migration of Reporting Agent settings for information broadcasting.
    The Reporting Agent is a tool used to schedule reporting functions in the background.
    The following functions are available:
    ·        Evaluating exceptions
    ·        Printing queries
    ·        Pre-calculating Web templates
    ·        Pre-calculating characteristic variables of type pre-calculated value sets
    ·        Pre-calculation of queries for Crystal reports
    ·        Managing bookmarks
    Note that you can only use the Reporting Agent if you are working with queries and Web templates in the SAP BW 3.x format.
    As of SAP NetWeaver 2004s, the Reporting Agent functions are covered by Information Broadcasting. We recommend that you use Information Broadcasting instead of the Reporting Agent.
    For more information, see Information Broadcasting.
    Use
           1.      You make settings for the specified reporting functions.
           2.      You assign the individual settings to scheduling packages for background processing.
           3.      You schedule scheduling packages as a job or within a process chain.
    The last two points do not apply to managing bookmarks.
    Structure
    The Reporting Agent interfaces are made up of two tree structures in the functional areas Exceptions, Print, Web Templates, and Value Sets.
    ·         The left-hand tree gives you an overview of the available objects as well as the settings that have already been made. To give you a better overview, you can filter according to queries with settings in the Exceptions and Print functions.
    ·         The right-hand tree gives you an overview of the scheduling package and manages the background processing.
    In the Bookmarks functional area, the Reporting Agent scheduler interfaces are made up of a single tree structure.
    Integration
    The following graphic gives an overview of the different functional areas for the Report Agent and its integration:
    See also:
    Defining Exceptions Settings and Exception Reporting
    Defining the Print Setting
    Defining the Web Template Setting
    Defining the Value Set Setting
    Defining Crystal Reports Query Settings
    Managing Bookmarks
    You have defined and actively saved one or more Reporting Agent settings.
    You have created one or more scheduling packages.
    Procedure
    Select the setting that you want to schedule in the left Reporting Agent Settings tree in the Reporting Agent Scheduler.
    Use drag and drop to assign the setting to the corresponding scheduling package in the right-hand tree.
    If the selected Reporting Agent setting from the Exceptions or Print function areas relates to a query with variables, you must select a variant of the query so that the scheduling package can be scheduled.
    You are in the view  Change in the right-hand tree of the Reporting Agent Scheduler. From the scheduling package context menu, choose Assign Variants The Variant Catalog. dialog window appears.
    Select the variant you want and choose  Select. The system adds the selected variants in the right tree in the Reporting Agent Scheduler in the Variant column.
    If you want to create a new variant for the required query or if you want to change variants already created, you have the option to process the variants in both the left and right-hand tree in the Reporting Agent Scheduler.
    Select Maintain Variants via the context menu of the Reporting Agent setting. You the see a screen on which you can process the variants for the selected query ( Create,  Display,  Change).
    Select the required variants as described above.
    Choose Next.
    You use this function to monitor and change the time and date settings on the mobile device.
    Prerequisites
         You have assigned the mobile device to a particular time zone.
         The synchronization service has been configured.
    Features
    You have the following options:
    Parameters for TIME_AGENT
    Parameters
    Description
    Possible Values
    AGENT_MODE
    Activate or deactivate monitoring
    ON, OFF
    AGENT_HISTORY
    Activate and deactivate the log function for the time and date setting
    TRUE, FALSE
    AGENT_HISTORY_INTERVAL
    Define intervals for logging (in minutes)
    AGENT_REPORT_ON_FIRST_CYCLE
    Or AGENT_REPORT_ON_SECOND_CYCLE
    Define synchronization cycle for sending data if the device is used by multiple users.
    Set at least one of the parameters.
    TRUE, FALSE
    AGENT_TRIGGER_ON_SYNC_COUNT
    Or
    Define the number of synchronization cycles run before data is sent to server
    Any integer
    0 – Never
    1 – With every synchronization
    2 – With every second synchronization
    AGENT_TRIGGER_ON_SYNC_INTERVAL
    and AGENT_TRIGGER_ON_SYNC_INTERVALTYPE
    Determine the intervals (type and interval) with which the data is sent to server
    Interval type:
    M – Minutes
    H – Hours
    D – Days
    Interval:
    Any integer
    0 – Never
    1 – In intervals of one minute, one hour, one day.
    Activities
    You define the values for the parameters in a parameter set (see Defining the Parameter Sets). Use the TIME_AGENT type to monitor the time and date settings.

  • Add another choice beside the (Report as Abuse)

    Hi Everyone,
     I would like to see another button with a kinder name such as (Check Post) or something added to the options in the image below that can be used for alerting moderators of things like Off Topic posts, posts with the wrong code language,
    or things like that, that are not really offensive and leave the (Report As Abuse)  button for things that are offensive such as Spamming, Being Rude to people, Using Foul Language, Adult Content, Posting malicious code and things of
    that nature. In my world they are two totally different categories and they should not be lumped into one.
     Suppose while i am viewing both the VB and C# forums at the same time and i accidentally post a VB code in the C# forum as a response to someone accidentally. I would be rather offended if i see that someone has marked it as Abusive when i didn`t mean
    no harm. Think about new comers to the forums. They may be offended as well and move to a different forum if they see that there question or reply to someone is marked as abusive.
     Thanks.   8)
    If you say it can`t be done then i`ll try it

    "If someone is posting to the wrong forum, it's considered an abusive post?"
     The (Mark As Abuse) button is basically used to alert a Moderator to look at the post and see why it is marked as abusive and they can decide if it is actually reasonable. They then have an option to remove the Abusive tag and let it go, remove the
    post, alert the poster that they have made a mistake, or whatever. I just think that in some cases as i have said above, the person may have made an honest mistake or have responded to someones question that takes it off topic a little. I don`t think that
    should be considered as Abuse like Spamming, leaving sarcastic rude comments to others, or using foul language.
     As i have said, if a new comer has made one of these mistakes then they may see it marked as Abusive and get offended causing them to decide to leave the forum. I don`t like to see that happen because, it would seem that the forum would want to keep
    people here and not offend anyone.
    "Are there any other hidden reasons for a post being marked abusive?"
     There is a whole list that seems to have grown over the years that are used as reasons why it may be marked as abusive and some of the reasons should not be considered as Abuse in my opinion. I am not sure where they are listed. I have seen some posted
    in some threads and can`t seem to locate the list at the moment.
    "That thread I linked is a good example of the attitude.  Here is another"
     I have seen some of this type of stuff and i don`t agree with anyone posting anything that is meant to be rude to othersno mater who they
    are. I am only asking for a button that will let the poster see that they may have made a small mistake instead of thinking they are being Abusive which may offend the poster if that was not there intent.
     My main point of this thread for example being, there is a difference between someone accidentally posting something in the wrong forum and someone posting a bunch of foul and/or offending words in a post on purpose that are meant to be sarcastic.
    If you say it can`t be done then i`ll try it
    This is a good suggestion. I think it was grouped together since they perform the same function... flag the mods to take action. Can you send this request to fissues at Microsoft?
    Thanks!
    Ed Price, Azure & Power BI Customer Program Manager (Blog,
    Small Basic,
    Wiki Ninjas,
    Wiki)
    Answer an interesting question?
    Create a wiki article about it!

  • How to add the dril down functionality in alv report.

    Hi All,
    I have a ALV report and now i want to add drill down functionality in this ALV report.
    See my code below:
    FORM f0002_build_field_catalog.
    Build the field catalog
    CLEAR ws_layout.
    ws_layout-colwidth_optimize = 'X'.
    ws_layout-edit = ' '.
      ws_field_catalog-col_pos = '1'.
      ws_field_catalog-fieldname = 'BUKRS'.
      ws_field_catalog-tabname = 'I_OUTPUT'.
      ws_field_catalog-seltext_l = 'Company Code'.
      ws_field_catalog-seltext_m = 'CCode'.
      ws_field_catalog-seltext_s = 'CCode'.
    ws_field_catalog-fix_column = 'X'.
    ws_field_catalog = 'X'.
    ws_fieldcat-ref_tabname  = 'VBKPF'.
      APPEND ws_field_catalog TO lt_fieldcat.
      CLEAR: ws_field_catalog.
      ws_field_catalog-col_pos = '2'.
      ws_field_catalog-fieldname = 'BELNR'.
      ws_field_catalog-tabname = 'I_OUTPUT'.
      ws_field_catalog-seltext_l    = 'Document no.'.
      ws_field_catalog-hotspot = 'V'.
      ws_field_catalog-seltext_m    = 'Doc.no.'.
      ws_field_catalog-seltext_s    = 'Doc.no.'.
      APPEND ws_field_catalog TO lt_fieldcat.
      CLEAR: ws_field_catalog.
      ws_field_catalog-col_pos = '3'.
      ws_field_catalog-fieldname = 'GJAHR'.
      ws_field_catalog-tabname = 'I_OUTPUT'.
      ws_field_catalog-seltext_l    = 'Year'.
      ws_field_catalog-seltext_m    = 'Year'.
      ws_field_catalog-seltext_s    = 'Year'.
      APPEND ws_field_catalog TO lt_fieldcat.
      CLEAR: ws_field_catalog.
      ws_field_catalog-col_pos = '4'.
      ws_field_catalog-fieldname = 'BSTAT'.
      ws_field_catalog-tabname = 'I_OUTPUT'.
      ws_field_catalog-seltext_l    = 'Status'.
      ws_field_catalog-seltext_m    = 'Status'.
      ws_field_catalog-seltext_s    = 'Status'.
      APPEND ws_field_catalog TO lt_fieldcat.
      CLEAR: ws_field_catalog.
      ws_field_catalog-col_pos = '5'.
      ws_field_catalog-fieldname = 'FLAG'.
      ws_field_catalog-tabname = 'I_OUTPUT'.
      ws_field_catalog-seltext_l    = 'Open/Cleared'.
      ws_field_catalog-seltext_m    = 'Open/Cleared'.
      ws_field_catalog-seltext_s    = 'Open/Cleared'.
      APPEND ws_field_catalog TO lt_fieldcat.
      CLEAR: ws_field_catalog.
      ws_field_catalog-col_pos = '6'.
      ws_field_catalog-fieldname = 'BLART'.
      ws_field_catalog-tabname = 'I_OUTPUT'.
      ws_field_catalog-seltext_l    = 'Doc.Type.'.
      ws_field_catalog-seltext_m    = 'Doc.Type'.
      ws_field_catalog-seltext_s    = 'Doc.Type'.
      APPEND ws_field_catalog TO lt_fieldcat.
      CLEAR: ws_field_catalog.
      ws_field_catalog-col_pos = '7'.
      ws_field_catalog-fieldname = 'WRBTR'.
      ws_field_catalog-tabname = 'I_OUTPUT'.
      ws_field_catalog-seltext_l    = 'Total Amount'.
      ws_field_catalog-seltext_m    = 'Total Amount'.
      ws_field_catalog-seltext_s    = 'Total Amount'.
      APPEND ws_field_catalog TO lt_fieldcat.
      CLEAR: ws_field_catalog.
      ws_field_catalog-col_pos = '8'.
      ws_field_catalog-fieldname = 'WAERS'.
      ws_field_catalog-tabname = 'I_OUTPUT'.
      ws_field_catalog-seltext_l    = 'Currency.'.
      ws_field_catalog-seltext_m    = 'Currency'.
      ws_field_catalog-seltext_s    = 'Currency'.
      APPEND ws_field_catalog TO lt_fieldcat.
      CLEAR: ws_field_catalog.
      ws_field_catalog-col_pos = '9'.
      ws_field_catalog-fieldname = 'LIFNR'.
      ws_field_catalog-tabname = 'I_OUTPUT'.
      ws_field_catalog-seltext_l    = 'Vendor'.
      ws_field_catalog-seltext_m    = 'Vendor'.
      ws_field_catalog-seltext_s    = 'Vendor'.
      APPEND ws_field_catalog TO lt_fieldcat.
      CLEAR: ws_field_catalog.
      ws_field_catalog-col_pos = '10'.
      ws_field_catalog-fieldname = 'NAME1'.
      ws_field_catalog-tabname = 'I_OUTPUT'.
      ws_field_catalog-seltext_l    = 'Vendor Name'.
      ws_field_catalog-seltext_m    = 'Name 1'.
      ws_field_catalog-seltext_s    = 'Name 1'.
      APPEND ws_field_catalog TO lt_fieldcat.
      CLEAR: ws_field_catalog.
      ws_field_catalog-col_pos = '11'.
      ws_field_catalog-fieldname = 'UZAWE'.
      ws_field_catalog-tabname = 'I_OUTPUT'.
      ws_field_catalog-seltext_l    = 'Payment Method Supplement'.
      ws_field_catalog-seltext_m    = 'PmtMthSuppl'.
      ws_field_catalog-seltext_s    = 'PmtMthSuppl'.
      APPEND ws_field_catalog TO lt_fieldcat.
      CLEAR: ws_field_catalog.
      ws_field_catalog-col_pos = '12'.
      ws_field_catalog-fieldname = 'XBLNR'.
      ws_field_catalog-tabname = 'I_OUTPUT'.
      ws_field_catalog-seltext_l    = 'Reference'.
      ws_field_catalog-seltext_m    = 'Ref. No.'.
      ws_field_catalog-seltext_s    = 'Ref. No.'.
      APPEND ws_field_catalog TO lt_fieldcat.
      CLEAR: ws_field_catalog.
    g_variant-report  = sy-repid.
       CLEAR struct_extab.
      MOVE '&XPA' TO struct_extab-fcode.
      APPEND struct_extab TO i_extab.
      MOVE '&OMP' TO struct_extab-fcode.
      APPEND struct_extab TO i_extab.
    Display the list
      CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
       EXPORTING
          i_callback_program      = ws_repid
          i_callback_user_command = 'HANDLE_USER_COMMAND'
         is_layout               = ws_layout
          it_fieldcat             = lt_fieldcat[]
          it_excluding            = i_extab[]
         i_default                = 'X'
         i_save                  =  'U'  "For user variants
         is_variant              = g_variant
        TABLES
          t_outtab                = i_output.
    ENDFORM.                    "f0002_build_field_catalog
    *&      Form  f0038_pf_status
          text
         -->I_EXTAB    text
    FORM f0038_pf_status USING i_extab TYPE slis_t_extab.       "#EC CALLED
      CLEAR struct_extab.
      MOVE '&XPA' TO struct_extab-fcode.
      APPEND struct_extab TO i_extab.
      MOVE '&OMP' TO struct_extab-fcode.
      APPEND struct_extab TO i_extab.
      SET PF-STATUS 'Z_PFSTATUS2' EXCLUDING i_extab.
    ENDFORM.                     "f0038_pf_status
    Pls tell me how i use this below dril down ability functionality in my code.
    See the requirement below.
    The Document Number, aka Accounting Document Number (BELNR) of each row will take the user to the appropriate document to edit as follows:
    For Parked documents:-
    If VBKPF-AWTYP (Reference Procedure) = “RMRP”, then the drilldown functionality should be to MIR4 using the Object ID in VBKPF- AWKEY. In this scenario the Object ID represents a Invoice Document Number, not an Accounting Document Number. Not the Object ID is a combination of Invoice Document Number and Fiscal Year
    If VBKPF-AWTYP = Any other value, then the drilldown functionality should be to FBV2 using the Object ID in VBKPF-AWKEY. In this scenario the Object ID represents a true Accounting Document Number. Note the Object ID is a combination of Company Code (VBKPF-BUKRS), Accounting Document Number (VBKPF-BELNR) and Fiscal Year (VBKPF-GJAHR)
    For Posted, not Cleared documents:-
    Drilldown ability should be to FB02. The combination of Company Code (BSIK-BUKRS), Accounting Document Number (BSIK-BELNR) and Fiscal Year (BSIK-GJAHR) will be used to open/drilldown to the correct document in FB02.
    For Cleared documents:-
    Drilldown ability should be to FB03. The combination of Company Code (BSIK-BUKRS), Accounting Document Number (BSIK-BELNR) and Fiscal Year (BSIK-GJAHR) will be used to open/drilldown to the correct document in FB03.
    Its very urgent, pls help on this.
    Thanks!
    Vipin

    Pls refer :
    https://wiki.sdn.sap.com/wiki/display/Snippets/ABAPInteractiveALVwithCallTransaction%28usingParameterID%29
    https://wiki.sdn.sap.com/wiki/display/Snippets/ABAPInteractiveALV+Program
    Regards,
    Anish Thomas
    Pls reward all useful answers

  • How to find out the Area Menu for a Report/ Table/Function Module

    Hi,
    Is there any procedure to find out the <b>"AREA MEANU"</b> for a Report/Table/Function Module...
    Or is there any Transaction code / Report is available to find out all the report for a particular "AREA MENU".
    Thank you for your quick response...
    Regards,
    Thiru
    <b></b>

    Hi,
    Check these below threads:
    user log in & log out time SAO
    How to find user log-out time ?
    Regards,
    Nitin

Maybe you are looking for