What are the external events of a report?

Hi,
Please tell me if you have any idea about what are the external events of a Report?
Thanks in advance.
MD.

Hi,
   When you run an executable program, the program flow is controlled by the external events in the ABAP runtime environment. The following diagram shows the sequence of the events:
check this link for more....
http://help.sap.com/saphelp_nw70/helpdata/en/9f/db99fa35c111d1829f0000e829fbfe/content.htm
Regards,
Shanthi.P
Reward points if useful ***

Similar Messages

  • What are the external events in report programming

    hi
    experts
    pz help me for this qn

    Chk this.
    http://help.sap.com/saphelp_nw70/helpdata/en/9f/db9a0735c111d1829f0000e829fbfe/content.htm

  • What are the maximum no of wad reports in a project

    Hi all,
    what are the maximum no of wad reports in a project.
    can you suggest how many people will work on wad reports  either one or more than one.
    can you provide me example scenerio.
    thanks,
    cheta.

    Hi ,
    The number of WAD Reports depends on your Reporting requirement.
    You can either have one WAD for one Report each. or you can also have more than one report in a single WAD.
    Could you please be more specific in what exactly your requirement is???

  • What are the tables used for this Report

    hi all..
    i am a fresher for ABAP. i need the help.
    what r the tables used for this report.
    Reports provide pending order details according to Material wise and customer wise for particular month.
    thanks in advance
    RK.Ashokkumar.
    9994262112.

    hi
    good
    try with these tables,
    MARA
    KNA1
    thanks
    mrutyun^

  • HT5219 What are the external monitor requirements that can support having two windows email and safari open side by side?

    I have a 27" iMac at home that supports this but would like to see if I can enable my Macbook air to do the same thing.  I want to find out if this capability can be supported with my Macbook air and if so what are the monitor requirements.

    Usually two causes of that, the first being the windows dpi scaling (most common cause) and the second being your graphics card driver needs to be updated.
    Try playing with the windows dpi settings
    Right click on your Desktop and select Screen Resolution
    Then in the screen that comes up, click on Make Text or Other Items Larger or Smaller
    Then move the slider under Change the Size of All Items to Smaller and restart windows 8
    Also, you can try clicking on Let me choose one scaling level for all my displays, then click on Custom sizing options and drag on the rulers to set 149% and see if that is any better.

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

    hi
    experts can u help me for this

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

  • What are the valid 'sources' for Fin Reports 11.1.2?

    Hi,
    Have a client that wants to report using Fin Reports 11.1.2. He wants to connect to a Oracle Schema or SQL Server data warehouse and then connect to Essbase/Planning cube and also to the Planning relational tables to report on supporting detail etc. I don't think FR can connect to a relational source other than HFM and/or Planning Detail. Is that correct? Or can it connect to any Oracle/SQL server database and report off that too. I thought Interactive Reporting (Brio) is the tool for that.
    Please advise.

    Hi,
    Here is the whole list: http://download.oracle.com/docs/cd/E12825_01/epm.111/bpmui_user/database_manager_fr.html
    Cheers,
    Mehmet

  • What are the best practices for audit report for SharePoint 2013 farm ?

    Hello,
    I am looking for the best practices for audit reporting in SharePoint 2013 farm.Can anyone please provide me checklist/tools/guidelines on same ?
    your help will be much appreciated.
    Thanks and Regards,
    Dipti Chhatrapati

    This is quite open ended question. A sharepoint farm should be well maintained as per :
    1. Microsoft's recommendations on : Topology, Hardware and Software requirements, Operational procedures and most important Capacity guidelines:
    http://technet.microsoft.com/en-us/library/ff758645(v=office.15).aspx
    http://technet.microsoft.com/en-us/library/cc262787(v=office.15).aspx
    2. Organisation's IT policies and procedures : Farm Configuration, Workload and monitoring
    http://technet.microsoft.com/en-us/library/ff758658(v=office.15).aspx
    http://technet.microsoft.com/en-us/library/ee748651(v=office.15).aspx
    3. Industry best practices
    I would suggest to start thinking over these lines and create a plan for your Sharepoint farm.
    You can then create powershell scripts to run these reports at certain frequency to find the changes, any deviation from the standard and health of the entire farm.
    Hope this helps!!
    I LOVE MS..... Thanks and Regards, Kshitiz (Posting is provided "AS IS" with no warranties, and confers no rights.)

  • What are the Dynamic Events avaliable in the LabView 6.1 Event Structure?

    I recieved LabView 6.1 recently and I am working with the Event Structure, and I'm trying to figure out what Dynamic Events are avaliable in the event structure, and how to access them. If you don't understand what I'm talking about, open a new VI in LabView 6.1 and drop an event structure on the diagram. Add an event and look at the dialog box that appears on the screen, specifically the Event Sources section. The third option in this area of the screen is "grayed out" but reads "Dynamic". I'm curious what these events are, and how I access them. I'm running WinNT 4 SP6.
    Thanks,
    Chris Davis

    I believe this is part of a feature which is not yet present in LabVIEW 6.1, but may be present in a future release.

  • What are the possiblities to create BO report on SAP Tables

    Hi All,
    Can any one please sugegst me the possiblities to create a BO report WEBI/Crystal on SAP ECC Tables .
    Thanks
    Bin.

    Hi Ingo,
    I really want to activate Transient Provider. I have ECC 6.0 EHP5 and BO 4.0 but when I try to activate transient provider I receive a dump error.
    When I the report rsrts_activate_r3is, I put the current mandant on the selection screen.
    Details:
    Error: UNCAUGHT_EXCEPTION
    Excep: CX_RSR_X_MESSAGE
    Program ABAP: CL_RSDM_READ_MASTER_DATA======CP
    Application Component: BW-WHM-MTD
    We put a OSS message  but we don´t have answer yet.
    I really appreciate your help in these case.
    Best regards,
    Gustavo

  • Quick report what are the notiifications are send out from SRM via SOST

    Hi all
    Can i have a list of messages sent out of SRM (from SRM via SOST.)
    sc completed by the buyer -
    but i want a set of all reports. so that i can decide i can filter go / no-go from srm system .
    any help is appreciated,
    what are the events are triggered notification.
    for eg. COMPLETED ...when buyer completed , requestor gets notification.
    so what are the other events. i have forgotten
    user creation too right? like that many..
    WHAT ARE THE ACTIONS IF I DO IN THE WEB , SOST entries will get created?. I KNEW BACKEND METHOD to download all sost message. but really we should know without seeing sost.
    Muthu

    You can check the fields of these tables via SE11
    Purchase Document Date  -  EKKO-BEDAT
    Item Description  -  EKPO-TXZ01
    Net price per item - EKPO-NETPR.
    Regards,
    Rich Heilman

  • What are the Different Reporting Types Offer By SAP Package

    Hello everyone...
    Been on SAP almost a year and finding there is alot to learn.
    Question: What are the different ways to generate reports and to link reports\programs across the SAP system. I know about BW, RRI, ABAP language, CRYSTAL.
    Are there any more ?
    Thank you in advance....
    Jim

    there are four reporting possibilities using business explorer in bw:
    bex analyser:
    (reports displayed in normal excell)
    web application:
    (publishing above reports in web)
    formated reporting:
    (crystal reports)
    mobile intelligence:
    (view reports in mobiles)
    hope it helps

  • What are the 'events' that are captured by a Visual Studio Workflow (PWA)

    Hello All,
    I need to understand what are the different events that Visual Studio workflow (PWA 2013) knows when it an event is triggered. As far as I know there are 3 events
    'OnProjectSubmit', 'OnProjectCommit' and “OnProjectCheckIn'.
    Are there any other events that workflow understands, especially on a click of a Save button?

    well done...
    http://www.soran.edu.iq

  • What are the list of .stock by storage location

    hi, iwant to devlop the report to stock by storage location.give me description about a report to list of .stock by storage location. what are the functional spects for this report, what are the tables and fields we have to used for this report plz give me sample report.

    Dear Radha Krishna,
    You can either use program RMMMBESTN (from SE38) or TCode MMBE. However, you can copy the above program into a 'Z' program and change the logic if your requirement is not served by the standard report or you want to enhance the same.
    Go through standard Reports:
    MMBE Stock Overview
    MB52 List of Warehouse Stocks on Hand
    MB53 Display Plant Stock Availability
    MB54 Consignment Stocks
    MB5B Stocks for Posting Date
    MB5K Stock Consistency Check
    MB5L List of Stock Values: Balances
    MB5T Stock in transit CC
    MB5W List of Stock Values
    MBBS Display valuated special stock
    MBLB Stocks at Subcontractor
    MBSF Release Blocked Stock via Mat. Doc.
    MBW1 Special stocks via WWW
    MC.1 INVCO: Plant Anal. Selection: Stock
    MC.5 INVCO: SLoc Anal. Selection, Stock
    MC.9 INVCO: Material Anal.Selection,Stock
    MC.D INVCO: MRP Cntrllr.Anal.Sel. Stock
    MC.H INVCO: Business Area Anal.Sel. Stock
    MC.L INVCO: Mat.Group Analysis Sel. Stock
    MC.P INVCO: Division Analysis Sel. Stock
    MC.T INVCO: Mat.Type Anal.Selection Stock
    MC48 INVCO: Anal. of Current Stock Values
    MC49 INVCO: Mean Stock Values
    MC50 INVCO: Analysis of Dead Stock
    MC8M Read Opening Stocks
    MCB) INVCO: Long-Term Stock Selection
    MCC4 Set Up INVCO Info Structs.from Stock
    MCH: RIS: STRPS/Mvmts + Stock - Selection
    MCKJ Selection version tree: Stock
    MCKR User-spec. sel. vers. tree: Stock
    MCNB BW: Initialize Stock Balances
    MCSK Call Standard Analyses of Stocks
    MD04 Display Stock/Requirements Situation
    ME27 Create Stock Transport Order
    ME2O SC Stock Monitoring (Vendor)
    MF65 Stock Transfer for Reservation
    MI35 Batch Input: Post Zero Stock Balance
    MIQ1 Batch Input: PhInvDoc. Project Stock
    MM73 Special Stocks: Preparation
    MM74 Archive Special Stocks
    MM75 Display Archive of Special Stocks
    MMBE_OLD Stock Overview
    MMN1 Create Non-Stock Material &
    MS04 Planning Scenario: Stock/Reqmts List
    MS29 Calculate Sim. Initial Stock
    Tables:
    MKPF Header: Material Document
    MSEG Document Segment: Material
    IKPF Header: Physical Inventory Document
    ISEG Physical Inventory Document Items
    SBSE Stock Mngmt Levels for Inventory Sampling
    SKPF Header Data: Inventory Sampling
    SLGH Elements of Stock Population
    SSCH Strata of Inventory Sampling
    T156 Movement Type
    MSKA Sales Order Stock
    MSKAH Sales Order Stock: History
    MSKU Special Stocks with Customer
    MSKUH Special Stocks at Customer: History
    MSLB Special Stocks with Vendor
    MSLBH Special Stocks at Vendor: History
    MSPR Project Stock
    MSPRH Project Stock: History
    MSSAH Total Sales Order Stocks: History
    MSSL Total Special Stocks with Vendor
    MSSQ Project Stock Total
    MSSQH Total Project Stocks: History
    http://goldenink.com/abap/files_in_sap.html
    http://www.erpgenie.com/abap/tables.htm
    Regards,
    Naveen.

  • What are the areas cover under CO module

    Hi Friends
                   What are the areas the CO-Controling module  covers in BW. I know some...CCA,PCA.Any more....What are the Business content Cubes,ODSs,Reports in for CO module.
    <removed by moderator>
    Thanks&Regards
    Revathi
    Edited by: Siegfried Szameitat on Nov 24, 2008 4:16 PM

    Hi,
    There is a doc in service market place that covers all co content.Search for it.
    You can also take a look at best practice for controlling.
    http://help.sap.com/bp_biv335/BI_EN/html/BW/ControllingAnalysis.htm
    Regards.

Maybe you are looking for

  • Trying to connect to Discoverer Plus or Viewer the following error

    HI, I am not sure that this is the correct forum. The following error occurred: "OracleBI Discoverer has not been started or has been stopped. Discoverer was stopped by your Administrator." Has anyone had the same problem? We are currently on version

  • How do i read the Shift register value of a vi which is written in the teststand sequence from labview exe

    Dear All.. My Qusetion is ... I have a VI in which I can writ the data to shift register and I can read( Differenent cases). I am Running the VI in write mode to write SAY '100' in the shiftreg( VI will be In teststand Sequence) . And I am reading th

  • P55M-GD45 win 7 x64 1.99GB useable

    I have been looking all over for an answer for this and it all points to Memory Remapping being disabled. I have the updated BIOS (1.4) and I cant see an option to enable Memory Remapping. From a forum search most topics say that is enabled by defaul

  • What is an ageing report?

    What exactly is an ageing report? What are different scenarios that fall in this category?

  • SAP Query- Is summation possible

    Dear All, Pls let me know if we can do summation in SAP Query to get a count on positions for example. Eg. If i ve say 25 positions in the system pulled out by through Query, can i be able to sum them up saying the count is "25" in SAP Query. Points