What r the main events called in an alv report.............

what r the mandatory events called in an alv grid report ................pls lemme know
Message was edited by:
        'GURU'

Hi
there are no mandatory events by default
chk this prog
Hi
chk this sample programs
report zkiran .
Global ALV Data Declarations
type-pools: slis.
Internal Tables
data: begin of ialv occurs 0,
test1(10) type c,
test2(10) type c,
end of ialv.
data: fieldcat type slis_t_fieldcat_alv.
start-of-selection.
perform get_data.
perform call_alv.
Form GET_DATA
form get_data.
ialv-test1 = 'ABC'.
ialv-test2 = 'DEF'.
append ialv.
ialv-test1 = 'GHI'.
ialv-test2 = 'JKL'.
append ialv.
ialv-test1 = '123'.
ialv-test2 = '456'.
append ialv.
endform. "GET_DATA
CALL_ALV
form call_alv.
perform build_field_catalog.
Call ABAP List Viewer (ALV)
call function 'REUSE_ALV_GRID_DISPLAY'
exporting
it_fieldcat = fieldcat
tables
t_outtab = ialv.
endform. "CALL_ALV
BUILD_FIELD_CATALOG
form build_field_catalog.
clear: fieldcat. refresh: fieldcat.
data: tmp_fc type slis_fieldcat_alv.
tmp_fc-reptext_ddic = 'Test1'.
tmp_fc-fieldname = 'TEST1'.
tmp_fc-tabname = 'IALV'.
tmp_fc-outputlen = '10'.
append tmp_fc to fieldcat.
tmp_fc-reptext_ddic = 'Test2'.
tmp_fc-fieldname = 'TEST2'.
tmp_fc-tabname = 'IALV'.
tmp_fc-outputlen = '10'.
append tmp_fc to fieldcat.
endform. "BUILD_FIELD_CATALOG
reward points to all helpful answers
kiran.M

Similar Messages

  • What are the main tables using in vendor performance report.

    what are the main tables using in vendor performance report.
    how many select statements are in ABAP reports.

    Refer the links -
    vendor performance report !!!
    vendor performance report
    vendor performance report
    I need standard vendor performance report
    Regards,
    Amit
    Reward all helpful replies.

  • 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 main sap script events and their functionality and usage?

    what are the main sap script events and their functionality and usage?

    Hi,
    Inside the Script, there are events like Top of Page, End of page etc.
    Please elaborate about your requirement.
    Best regards,
    Prashant

  • What are the main transaction codes in XI?

    What are the main transaction codes in XI?

    SAP XI TRANSACTION CODES
    ALRTCATDEF- Alerts Configuration.
    ALRTDISP - Display of Alerts Created
    SXMB_IFR -> Start Integration Builder
    SXMB_MONI -> Integration Engine - Monitoring
    SXI_MONITOR -> XI: Message Monitoring
    SXI_CACHE -> To Access IS runtime cache
    SXI_SUPPORT -> Test all the Repository and Directory Objects
    SXI_CACHE -> XI data directory cacheidx1 -> idoc adapter
    IDX2 -> idoc metadata
    IDX5 -> monitor idoc adapter
    SM21 -> log di sistema
    ST22 -> dump abap (analisi di eccezioni)
    SMQ1 -> messages inbound e outbound queue
    SMQ2 -> messages inbound e outbound queue
    SMICM -> J2EE administration
    ST06 -> stato della macchina cpu memory filesystem machine status - cpu, memory and file system.
    ST03 -> workload.
    SCC4 -> visualizza mandanti del sistema
    WE20 -> partner profiles
    sale - ale settings
    RZ10 - edit system profile
    SM59 ->mantain rfc destinations
    BD64 -> mantain distribution model (trasformazioni)
    SU01 -> users
    AL08 -> list all logged users(user login logon)
    SE10 -> Change Request
    SE09 -> Change Request
    WE05 -> All idocs
    WE19 -> IDoc Test Tool
    WE21 -> port definition
    SE11 -> Data dictionary
    SM21 -> log sistema xi
    se37 -> mantain funcion modules
    SICF -> http server configuration
    SMGW -> trace, alzare livello di trace.
    BD13 ->
    BD64 -> modelli di distribuzione
    PFCG -> Roles
    tabella TSTC -> sap transactions codes
    tabella TSTCT -> transaction descriptions
    STMS -> transports management
    SPAM -> apply ABAP support packages
    SPAU -> manage objects after apply support packages
    SE01 -> manage change requests
    SLDCHECK -> Test SLD Connection
    SLDAPICUST-> SLD API Customizing
    SXMB_ADM -> Integration Engine - Administration
    SXMB_MONI_BPE -> Process Engine - Monitoring
    SE38 -> ABAP Editor
    SE11 -> ABAP Dictionary
    ST22 -> ABAP dump analysis
    SPROXY-> ABAP Proxy Generation
    SE80 -> Object Navigator
    ABAPDOCU -> ABAP Documentation and Examples
    SE24-> Class Builder
    SM21-> Online System Log Analysis
    SMQ1-> qRFC Monitor (Outbound Queue)
    SMQ2-> qRFC Monitor (Inbound Queue)
    RZ70-> SLD Administration
    SM58-> Asynchronous RFC Error Log
    SM59-> RFC Destinations (Display/Maintain)
    SMICM-> ICM Monitor
    WE60-> Documentation for IDoc types
    BD87-> Status Monitor for ALE Messages
    IDX1-> Port Maintenance in IDoc Adapter
    IDX2-> Meta Data Overview in IDoc Adapter
    WE05-> IDoc Lists
    WE02-> Display IDoc
    WE19-> Test tool
    WE09-> Search for IDocs by Content
    WE20-> Partner Profiles
    WE21-> Port definition in XI
    SE16-> Data Browser
    SE93-> Maintain Transaction Codes
    SM30-> Call View Maintenance
    SU01-> User Maintenance
    SM02-> System Messages
    BD54 -Logical System Creation.
    SWXF_PBUILDER -> for Detail BPM Process
    SMQS - > to register the destination in QOUT scheduler
    WEOUTQUEUE - > to start the queue processing
    SMQR - > to register the queue
    IDXPW - > to activate the IDOC message package
    IDXP - > to monitor the message packages.
    SWF_XI_CUSTOMIZING -> transaction to check prerequisites for integration processes.
    http://www.erpgenie.com/abaptips/content/view/452/62/

  • What are the main differences between  3 three important class types

    PP members
    What are the main differences between class type 300(variants) , class type 200 (configurable objects) & 001 ( material class)
    Please elucidate on the above
    Thanks
    Suren R

    Hi,
    The class type is a central concept in the classification system. The class type determines how classes are processed, and how objects can be classified and retrieved in these classes. In Customizing for Classification, you define the settings for a class type. You define class types for a specific object type, such as materials. You can then use classes of this class type to classify objects of this object type.
    When you first create a class, you must enter a class type for the class. Each class type is a closed system. There is no link between the different class types.
    he class type determines the following:
    Which object types you can assign to a class
    Which class maintenance functions you can process
    Whether you can classify objects in more than one class
    Which class statuses, organizational areas, and text types are supported in class maintenance functions
    Whether you can use engineering change management for classification
    Which filter functions you can use to restrict the search result
    All materials can be classified with class type 001. Class type 300 is for variant configuration the variants under a class item are called as variants and can be picked during sales order creation. Class type 200 is for classes that are used as class items in bills of material. You can classify the same materials separately in these class types.
    This is basically used to differentiate the BOM class items.
    Prakash

  • What are the main points to freeze technical scenario in SRM?VeryUrgent Pls

    Hi SRM Guruu2019s,
    What are the main points to freeze technical scenario in SRM?.
    Please mention main points to select Classic Scenario and Extended Classic scenario individually.
    I would really appreciate.
    Regards,
    John.
    Edited by: johnmiller465 on Nov 12, 2009 3:30 PM

    i believe what is your PPS version / SRM version
    generally PPS works on EXtended Classic
    http://wiki.sdn.sap.com/wiki/display/SRM/PPS-ProcurementforPublicSector-+enhancements#PPS-ProcurementforPublicSector-enhancements-PPSprocessisbasedinExtendedClassicscenario
    Procurement for Public Sector - PPS1.0: An Overview
    Ralf Wolfgang Geithner
    Business Card
    Company: SAP AG
    Posted on Nov. 20, 2007 11:57 AM in Public Sector  Subscribe
    Print
    Permalink
    Introduction:
    SAP PPS1.0 is an addon to SAP SRM5.0 addressing requirements of public sector procurement. SAP SRM is used as functional frontend to support the main procurement processes:
    Public tendering
    Awarding
    Contract negotiation
    Purchase order creation
    SAP PPS1.0 has been designed to work in the extended classic scenario, where SAP ERP 2004 functions as backend supporting the processes:
    Sales Order processing
    Purchase Requisition processing
    Goods Receipt processing
    Invoice Receipt processing
    Main Features:
    PPS 1.0 features a couple of unique functions designed for the needs of public sector customers, namely:
    Document Builder Integration
    Records Management Integration
    Smart document numbering
    Funds Management integration
    Acceptance at Origin
    Central Contractor Registration (CCR)
    Contract Tracking and Monitoring
    Close Out Execution
    Enhanced Versioning
    FPDS Reporting
    Guaranteed Minimum
    Maximum Quantity per Period
    Public Sector User Status
    Reason Codes for Document Changes
    Smart numbering of procurement documents
    Selective Release
    Sourcing Priorization
    In the next couple of blog posts I want to describe the different features and  give some guidelines for the implementation of the functionality.
    What Next?
    I plan to start with the smart numbering which is called as well "long procurement number"
    Ralf Wolfgang Geithner is Senior Developer in Procurement for Public Sector core team

  • What is the main diff b/n ldb pnp and pnpce?

    hi ,
    what is the main diff b/n ldb pnp and pnpce?
    thanks.

    Hi Arun,
      PNP/PNPCE  - Both are Logical Databases for PA Module
    In PNPCE - CE stands for Concurrent Employment.
    The differnces are:
    The PNPCE logical database supports the evaluation of HR master data. It includes the functions of the PNP logical database and offers additional evaluation options. Therefore, you should use the PNPCE logical database instead of the PNP logical database for all new developments.
    The enhanced functionality of PNPCE in comparison to PNP essentially concerns the evaluation of Concurrent Employment, that is the possibility to group evaluate several assignments/personnel numbers of a person. The new events 'GET PERSON' and 'GET GROUP' as well as an enhanced syntax for the INFOTYPES statement (addition AS PERSON TABLE) for the procurement of infotype data enable you to use the new functionality. The use of these new functions is optional. You can run a PNPCE report that does not use the new events and the addition for the INFOTYPES statement in a PNP-compatible session. Since the PNPCE also has an improved selection screen, each report benefits from this even if the report does not use the functions for evaluating Concurrent Employment.
    Hope this helps you.
    Regards,
    Chandra Sekhar

  • What is the main funtion of Accounting commands

    Hi,
    Can any one tell me that,
    what is the main funtion of below commands in TACACS
    aaa accounting exec default start-stop group tacacs+
    aaa accounting commands 1 default start-stop group tacacs+
    aaa accounting commands 15 default start-stop group tacacs+
    aaa accounting system default start-stop group tacacs+

    aaa accounting exec default start-stop group tacacs+
    !--- Log the start and stop of EXEC session to the device. When the user logged in and when the user logged out. Total time spent.
    aaa accounting commands 1 default start-stop group tacacs+
    !--- Account/Log all the commands executed by the user, that are at privilege level 1.
    aaa accounting commands 15 default start-stop group tacacs+
    !--- Account/Log all the commands executed by the user, that are at privilege level 15.
    aaa accounting system default start-stop group tacacs+
    !--- Send the log to the Tacacs server about the system events (reboot etc..)
    More details,
    http://www.cisco.com/en/US/docs/ios/security/command/reference/sec_a1.html#wp1038916
    Regards,
    Prem
    Please rate if it helps!

  • What is the main functionality of FM 'ISU_S_PAYSCHEME_ROLLIN_ROLLOUT' ?

    Hi Folks,
      I need to use the function module 'ISU_S_PAYSCHEME_ROLLIN_ROLLOUT'. what is the main functionality of this function module? there is no documentation available for this FM.
    Thanks in advance

    Hi,
    Plz follow the link below for answer of your question.
    Link is: Re: how to call standard SAP method in the Custom Program ?
    Thanks & Regards,
    Sarita Singh Rathour

  • What is the main difference between these two api

    Hi
    I am using portal 3.0.9.8.1 under NT environment.
    I am planning to change the user's password programmatically.
    Could someone advise me about the difference between these two
    api:
    wwsso_api_user_admin.change_password and
    wwsso_api_user_mgr.change_password
    Are these api the same?Are they affecting the same table?
    Thanks in advance for any clarification
    Regards

    Michelle1892773 wrote:
    What is the main difference between LOCAL VARIABLE, REFERENCE, PROPERTY NODE and INVOC. NODE?
    Can u show this with an example in a VI using all these?
    Basic overview. Someone can go into more depth if they want.
    Local Variable - Correlates to some location in memory that holds information. Based on the data type, it looks at that location and interprets the 1's and 0's as either a double, integer, string, structure(cluster), etc.
    Reference - ill leave the details of this to someone else I can't give a decent explanation.
    Property node- sets different "properties" of a control/indicator etc. One of the properties is value so that works similar to a local variable. However, you can set much more than that. For example, with controls you can set the property of visible, not visible, color, etc etc.
    Invoke node - invokes some "method." i.e. calls some function to act on something
    These may not be the best explanations, or even 100% correct. But it should get you started. I'm sure someone else will build on this.
    CLA, LabVIEW Versions 2010-2013

  • What is the main difference between Enhancements and BADI.?

    What is the main difference between Enhancements and BADI.?plzz tell
    Edited by: Alvaro Tejada Galindo on Feb 13, 2008 3:48 PM

    CMOD is the Project Management of SAP Enhancements (i.e., SMOD Enhancements). SMOD contains the actual enhancements and CMOD is the grouping of those SMOD enhancements.
    Difference Between BADI and User Exits
    BADI's can be used any number of times, where as USER-EXITS can be used only one time.
    Ex:- if your assigning a USER-EXIT to a project in (CMOD), then you can not assign the same to other project.
    BADI's are oops based.
    Business Add-Ins are a new SAP enhancement technique based on ABAP Objects. They can be inserted into the SAP System to accommodate user requirements too specific to be included in the standard delivery. Since specific industries often require special functions, SAP allows you to predefine these points in your software. 
    As with customer exits two different views are available:
    In the definition view, an application programmer predefines exit points in a source that allow specific industry sectors, partners, and customers to attach additional software to standard SAP source code without having to modify the original object. 
    In the implementation view, the users of Business Add-Ins can customize the logic they need or use a standard logic if one is available.
    In contrast to customer exits, Business Add-Ins no longer assume a two-level infrastructure (SAP and customer solutions), but instead allow for a multi-level system landscape (SAP, partner, and customer solutions, as well as country versions, industry solutions, and the like). Definitions and implementations of Business Add-Ins can be created at each level within such a system infrastructure.
    SAP guarantees the upward compatibility of all Business Add-In interfaces. Release upgrades do not affect enhancement calls from within the standard software nor do they affect the validity of call interfaces. You do not have to register Business Add-Ins in SSCR.
    The Business Add-In enhancement technique differentiates between enhancements that can only be implemented once and enhancements that can be used actively by any number of customers at the same time. In addition, Business Add-Ins can be defined according to filter values. This allows you to control add-in implementation and make it dependent on specific criteria (on a specific Country value, for example).
    All ABAP sources, screens, GUIs, and table interfaces created using this enhancement technique are defined in a manner that allows customers to include their own enhancements in the standard. A single Business Add-In contains all of the interfaces necessary to implement a specific task.
    The actual program code is enhanced using ABAP Objects. In order to better understand the programming techniques behind the Business Add-In enhancement concept, SAP recommends reading the section on ABAP Objects.

  • What is the main difference between menu_exits and user_exits

    what is the main difference between menu_exits and user_exits

    Hi,
    User Exits:
    A user exit is a three character code that instructs the system to access a program during system processing.
    SXX: S is for standard exits that are delivered by SAP. XX represents the 2-digit exit number.
    UXX: U is for user exits that are defined by the user. XX represents the 2-digit exit number
    Menu Exits:
    Menu exits add items to the pulldown menus in standard SAP applications. You can use these menu items to call up your own screens or to trigger entire add-on applications.
    SAP creates menu exits by defining special menu items in the Menu Painter. These special entries have function codes that begin with "+" (a plus sign). You specify the menu item’s text when activating the item in an add-on project.
    Regards,
    Priyanka.

  • What is the main difference between view and materialize view and advantage of Mview   ??

    What is the main difference between view and materialize view and advantage of Mview   ??

    1.A view uses a query to pull data from its associated tables.
    2.Views do not have data's physically stored in the Database.
    3.Views Get the Data from 2 or more tables and displays as a single block.
    4.But a materialized view is a table on disk is a result set of a query done.
    5.A Materialized view can have data's in the database.
    6.Materialized view are used for Boosting the Performance.
    7.And the important one is Materialized views are updated based on the parameters defined when they are created.
    8.By using triggers we can update the data in a materialized view.
    9.When you call a materialized view it will show the data when it was last updated.
    Hope it helps.

  • What are the parameters in Call transaction method?

    Hi ABAPER'S,
        Please give me what are the parameters in call transaction method?
    Thanks,
    Prakash

    Processing batch input data with CALL TRANSACTION USING is the faster of the two recommended data transfer methods. In this method, legacy data is processed inline in your data transfer program.
    Syntax:
    CALL TRANSACTION <tcode>
    USING <bdc_tab>
    MODE  <mode>
    UPDATE  <update>
    <tcode> : Transaction code
    <bdc_tab> : Internal table of structure BDCDATA.
    <mode> : Display mode:
    A
    Display all
    E
    Display errors only
    N
    No display
    <update> : Update mode:
    S
    Synchronous
    A
    Asynchronous
    L
    Local update
    A program that uses CALL TRANSACTION USING to process legacy data should execute the following steps:
    Prepare a BDCDATA structure for the transaction that you wish to run.
    With a CALL TRANSACTION USING statement, call the transaction and prepare the BDCDATA structure. For example:
    CALL TRANSACTION 'TFCA' USING BDCDATA
    MODE 'A'
    UPDATE 'S'.
    MESSAGES INTO MESSTAB.
    IF SY-SUBRC <> 0.
    <Error_handling>.
    ENDIF.
    The MODE Parameter
    You can use the MODE parameter to specify whether data transfer processing should be displayed as it happens. You can choose between three modes:
    A Display all. All screens and the data that goes in them appear when you run your program.
    N No display. All screens are processed invisibly, regardless of whether there are errors or not. Control returns to your program as soon as transaction processing is finished.
    E Display errors only. The transaction goes into display mode as soon as an error in one of the screens is detected. You can then correct the error.
    The display modes are the same as those that are available for processing batch input sessions.
    The UPDATE Parameter
    You use the UPDATE parameter to specify how updates produced by a transaction should be processed. You can select between these modes:
    A Asynchronous updating. In this mode, the called transaction does not wait for any updates it produces to be completed. It simply passes the updates to the SAP update service. Asynchronous processing therefore usually results in faster execution of your data transfer program.
    Asynchronous processing is NOT recommended for processing any larger amount of data. This is because the called transaction receives no completion message from the update module in asynchronous updating. The calling data transfer program, in turn, cannot determine whether a called transaction ended with a successful update of the database or not.
    If you use asynchronous updating, then you will need to use the update management facility (Transaction SM12) to check whether updates have been terminated abnormally during session processing. Error analysis and recovery is less convenient than with synchronous updating.
    S Synchronous updating. In this mode, the called transaction waits for any updates that it produces to be completed. Execution is slower than with asynchronous updating because called transactions wait for updating to be completed. However, the called transaction is able to return any update error message that occurs to your program. It is much easier for you to analyze and recover from errors.
    L Local updating. If you update data locally, the update of the database will not be processed in a separate process, but in the process of the calling program. (See the ABAP keyword documentation on SET UPDATE TASK LOCAL for more information.)
    The MESSAGES Parameter
    The MESSAGES specification indicates that all system messages issued during a CALL TRANSACTION USING are written into the internal table <MESSTAB> . The internal table must have the structure BDCMSGCOLL .
    You can record the messages issued by Transaction TFCA in table MESSTAB with the following coding:
    (This example uses a flight connection that does not exist to trigger an error in the transaction.)
    DATA: BEGIN OF BDCDATA OCCURS 100.
    INCLUDE STRUCTURE BDCDATA.
    DATA: END OF BDCDATA.
    DATA: BEGIN OF MESSTAB OCCURS 10.
    INCLUDE STRUCTURE BDCMSGCOLL.
    DATA: END OF MESSTAB.
    BDCDATA-PROGRAM = 'SAPMTFCA'.
    BDCDATA-DYNPRO = '0100'.
    BDCDATA-DYNBEGIN = 'X'.
    APPEND BDCDATA.
    CLEAR BDCDATA.
    BDCDATA-FNAM = 'SFLIGHT-CARRID'.
    BDCDATA-FVAL = 'XX'.
    APPEND BDCDATA.
    BDCDATA-FNAM = 'SFLIGHT-CONNID'.
    BDCDATA-FVAL = '0400'.
    APPEND BDCDATA.
    CALL TRANSACTION 'TFCA' USING BDCDATA MODE 'N'
    MESSAGES INTO MESSTAB.
    LOOP AT MESSTAB.
    WRITE: / MESSTAB-TCODE,
    MESSTAB-DYNAME,
    MESSTAB-DYNUMB,
    MESSTAB-MSGTYP,
    MESSTAB-MSGSPRA,
    MESSTAB-MSGID,
    MESSTAB-MSGNR.
    ENDLOOP.
    The following figures show the return codes from CALL TRANSACTION USING and the system fields that contain message information from the called transaction. As the return code chart shows, return codes above 1000 are reserved for data transfer. If you use the MESSAGES INTO <table> option, then you do not need to query the system fields shown below; their contents are automatically written into the message table. You can loop over the message table to write out any messages that were entered into it.
    Return codes:
    Value
    Explanation
    0
    Successful
    <=1000
    Error in dialog program
    > 1000
    Batch input error
    System fields:
    Name:
    Explanation:
    SY-MSGID
    Message-ID
    SY-MSGTY
    Message type (E,I,W,S,A,X)
    SY-MSGNO
    Message number
    SY-MSGV1
    Message variable 1
    SY-MSGV2
    Message variable 2
    SY-MSGV3
    Message variable 3
    SY-MSGV4
    Message variable 4
    Error Analysis and Restart Capability
    Unlike batch input methods using sessions, CALL TRANSACTION USING processing does not provide any special handling for incorrect transactions. There is no restart capability for transactions that contain errors or produce update failures.
    You can handle incorrect transactions by using update mode S (synchronous updating) and checking the return code from CALL TRANSACTION USING. If the return code is anything other than 0, then you should do the following:
    write out or save the message table
    use the BDCDATA table that you generated for the CALL TRANSACTION USING to generate a batch input session for the faulty transaction. You can then analyze the faulty transaction and correct the error using the tools provided in the batch input management facility.

Maybe you are looking for