Difference between Next Set and Next Page

Hi,
does anyone know what is the difference between Next Set Template and Next Page Template in a Report Template?
Thanks,
Gari.

When you have a report with say 15 pages you can split it into a set like:
page 1 -5 , 6 - 10, 11 -15
When you select the next set HTML DB wil go from
1,2,3,4,5 [next set] to 6,7,8,9,10 [next set]
When you go to the next page is just shows the next page. You can go from page 5 to 6 with the next page and still end up on the next set :-).
Chris

Similar Messages

  • What is the difference between "create set" and "create dynamic set"?

    What is the difference between  "create set" and "create dynamic set"?
    we have a complete cube ready for production that was tested and working without any issues in non-r2. we found that some "create set" assignments don't work in R2. But when changed to from  "create set" to "create dynamic set"?
    they are working, However, not sure how it will impact other areas of the cube.

    Thanks YuliaKlimov, I can reproduce this issue, but I cannot explain the different behaviors between SSAS 2008 and 2008R2. As a workaround,
    could you try to use dynamic set or create statics set but with fixed member for example:
    CREATE 
    SET CURRENTCUBE.[Prior Month] AS
    [Date].[Date Key].&[20050723].PrevMember
    , DISPLAY_FOLDER = 'Relative Period Sets';
    Personally, I think your set is dynamic set, because the currentmember is changed base on current selection. You can also submit this issue
    on below official link to get confirmation from Product Group:
     https://connect.microsoft.com/SQLServer/
    Thanks,
    Raymond
    Raymond Li - MSFT

  • Differences between BC Set SOLMAN40_CHARM_BASICFUNC_001 and database.

    Hello Team,
    We are configuring Change Request management in Solution manager.
    Activation of BC sets ends with warning.Activation log shows below error.
    'Differences between BC Set SOLMAN40_CHARM_BASICFUNC_001 and database. Check values'
    There errors like "
    Field Not Copied
    Difference between BC Set and Table"
    We are through with note :903527  which suggest "2) Create a new transport request (Transaction SE09) in the source client of your Solution Manager system. Unpack the file Piecelist_Change_Management_Init.zip, which is attached to this note. Copy the contents of the file Piecelist_Change_Management_Initial.txt into the transport request. Use Transaction SCC1 to import the transport request into your Solution Manager client"
    But how to "Copy the contents of the file Piecelist_Change_Management_Initial.txt into the transport request"?
    Please let me know if you have any hint.
    Best Regards,
    Tushar

    status/action??
    when u click action tab in maintenance transaction the status updated auomatically.
    have u checked the errors shown in error tab....after u removed the errors....
    thn u choose up 'update maintenance cycle' action press save button the status will be same but error button wiil be green
    Then u have action Next phase"'in dev with release"
    If it is not appearing even there is no error........Pls  ck the action profile or ask solman consultant to chk the same
    Hope it clarifies
    Regards
    Prakhar

  • WHAT IS THE DIFFERENCE BETWEEN PHRASE GROUP AND PHRASE SET?

    WHAT IS DIFFERENCE BETWEEN PHRASE GROUP AND PHRASE SET?

    Hi Ramya,
    Definition of a Phrase group is a number of phrases contained in a phrase library grouped according to logical criteria. A phrase can be assigned to only one phrase group.
    Phrase set is grouping of phrases for a purpose which includes allowed phrases for a value assignment type and Default phrases for a value assignment type. A phrase can be assigned to a number of phrase sets.
    Hope this helps you
    Best Regards
    Srinivas

  • What is the difference between quarterly patches and patch sets

    Hello,
    What is the difference between quarterly patches and patch sets?
    Should we always apply the latest quarterly pathches?
    Is it better to apply to the latest patch set if one can afford?

    The quarterly patch sets are generally security fixes, or Critical Patch Updates (CPU). Oracle strongly recommends that the CPU patches are applied. CPU and quarterly patches do not change the release/version of the database.
    The patch sets contain bug fixes and do change the release/version of the database.
    As with all patches you should test them on a test database before deploying in production. If you have vendor supported applications you should contact your vendor before applying any patchsets.

  • Feature set difference between FI-AR and FI-CA

    Hi,
    While I am trying to do a comparison analysis between FI-AR/AP and FI-CA for Insurance Industry, I can deduce various facts like FI-CA been developed for transaction extensive industries like telecom/insurance which might often need automated processing (FI-AR appears to have more of manual processes for handling aspects of incoming payments) along with required performance. FI-AR/AP are more of standard Accounts receivable/payable module not necessarily catering to exact needs of industries mentioned above. Another major difference is the more flexible master data model FI-CA has to offer compared to FI-AR/AP.
    However, I am not able to deduce clearly if there are corresponding features available in FI-AR/AP for specific features available in FI-CA for handling incoming & outgoing payments. e.g.:
    1) Is bank reconciliation supported in FI-AR/AP? Do we have mechanisms to upload electronic bank statement for the same?
    2) Does FI-AR provides varying features like different lot processing in FI-CA for bulk processing, Cash desk (i know this is not supported in FI-AR). The process of clearing appears to be very manual intensive.
    3) Similarly what is the support for payments (especially automated for bulk processing) in FI-AP? 
    4) Assume other insurance industry specific features like brokers collection, collection agency collections, co-insurance specific features etc. are not supported in FI-AR/AP and no corresponding features would exist for obvious reasons.  
    Please suggest any other major differences between FI-CA and FI-AR/AP from an Insurance/Reinsurance industry perspective you may know of.
    Thanks in advance for your time.
    Regards,
    Ankit

    Ravindra,
    1) Check the configuration.
    Data from SD is posted to accounts (FI/PCA) via condition type -> accout key -> access sequence -> account.
    Data from SD is posted to SIS via the mapping of condition type to key figures.
    2) Check if values are posted to sales accounts directly from FI. These will not reflect in SIS.
    Mohit

  • Difference between Drilldown report and Interactive report

    There is no difference between drill down and interactive report, they are the same.
    With drilldown reporting, SAP provides you with an interactive information system to let you evaluate the data collected in your application. This information system is capable of analyzing all the data according to any of the characteristics that describe the data. You can also use any key figures you wish to categorize your data. You can display a number of objects for a given key figure, or a number of key figures for a given object. In addition, the system lets you carry out any number of variance analyses (such as plan/actual comparisons, fiscal year comparisons, comparisons of different objects, and so on).
    You can produce both simple, data-directed lists (basic reports) and complex, formatted lists in drilldown reporting (form reports).
    Drilldown report provides you with comfortable functions for navigating through your data. For example, you can jump to the next level of detail or the next report object on the same level, hide individual levels and switch between the detail and drilldown lists. It also provides a number of additional functions which let you process lists interactively (sorting, conditions, ranking lists, and so on). SAP Graphics, SAPmail and the Excel List Viewer are also integrated into drilldown reporting.
    The drilldown functions are divided into three groups which differ in the number of functions available. That way each user can choose the functional level most suited for his requirements.
    In addition to the online functions for displaying reports, drilldown reporting also provides functions which let you print reports. A number of formatting functions are available to let you determine the look of your printed reports (page breaks, headers and footers, underscores, and so on).
    The menus and the functions available directly on the drilldown report make it easy to use the information system.
    What is an Interactive Report?
    An interactive report generally works in the following fashion:
    1. Basic list is displayed.
    2. User double clicks on any valid line
        or
        User selects a line and presses as button on the tool bar.
    3. The corresponding event is triggered
    4. Then in the code, the line on which action was done, is read.
    5. Depending on the values in that selected line, a secondary list is displayed.
    6. Steps from 2-5 are repeated till the end.
    From the above explanation, I believe, its clear that, the 20th list, will essentially depend on the "selected line" of 19th list. According to your question, you want to move to 20th list directly, without "a prior list". May I know the exact requirement so that, an appropriate solution can be suggested? 
    Again, your question was, how to move to 20th list directly on pressing of execute button. Its not possible to move to 20th list. You must cross over a basic list, before you can go to a different list level, using the code given by Pavan. 
    What are Drilldown reports?
    The lines of basic list of a drilldown report when clicked, will take the user to the corresponding (standard) object's display.
    For eg: Suppose your report's primary component is purchase requisition, (assume you are printing PR details), and the basic list displays details of many PRs.
    Eg: when clicked on a particular line of the PR basic list, it takes you to std t-code me53 (display of purchase requisition). This is the 'Drill-down' functionality.
    For this, in the at-line selection of your program, as per the above ex: you'll set the parameter ID of PR number BAN (that you can get from Data element) in memory (using set parameter id) and then calling the corresponding transaction (usually skipping initial screen of the std t-code).   
    Likewise, if it's Material Number (Matnr), you'll be displaying MM03 transaction w.r.t. the line's matnr.
    AKSHAT..........

    Good, information. But I think you should post these items in Wiki, in place of forum, as here we have Qns & Ans;  problems and solutions.
    https://www.sdn.sap.com/irj/sdn/wiki
    [ABAP Development > ABAP General ]
    Wiki is the right place for such knowledge base
    Thanks!!
    Regards,
    Vishal.

  • List of differences between PSE 40 and PSE30

    A lot of users are asking what are the differences between PSE 30 and PSE 40.
    This Thread provides information on this subject. First, you will find information copied from the section "New Features" of the useful "Adobe Photoshop Elements 4.0 User Guide". Then later on, you might find additional information on the same subject provided by users of PSE.
    --- Start of copy of information in the PSE 4.0 User Guide ----
    1 What's new in PSE 4.0
    1.1 Editing and selection
    1.1.1 Magic Selection Brush tool
    Easily and accurately select portions of your photos using this new tool in either Standard Edit and Quick Fix. Simply scribble or place dots on the object you want to select -no need to precisely outline the object- and Adobe Photoshop Elements selects the object for you. You can add to or subtract from the selection by using additional tools in the options bar. (See User Guide "To use the Magic Selection Brush tool" on page 193.)
    1.1.2 Magic Extractor.
    Easily select an object in a photo and extract it from its background. Just scribble or place dots on
    the object you want to extract; then scribble or place dots on the background, and Photoshop Elements separates the object from its background. This tool is perfect for creating composites or scrapbook images. (See User Guide "To use the Magic Extractor" on page 194.)
    1.1.3 Skin tone adjustment
    Click an area of skin and watch the tonal balance of all colors in the photo improve. If you
    want, you can also manually adjust the color by using color sliders. (See User Guide "To adjust the color of skin tone" on page 224.)
    1.1.4 Red eye removal
    Automatically remove red eye during import, or select one or more files and easily remove red eye
    in either the Organizer or the Editor. (See User Guide "To remove red eye" on page 249.)
    1.1.5 Defringe
    Automatically remove the colored specs or halo around the edges of a selection. (See User Guide "To defringe a Selection" on page 200.)
    1.1.6 Straighten tool
    Straighten and crop crooked photos by drawing a horizontal or vertical line in the image. Photoshop
    Elements aligns the photo to that line. (See User Guide "To straighten an image" on page 243.)
    1.1.7 WYSIWYG font menu
    What you see is what you get -see what each font looks like from within the font menu. (See
    User Guide "To choose a font family and style" on page 332.)
    1.2 Sharing and printing
    1.2.1 One-click printing (US, Canada, Japan only)
    Order prints and professional hardbound photo books directly from Photoshop Elements simply by dragging the items to the Order Prints palette. (See User Guide "To use the Order Prints palette (US, Canada, Japan only)" on page 401.)
    1.2.2 Slide shows on TV
    If you have Windows¨ XP Media Center 2005 installed, you can view your Photoshop Elements
    slide shows on your TV and navigate using your TV remote control. (See User Guide "To output a slide show" on page 354.)
    1.3 Tagging and organizing
    1.3.1 Face tagging
    Select a group of photos and let Photoshop Elements isolate and display all the faces so that you can
    quickly tag them. The Find Faces dialog box displays thumbnails of each face until you tag it. (See User Guide "To automatically find faces for tagging" on page 101.)
    1.3.2 Search by metadata
    Search for a variety of metadata criteria, such as file name, file type, shutter speed, camera
    model, date, and tags. You can search on multiple criteria at once. (See User Guide "To find photos by details (metadata)" on page 89.)
    1.3.3 PDF support
    Manage and tag PDF files in the Organizer. PDF files remain intact as one file that you can tag. Open
    the PDF in the Editor to extract individual pages. (See User Guide "To open a PDF file" on page 148.)
    --- Continuation in next Post of this Thread ----

    --- Continuation from previous Post -----
    2 What's changed in PSE 4.0
    2.1 Editing and selecting
    2.1.1 Crop tool
    Freely change image size boundaries while cropping an image. When you're happy with your crop marks,
    click the Commit button , which is now conveniently located at the bottom right corner of the crop border. (See User Guide "To crop an image" on page 240.)
    2.1.2 Paragraph text
    Create paragraph text by dragging a border with the Text tool. The text you enter inside the border
    wraps to remain inside the boundaries. (See User Guide "To add text" on page 329.)
    2.1.3 Quick Fix
    Use the newly enhanced automatic correction options for the most common photo flaws. (See User Guide "To correct color in Quick Fix" on page 207.)
    2.1.4 Easier color management
    Easily get the color you expect when printing. N ew options and improved embedded
    profile support streamline color management. (See User Guide "About color management" on page 236.)
    2.1.5 Advanced camera raw
    Fine tune exposure and lighting by working with the raw data from your digital camera, and
    easily export photos to the universal DNG format. (See User Guide "About camera raw image files" on page 159.)
    2.1.6 Artifact reduction
    Quickly remove noise caused by shooting in low light or with ISO camera settings by using the
    new Remove JPEG Artifacts option in the Noise filter. (See User Guide "Reduce Noise" on page 289.)
    2.2 Sharing and printing
    2.2.1 Multimedia slide shows
    Create feature-rich slide shows with all the new tools and options available in the Slide Show
    Editor:
    a) Gracefully move from one image to another by adding interesting transitions between each slide. You can choose from over 50 transitions, such as dissolves and doors. (See User Guide "To add and edit transitions" on page 352.)
    b) Add text and graphics with the click of a button. (See User Guide "To add text to a slide" on page 348 and "To add clip art graphics to a slide" on page 347.)
    c) Make your slide show feel more like a video by panning and zooming your slides. For instance, you can pan from a face on the left side of an image to a face on the right side of the image. (See User Guide "To set pan and zoom" on page 350.)
    d) Add background music, make the duration of your slides match the duration of your audio, and narrate your slides all with the click of a button. (See User Guide "To add music to a slide show" on page 347 and "To add narration to a slide" on page 350.)
    e) Quickly reorder or edit your slides without leaving the Slide Show Editor. (See User Guide "To reorder slides" on page 346.)
    f) Preview anytime by clicking the Preview button, and then output your slide show by burning a DVD (if you have Adobe ' Premiere' Elements installed), sending it in e-mail, sharing it online, or sending it to your TV. (See User Guide "To output a slide show" on page 354.)
    2.2.2 Photo mail
    Turn plain e-mail into theme-based Photo Mail with enhanced and easier to use captions. (See User Guide "To send a photo using Photo Mail" on page 407.)
    2.2.3 Desktop wallpaper
    Create original desktop wallpaper using multiple photos. (See User Guide "To use photos as desktop
    Wallpaper" on page 367.)
    2.2.4 Creations
    Create your own cards, calendars, and photo albums, and then print them on your printer, upload them
    to the web, or burn them to CD. (See User Guide "About creations" on page 343.)
    2.3 Viewing, tagging, and organizing
    2.3.1 Faster download
    Use the enhanced Photo Downloader to quickly download photos from your digital camera and
    mobile phone, even when Photoshop Elements is not running. (See User Guide "To get photos from a digital camera or card reader" on page 62.)
    2.3.2 Full Screen and Side By Side View
    View your photos in full screen without the clutter of command menus and tools.
    (See User Guide "Viewing photos at full screen or side-by-side" on page 76.)
    2.3.3 Automatic organization and view options
    View your photos as arranged automatically by date, or use the intuitive
    Date View or the enhanced Folder Location view. (See User Guide "To sort files in the Photo Browser" on page 71.)
    2.3.4 Address book
    Import your addresses from Microsoft Outlook address book or vCards. (See User Guide "Using the contact Book" on page 404.)
    2.3.5 Captions
    Add captions to multiple photos at once. Open and edit audio captions by simply clicking the Audio
    icon in thumbnail view in the Photo Browser. (See User Guide "To add captions to files" on page 123 and "To add audio to a photo" on page 124.)
    --- End of Information Copied from the Adobe PSE 4.0 User Guide

  • Wat is the exact differences between clustered table and pooled table

    hi,
       can you tell me ravi...wat is the exact differences between clustered table and pooled table
    with regards//
    anilreddyg

    Hi Anil Reddy
    Pooled Tables, Table Pools, Cluster Tables, and Table Clusters
    These types of tables are not transparent in the sense that they are not legible or manageable directly using the underlying database system tools. They are managed from within the R/3 environment from the ABAP dictionary and also at runtime when they are loaded into application memory.Pool and cluster tables are logical tables. Physically, these logical tables are arranged as records of transparent tables. The pool and cluster tables are grouped together in other tables, which are of the transparent type. The tables that group together pool tables are known as table pools, or just pools; similarly, table clusters, or just
    clusters, are the tables which group cluster tables.Not all operations that can be performed over transparent tables can be executed over pool or cluster tables.
    For instance, you can manage these tables using Open SQL calls from ABAP, but not Native SQL.These tables are meant to be buffered and loaded in memory, because they are commonly used for storing internal control information and other types of data with no external (business) relevance. SAP recommends that tables of pool or cluster type be used exclusively for control information such as
    program parameters, documentation, and so on. Transaction and application data should be stored in transparent tables.
    Table Pools
    From the point of view of the underlying DBMS as from the point of view of the ABAP dictionary, a table pool is a transparent table containing a group of pooled tables which, when created, were assigned to this table pool.
    Field Type Description
    TABNAME CHAR(10) Table name
    VARKEY CHAR(n) Maximum key length n =< 110
    DATALN INT2(5) Length of the VARDATA record returned
    VARDATA RAW(m) Maximum length of the data varies according to DBMS
    Table Clusters
    Similarly to pooled tables, cluster tables are logical tables which, when created, are assigned to a table cluster. Therefore, a table cluster, or just cluster, groups together several tables of type clusters.Several logical rows from different cluster tables are brought together in a single physical record. The records
    from the cluster tables assigned to a cluster are thus stored in a single common table in the database.A cluster contains a transparent cluster key which must be located at the start of the key of all logical cluster tables to be included in the cluster. As well, a cluster contains a long field (VARDATA), which contains the
    data of the cluster tables for this key. If the data does not fit into a field, continuation records are created.
    Field Type Description
    CLKEY1 CHAR(*) First key fields
    CLKEY2 CHAR(*) Second key field
    CLKEYN CHAR(*) nth key field
    PAGENO INT2(5) Number of the next page
    TIMESTMP CHAR(14) Time stamp
    PAGELG INT2(5) Length of the VARDATA record returned
    VARDATA RAW(*) Maximum length of the data section; varies according to database system
    Working with Tables
    The dictionary includes many functions for working with tables. There are five basic operations you can perform on tables: display, create, delete, modify, copy. Please do not confuse displaying a table with displaying the table entries (table contents). In order to display a table, it must previously exist; otherwise the system will display an error message in the status bar. For the following example, the table TABNA is used. To display this table, from the main dictionary screen, enter the table name in the Object name
    input field with the radio button selected next to Tables. Then, click on the Display button at the bottom of the screen, or press the F7 function key, or, alternatively,
    select Dictionary object Display from the menu.
    In this screen, you can see table information such as
    ¨ Table type, shown next to the name of the object. In the example, it is a transparent table.
    ¨ Short text description.
    ¨ Name of the user who made the last change, and the date of the change.
    ¨ Master language.
    ¨ Table status. On the screen, you can see this table is saved and active.
    ¨ Development class. For information on development classes, refer to Chap. 6.
    Delivery class, which sets the maintenance group for the table. It controls how tables will behave during client copy procedures, upgrades, and so forth.¨
    Tab. Maint. Allowed flag, which indicates whether you can generate a screen for maintaining table entries.
    ¨Then, on the lower part of the screen, you can see the table fields with all associated characteristics such as:
    ¨ Field name.
    ¨ Key indicator. When set, this field is the primary key, or part of it.
    ¨ Data element.
    ¨ Basic data type.
    ¨ Length.
    ¨ Check table.
    ¨ Short text, describing the field.
    Additional information about the table can be displayed by selecting the corresponding functions from the menu or directly from the application toolbar, such as keys, indexes, or technical settings
    Standard table:
    The key access to a standard table uses a sequential search. The time required for an access is linearly dependent on the number of entries in the internal table.
    You should usually access a standard table with index operations.
    Sorted table:
    The table is always stored internally sorted by its key. Key access to a sorted table can therefore use a binary search. If the key is not unique, the entry with the lowest index is accessed. The time required for an access is logarithmically dependent on the number of entries in the internal table.
    Index accesses to sorted tables are also allowed. You should usually access a sorted table using its key.
    Hash table:
    The table is internally managed with a hash procedure. All the entries must have a unique key. The time required for a key access is constant, that is it does not depend on the number of entries in the internal table.
    You cannot access a hash table with an index. Accesses must use generic key operations (SORT, LOOP, etc.).
    Index table:
    The table can be a standard table or a sorted table.
    Index access is allowed to such an index table. Index tables can be used to define the type of generic parameters of a FORM (subroutine) or a function module.
    Just have a look at these links:
    http://help.sap.com/saphelp_nw04/helpdata/en/90/8d7304b1af11d194f600a0c929b3c3/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/74/83015785d811d295a800a0c929b3c3/frameset.htm
    Regards
    Sreeni

  • Differences Between Report Painter and Report Writer

    Hi,
    Anyone knows the differences between report painter and report writer?
    Thanks,
    CW

    Hello CW Teo,
    Yes report writer can be used in logistics also. One of the way which I am aware of is described below.
    Flexible analyses allow you to can tailor the way in which key figures are combined and aggregated. This means that it is possible to both provide administrators with detailed information and management with aggregated information.
    Flexible analyses enable easy access to the Report Writer, a user-friendly tool with which you can create reports for various analyses. The Report Writer is integrated in other SAP applications, such as Extended General Ledger and Cost Center Accounting.
    Evaluation structures form the interface to the Report Writer. Evaluation structures consist of characteristics and key figures and are easy to construct.An evaluation structure with the same name exists for each information structure in the standard system.Even the self-defined information structures created in Customizing can be evaluated via the flexible analyses.
    Evaluations:You can create an evaluation on the basis of the evaluation structure.
    To define an evaluation, all you need to do is select the characteristics and key figures you require (pick-up technique).One of the especially useful features here is that you have the option of tailoring the layout of your report to suit your particular requirements. You can also define extra key figures for the reports, which are derived from existing key figures by means of calculation formulas. You can thereby multiply the key figures or divide one key figure by another.
    ============================================================
    In addition to the above you can also edit a report in logistics module with the help of a report writer. below mentioned is the process for it.
    It is now possible to edit your report data using the Report Writer. You can also change the layout of the report. The most important functions of the layout design are summarized below.
    Summation levels:In the report screen, you can use the menu sequence View ->Summation level to specify the number of summation used to calculate total values. All totals that do not lie within the specified interval will be hidden. A summation level corresponds to a hierarchical level (for example, material level). Summation level 1 is the lowest hierarchical level. Summation level 2 is the next level up, and so on. The individual values are on the summation level 0.
    The summation levels can be specified both universally (for the entire report) or locally (for specific blocks of rows). In this case, the local settings overwrite global values.
    Report views:If a report is displayed on the screen, the Report Writer will then set page breaks so that exactly one page fits into the current window. This view will be defined as the standard view. As the Report Writer always processes exactly one page, you can only use the page keys and page icons to page up and down; the scroll bars cannot be used.
    The page view can be determined via Settings-> Page view. The page breaks in the page view correspond to those defined in the report layout.
    Hide and show rows:The function Edit->Hide rows exclude certain preselected areas of your report from the display. You can undo this command with Edit ® Show rows.
    Expanding and collapsing report rows:View-> Hierarchy->Collapse allows you to hide the report rows of the sub-trees that are located underneath. View->Hierarchy ->Expand allows you to undo this command level by level.
    If you want to display all the report rows that were hidden by collapsing the hierarchy or restricting the summation levels, select, View->Hierarchy-> Expand all.
    View->Collapse all allows you to reduced every row block to the highest summation level.
    Texts and Annotations:You can create an annotation for your report.
    Select: Extras->Annotation.
    You branch into the text editor of the Report Writer.
    Via the menu sequence Settings->Texts, you can create and format a title page, the last page, as well as headers and footers using word processing functions.
    For example, you can store variables in the header for the author of the report, the date of the selection or the name of the person who last changed the report.
    Layout parameters:Using the menu sequence Settings->Layout you can specify the page format, display form, rows and columns of the report according to your needs and you can determine the settings for the graphics function. You can make these layout settings with Report->Save settings.
    Hope I had been able to help you to some extent. please assign points as reward.
    Rgds
    Manish

  • What is difference between report programming and dialog programming?

    hi,
    what is difference between report programming and dialog programming? plz provide some example code
    bye

    ABAP programming
    Basically reports are used to read database and represent the results in lists.
    Reports are collections of processing blocks that the system calls depending on events.
    We can use reports to evaluate data from database tables.
    Reports are stand alone programs and controlled by events.
    A report itself never creates events
    steps in report:
    Processing the selection screen
    Reading the database
    Evaluating the data and creating lists
    Outputting a list.
    1st u write simple logics, after that u can enhance the code as step by step.
    http://venus.imp.mx/hilario/Libros/TeachYrslfAbap4/index.htm
    http://help.sap.com/saphelp_47x200/helpdata/en/d1/802cfc454211d189710000e8322d00/frameset.htm
    http://www.sapdev.co.uk/reporting/reportinghome.htm
    Dialog Programming
    Structure of a Dialog Program
    A dialog program consists of the following basic components:
    Screens (dynpros)
    Each dialog in an SAP system is controlled by dynpros. A dynpro (DYnamic PROgram) consists of a screen and its flow logic and controls exactly one dialog step. The flow logic determines which processing takes place before displaying the screen (PBO-Process Before Output) and after receiving the entries the user made on the screen (PAI-Process After Input).
    The screen layout fixed in the Screen Painter determines the positions of input/output fields, text fields, and graphical elements such as radio buttons and checkboxes. In addition, the Menu Painter allows to store menus, icons, pushbuttons, and function keys in one or more GUI statuses. Dynpros and GUI statuses refer to the ABAP/4 program that control the sequence of the dynpros and GUI statuses at runtime.
    ABAP/4 module pool
    Each dynpro refers to exactly one ABAP/4 dialog program. Such a dialog program is also called a module pool, since it consists of interactive modules. The flow logic of a dynpro contains calls of modules from the corresponding module pool. Interactive modules called at the PBO event are used to prepare the screen template in accordance to the context, for example by setting field contents or by suppressing fields from the display that are not needed. Interactive modules called at the PAI event are used to check the user input and to trigger appropriate dialog steps, such as the update task.
    All dynpros to be called from within one transaction refer to a common module pool. The dynpros of a module pool are numbered. By default, the system stores for each dynpro the dynpro to be displayed next. This dynpro sequence or chain can be linear as well as cyclic. From within a dynpro chain, you can even call another dynpro chain and, after processing it, return to the original chain.
    Check this link for basics.
    http://sap.mis.cmich.edu/sap-abap/abap09/index.htm
    Check this link for Dialog Programming/Table Control
    http://www.planetsap.com/Tips_and_Tricks.htm#dialog
    Check this SAP Help for Dialog Program doc.
    http://help.sap.com/saphelp_nw04/helpdata/en/9f/db9cdc35c111d1829f0000e829fbfe/content.htm
    Check this SAP Help link for Subscreens.
    http://help.sap.com/saphelp_nw70/helpdata/en/9f/dbabfe35c111d1829f0000e829fbfe/content.htm
    Check this link for subscreen demo program.
    http://abapcode.blogspot.com/2007/05/demo-program-to-create-subscreen-in.html
    Also check this link too.
    http://abapcode.blogspot.com/2007/06/dialog-programming-faq.html
    http://help.sap.com/saphelp_nw04/helpdata/en/9f/db9cdc35c111d1829f0000e829fbfe/frameset.htm
    http://sap.mis.cmich.edu/sap-abap/abap09/sld004.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/52/670ba2439b11d1896f0000e8322d00/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/52/670c17439b11d1896f0000e8322d00/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/52/670c17439b11d1896f0000e8322d00/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/9f/db9ccf35c111d1829f0000e829fbfe/frameset.htm
    http://abapprogramming.blogspot.com/

  • What is the difference between interactive report and alv interactive repor

    what is the difference between interactive report and alv interactive report
    could u plz explain clearly.

    Hi Rajesh,
    interactive report or alv interactive report , both are same but except the viewer, Abap List Viewer (ALV).
    Here in i am placing a sample simple ALV Interactive report.
    Just double click on the customer number to go to the next screen.
    *& Report  ZKAL_ALV_INTERACTIVE_1                                      *
    REPORT  ZKAL_ALV_INTERACTIVE_1                  .
    TYPE-POOLS: SLIS.
      TYPES: BEGIN OF TY_KNA1,
              KUNNR TYPE KUNNR,
              NAME1 TYPE NAME1,
              ORT01 TYPE ORT01,
            END OF TY_KNA1.
      TYPES: BEGIN OF TY_VBAK,
              VBELN TYPE VBELN,
              ERNAM TYPE ERNAM,
              ERDAT TYPE ERDAT,
              NETWR TYPE NETWR,
              WAERK TYPE WAERK,
             END OF TY_VBAK.
    &--WORK AREA & TABLE DECLARATION--
      DATA: W_KNA1 TYPE TY_KNA1.
      DATA: T_KNA1 TYPE STANDARD TABLE OF TY_KNA1 INITIAL SIZE 1.
      DATA: W_VBAK TYPE TY_VBAK.
      DATA: T_VBAK TYPE STANDARD TABLE OF TY_VBAK INITIAL SIZE 1.
    &--FIELDCAT TABLE & WORK AREA--
      DATA: W_FCAT TYPE SLIS_FIELDCAT_ALV.
      DATA: T_FCAT TYPE SLIS_T_FIELDCAT_ALV.
      DATA: W_FCAT1 TYPE SLIS_FIELDCAT_ALV.
      DATA: T_FCAT1 TYPE SLIS_T_FIELDCAT_ALV.
    &--EVENT TABLE AND WORK AREA--
      DATA: W_EVENTS TYPE SLIS_ALV_EVENT.
      DATA: T_EVENTS TYPE SLIS_T_EVENT.
      DATA: W_EVENTS1 TYPE SLIS_ALV_EVENT.
      DATA: T_EVENTS1 TYPE SLIS_T_EVENT.
    &--COMMENT TABLE & WORK AREA--
      DATA: W_COMMENT TYPE SLIS_LISTHEADER.
      DATA: T_COMMENT TYPE SLIS_T_LISTHEADER.
      DATA: W_COMMENT1 TYPE SLIS_LISTHEADER.
      DATA: T_COMMENT1 TYPE SLIS_T_LISTHEADER.
    &----APPENDING FCAT -
      W_FCAT-COL_POS = 1.
      W_FCAT-FIELDNAME = 'KUNNR'.
      W_FCAT-SELTEXT_M = 'CUST. NO'.
      W_FCAT-HOTSPOT = 'X'.            "HOT SPOT HAND SYMBOL
      W_FCAT-EMPHASIZE = 'C119'.       "FOR COLORING THE COLUMN 1
      APPEND W_FCAT TO T_FCAT.
      CLEAR W_FCAT.
      W_FCAT-COL_POS = 2.
      W_FCAT-FIELDNAME = 'NAME1'.
      W_FCAT-SELTEXT_M = 'CUST. NAME'.
      APPEND W_FCAT TO T_FCAT.
      W_FCAT-COL_POS = 3.
      W_FCAT-FIELDNAME = 'ORT01'.
      W_FCAT-SELTEXT_M = 'CITY'.
      APPEND W_FCAT TO T_FCAT.
      W_FCAT1-COL_POS = 1.
      W_FCAT1-FIELDNAME = 'VBELN'.
      W_FCAT1-SELTEXT_M = 'ORDER NO'.
      W_FCAT1-EMPHASIZE = 'C519'.
      APPEND W_FCAT1 TO T_FCAT1.
      CLEAR W_FCAT.
      W_FCAT1-COL_POS = 2.
      W_FCAT1-FIELDNAME = 'ERNAM'.
      W_FCAT1-SELTEXT_M = 'NAME OF PARTY'.
      APPEND W_FCAT1 TO T_FCAT1.
      W_FCAT1-COL_POS = 3.
      W_FCAT1-FIELDNAME = 'ERDAT'.
      W_FCAT1-SELTEXT_M = 'DATE'.
      APPEND W_FCAT1 TO T_FCAT1.
      W_FCAT1-COL_POS = 4.
      W_FCAT1-FIELDNAME = 'NETWR'.
      W_FCAT1-SELTEXT_M = 'ORDER VALUE'.
      APPEND W_FCAT1 TO T_FCAT1.
      W_FCAT1-COL_POS = 5.
      W_FCAT1-FIELDNAME = 'WAERK'.
      W_FCAT1-SELTEXT_M = 'CURRENCY'.
      APPEND W_FCAT1 TO T_FCAT1.
    &--APPEND COMMENTRY--
      W_COMMENT-TYP = 'H'.
      W_COMMENT-INFO = 'CUSTOMER DETAILS'.
      APPEND W_COMMENT TO T_COMMENT.
      CLEAR W_COMMENT.
    &--APPEND EVENTS TABLE--
      W_EVENTS-NAME = 'TOP_OF_PAGE'.
      W_EVENTS-FORM = 'TOPPAGE'.
      APPEND W_EVENTS TO T_EVENTS.
      W_EVENTS-NAME = 'USER_COMMAND'.
      W_EVENTS-FORM = 'SUB2'.
      APPEND W_EVENTS TO T_EVENTS.
      W_EVENTS1-NAME = 'TOP_OF_PAGE'.
      W_EVENTS1-FORM = 'TOPPAGE1'.
      APPEND W_EVENTS1 TO T_EVENTS1.
      CLEAR W_EVENTS1.
      W_EVENTS1-NAME = 'USER_COMMAND'.
      W_EVENTS1-FORM = 'SUB3'.
      APPEND W_EVENTS1 TO T_EVENTS1.
      SELECT-OPTIONS: CUSTNO FOR W_KNA1-KUNNR.
      SELECT KUNNR
             NAME1
             ORT01 FROM KNA1 INTO TABLE T_KNA1
             WHERE KUNNR IN CUSTNO.
    CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
    EXPORTING
       I_CALLBACK_PROGRAM                = 'ZKAL_ALV_INTERACTIVE_12'
       I_BACKGROUND_ID                   = 'BIKE'
       I_GRID_TITLE                      = 'CUSTOMER DETAILS'
       IT_FIELDCAT                       = T_FCAT
       IT_EVENTS                         = T_EVENTS
      TABLES
        T_OUTTAB                          = T_KNA1  .
      FORM TOPPAGE.
      CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
        EXPORTING
          IT_LIST_COMMENTARY       = T_COMMENT
         I_LOGO                   = 'LOGO_ALV'.
      ENDFORM.  "END OF TOPPAGE SUB.
      FORM SUB2 USING UCOMM LIKE SY-UCOMM FIELDS1 TYPE SLIS_SELFIELD.
      READ TABLE T_KNA1 INTO W_KNA1 INDEX FIELDS1-TABINDEX.
      SELECT VBELN
             ERNAM
             ERDAT
             NETWR
             WAERK
                   FROM VBAK
                   INTO TABLE T_VBAK
                   WHERE KUNNR = W_KNA1-KUNNR.
    CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
    EXPORTING
       I_CALLBACK_PROGRAM                = 'ZKAL_ALV_INTERACTIVE_12'
       I_BACKGROUND_ID                   = 'KALEEM'
       I_GRID_TITLE                      = 'LIST OF ORDERS'
       IT_FIELDCAT                       = T_FCAT1
       IT_EVENTS                         = T_EVENTS1
      TABLES
        T_OUTTAB                          = T_VBAK.
    ENDFORM.    "END OF SUB2.
    FORM TOPPAGE1.
    &--APPEND COMMENTRYOF SECONDRY SCREEN--
      W_COMMENT1-TYP = 'H'.
      W_COMMENT1-INFO = 'LIST OF ORDERS'.
      APPEND W_COMMENT1 TO T_COMMENT1.
      W_COMMENT1-TYP = 'S'.
      W_COMMENT1-KEY = 'CUSTOMER'.
      W_COMMENT1-INFO = W_KNA1-KUNNR.
      APPEND W_COMMENT1 TO T_COMMENT1.
      CLEAR W_COMMENT.
      W_COMMENT1-TYP = 'A'.
      W_COMMENT1-INFO = W_KNA1-NAME1.
      APPEND W_COMMENT1 TO T_COMMENT1.
      CLEAR W_COMMENT1.
      CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
        EXPORTING
          IT_LIST_COMMENTARY       = T_COMMENT1
         I_LOGO                   = 'LOGO_ALV'
    REFRESH T_COMMENT1.
    ENDFORM.    "END OF TOPPAGE1
      FORM SUB3 USING UCOMM LIKE SY-UCOMM FIELDS1 TYPE SLIS_SELFIELD.
        READ TABLE T_VBAK INTO W_VBAK INDEX FIELDS1-TABINDEX.
    SET PARAMETER ID 'AUN' FIELD W_VBAK-VBELN.
    CALL TRANSACTION 'VA02' AND SKIP FIRST SCREEN.
      ENDFORM.
    U can also find some of the useful codes on WIKI-SDN.
    Reward helpful Answers.
    Regds,
    Kaleem.

  • Quality difference between S-video and RCA

    Can someone tell me what's the difference (in quality) between S-video out and RCA out?
    I'm using RCA out because with s-video, the image shows up in black and white on my TV.
    It would help to know I'm not loosing too much quality this way...
    Regards everyone.

    pauliewog is speechless  
    But what Robi says is true!
    The various forms of (analogue) signal transfer are, in descending order of quality:
    RGB - The Red, Green and Blue signals are generated by the PC (say), and connected by separate wires to ultimately control the Red, Green and Blue electron guns of the display monitor/TV set. The standard 15-pin "VGA" connector is RGB (plus H and V synchronising pulses).
    YUV - Also called Component, and YCrCb, as found on DVD players. The Y is the luminance, or Black-and-White component, while the Cr and Cb are the Differences between the Y and the Red and Blue signals respectively. Usually, the Y signal has higher bandwidth than the Cr and Cb signals (twice as many Y samples as Cr and Cb samples on the DVD). Still needs wires, but the Sync is added to the Y signal.
    Y/C - aka S-Video. The Y is as above, but the Cr and Cb signals are used to modulate a subcarrier (3.579545MHz for NTSC, 4.43361875MHz for PAL), with one of the signals effectively at 90 degrees to the other - the C signal. The bandwidths of the colour difference signals need to be bandwidth limited to about 1/3 of the subcarrier frequency (about 1.7MHz for PAL from memory), compared to the Y bandwidth of 5MHz for broadcast television. In PAL, the phase of one of the signals is inverted every other line (PAL = Phase Alternating Line, aka Peace At Last). Transmission errors which result in green faces and purple trees in NTSC (National Television Standards Commitee, aka Never Twice the Same Colour) tend to desaturate the colours instead.
    CVBS, aka Composite Video (also RCA, named after the company that developed the type of connector used, which is typically yellow for video). The Y and C (and sync) signals are combined one one wire. The TV has a harder job of separating them back to RGB  :(
    RF (Radio Frequency). The CVBS signal is modulated onto an RF carrier, which could be anywhere between about 45MHz and about 1000MHz (not counting satellite distribution), so that it looks the same as a broadcast TV station to a TV set, and connects via a single cable to the antenna socket of a TV set. So first the TV has to demodulate the signal back to CVBS, before separating the Y and C, then separating the C into Cr and Cb and putting into a matrix with the Y to get RGB back. Nevertheless, this is a useful technique for distributing a signal to a lot of TV sets over a reasonably large area. It is also the only method that works with old TVs without A/V inputs - which is why game consoles used to come with an RF Modulator (aka RF Converter) as standard.
    The above methods are also in descending order of signal bandwidth, which restricts the available resolution, or the finest horizontal detail (especially colour detail). Generally, 800x600 is about as good a resolution as you can expect to get on a TV display without resorting to special enhancing techniques.
    The above is probably a lot more detail than you need, but is still a fairly superficial explanation. But study it up, the test is next Monday at 9am  :D
    Cheers

  • Differences between Procedural ABAP and OOPs ABAP

    Hi Friends,
    Can any one explain the differences between Procedural ABAP and OOPs ABAP in brief ? pls explain the most important ( atleast 3 or 4 points ). pls don't give me any other links, i will appreciate for good responses... and will be awarded with full points...
    Thanks and Regards
    Vijaya

    Hi
    Core ABAP (procedural) works with Event driven, subroutine driven one
    OOPS ABAP works on the OOPS concepts like Inheritance, polymorphism,abstraction and encapsulation.
    see the doc
    ABAP is one of many application-specific fourth-generation languages (4GLs) first developed in the 1980s. It was originally the report language for SAP R/2, a platform that enabled large corporations to build mainframe business applications for materials management and financial and management accounting. ABAP used to be an abbreviation of Allgemeiner Berichtsaufbereitungsprozessor, the German meaning of "generic report preparation processor", but was later renamed to Advanced Business Application Programming. ABAP was one of the first languages to include the concept of Logical Databases (LDBs), which provides a high level of abstraction from the basic database level.
    The ABAP programming language was originally used by SAP developers to develop the SAP R/3 platform. It was also intended to be used by SAP customers to enhance SAP applications – customers can develop custom reports and interfaces with ABAP programming. The language is fairly easy to learn for programmers but it is not a tool for direct use by non-programmers. Good programming skills, including knowledge of relational database design and preferably also of object-oriented concepts, are required to create ABAP programs.
    ABAP remains the language for creating programs for the client-server R/3 system, which SAP first released in 1992. As computer hardware evolved through the 1990s, more and more of SAP's applications and systems were written in ABAP. By 2001, all but the most basic functions were written in ABAP. In 1999, SAP released an object-oriented extension to ABAP called ABAP Objects, along with R/3 release 4.6.
    SAP's most recent development platform, NetWeaver, supports both ABAP and Java.
    Implementation
    Where does the ABAP Program Run?
    All ABAP programs reside inside the SAP database. They are not stored in separate external files like Java or C++ programs. In the database all ABAP code exists in two forms: source code, which can be viewed and edited with the ABAP workbench, and "compiled" code ("generated" code is the more correct technical term), which is loaded and interpreted by the ABAP runtime system. Code generation happens implicitly when a unit of ABAP code is first invoked. If the source code is changed later or if one of the data objects accessed by the program has changed (e.g. fields were added to a database table), then the code is automatically regenerated.
    ABAP programs run in the SAP application server, under control of the runtime system, which is part of the SAP kernel. The runtime system is responsible for processing ABAP statements, controlling the flow logic of screens and responding to events (such as a user clicking on a screen button). A key component of the ABAP runtime system is the Database Interface, which turns database-independent ABAP statements ("Open SQL") into statements understood by the underlying DBMS ("Native SQL"). The database interface handles all the communication with the relational database on behalf of ABAP programs; it also contains extra features such as buffering of frequently accessed data in the local memory of the application server.
    Basis
    Basis sits between ABAP/4 and Operating system.Basis is like an operating system for R/3. It sits between the ABAP/4 code and the computer's operating system. SAP likes to call it middleware because it sits in the middle, between ABAP/4 and the operating system. Basis sits between ABAP/4 and the operating system. ABAP/4 cannot run directly on an operating system. It requires a set of programs (collectively called Basis) to load, interpret, and buffer its input and output. Basis, in some respects, is like the Windows environment. Windows starts up, and while running it provides an environment in which Windows programs can run. Without Windows, programs written for the Windows environment cannot run. Basis is to ABAP/4 programs as Windows is to Windows programs. Basis provides the runtime environment for ABAP/4 programs. Without Basis, ABAP/4 programs cannot run. When the operator starts up R/3, you can think of him as starting up Basis. Basis is a collection of R/3 system programs that present you with an interface. Using this interface the user can start ABAP/4 programs. To install Basis, an installer runs the program r3inst at the command-prompt level of the operating system. Like most installs, this creates a directory structure and copies a set of executables into it. These executables taken together as a unit form Basis.
    To start up the R/3 system, the operator enters the startsap command. The Basis executables start up and stay running, accepting requests from the user to run ABAP/4 programs.
    ABAP/4 programs run within the protective Basis environment; they are not executables that run on the operating system. Instead, Basis reads ABAP/4 code and interprets it into operating system instructions. ABAP/4 programs do not access operating system functions directly. Instead, they use Basis functions to perform file I/O and display data in windows. This level of isolation from the operating system enables ABAP/4 programs to be ported without modification to any system that supports R/3. This buffering is built right into the ABAP/4 language itself and is actually totally transparent to the programmer.
    Basis makes ABAP/4 programs portable. The platforms that R/3 can run on are shown in Table. For example, if you write an ABAP/4 program on Digital UNIX with an Informix database and an OSF/Motif interface, that same program should run without modification on a Windows NT machine with an Oracle database and a Windows 95 interface. Or, it could run on an AS/400 with a DB2 database using OS/2 as the front-end.
    SAP also provides a suite of tools for administering the Basis system. These tools perform tasks such as system performance monitoring, configuration, and system maintenance. To access the Basis administration tools from the main menu, choose the path Tools->Administration.
    Platforms and Databases Supported by R/3
    Operating Systems Supported Hardware Supported Front-Ends Supported Databases
    AIX SINIX IBM SNI SUN Win 3.1/95/NT DB2 for AIX
    SOLARIS HP-UX Digital HP OSF/Motif Informix-Online
    Digital-UNIX Bull OS/2 Oracle 7.1
    Windows NT AT&T Compaq Win 3.1/95/NT Oracle 7.1
    Bull/Zenith OSF/Motif SQL Server 6.0
    HP (Intel) SNI OS/2 ADABAS D
    OS/400 AS/400 Win95 OS/2 DB2/400
    SAP Systems and Landscapes
    All SAP data exists and all SAP software runs in the context of an SAP system. A system consists of a central relational database and one or more application servers ("instances") accessing the data and programs in this database. A SAP system contains at least one instance but may contain more, mostly for reasons of sizing and performance. In a system with multiple instances, load balancing mechanisms ensure that the load is spread evenly over the available application servers.
    Installations of the Web Application Server (landscapes) typically consist of three systems: one for development, one for testing and quality assurance, and one for production. The landscape may contain more systems, e.g. separate systems for unit testing and pre-production testing, or it may contain fewer, e.g. only development and production, without separate QA; nevertheless three is the most common configuration. ABAP programs are created and undergo first testing in the development system. Afterwards they are distributed to the other systems in the landscape. These actions take place under control of the Change and Transport System (CTS), which is responsible for concurrency control (e.g. preventing two developers from changing the same code at the same time), version management and deployment of programs on the QA and production systems.
    The Web Application Server consists of three layers: the database layer, the application layer and the presentation layer. These layers may run on the same or on different physical machines. The database layer contains the relational database and the database software. The application layer contains the instance or instances of the system. All application processes, including the business transactions and the ABAP development, run on the application layer. The presentation layer handles the interaction with users of the system. Online access to ABAP application servers can go via a proprietary graphical interface, the SAPGUI, or via a Web browser.
    Transactions
    We call an execution of an ABAP program using a transaction code a transaction. There are dialog, report, parameter, variant, and as of release 6.10, OO transactions. A transaction is started by entering the transaction code in the input field on the standard toolbar, or by means of the ABAP statements CALL TRANSACTION or LEAVE TO TRANSACTION. Transaction codes can also be linked to screen elements or menu entries. Selecting such an element will start the transaction.
    A transaction code is simply a twenty-character name connected with a Dynpro, another transaction code, or, as of release 6.10, a method of an ABAP program. Transaction codes linked with Dynpros are possible for executable programs, module pools, and function groups. Parameter transactions and variant transactions are linked with other transaction codes. Transaction codes that are linked with methods are allowed for all program types that can contain methods. Transaction codes are maintained in transaction SE93.
    So, a transaction is nothing more than the SAP way of program execution—but why is it called “transaction”? ABAP is a language for business applications and the most important features of business applications were and still are are transactions. Since in the early days of SAP, the execution of a program often meant the same thing as carrying out a business transaction, the terms transaction and transaction code were chosen for program execution. But never mix up the technical meaning of a transaction with business transactions. For business transactions, it is the term LUW (Logical Unit of Work) that counts. And during one transaction (program execution), there can be many different LUW’s.
    Let’s have a look at the different kind of transactions:
    Dialog Transaction
    These are the most common kind of transactions. The transaction code of a dialog transaction is linked to a Dynpro of an ABAP program. When the transaction is called, the respective program is loaded and the Dynpro is called. Therefore, a dialog transaction calls a Dynpro sequence rather than a program. Only during the execution of the Dynpro flow logic are the dialog modules of the ABAP program itself are called. The program flow can differ from execution to execution. You can even assign different dialog transaction codes to one program.
    Parameter Transaction
    In the definition of a parameter transaction code, a dialog transaction is linked with parameters. When you call a parameter transaction, the input fields of the initial Dynpro screen of the dialog transaction are filled with parameters. The display of the initial screen can be inhibited by specifying all mandatory input fields as parameters of the transaction.
    Variant Transaction
    In the definition of a variant transaction code, a dialog transaction is linked with a transaction variant. When a variant transaction is accessed, the dialog transaction is called and executed with the transaction variant. In transaction variants, you can assign default values to the input fields on several Dynpro screens in a transaction, change the attributes of screen elements, and hide entire screens. Transaction variants are maintained in transaction SHD0.
    Report Transaction
    A report transaction is the transaction code wrapping for starting the reporting process. The transaction code of a report transaction must be linked with the selection screen of an executable program. When you execute a report transaction, the runtime environment internally executes the ABAP statement SUBMIT—more to come on that.
    OO Transaction
    A new kind of transaction as of release 6.10. The transaction code of an OO transaction is linked with a method of a local or global class. When the transaction is called, the corresponding program is loaded, for instance methods an object of the class is generated and the method is executed.
    Types of ABAP programs
    In ABAP, there are two different types of programs:
    Report programs(Executable pools)
    A Sample ReportReport programs AKA Executable pools follow a relatively simple programming model whereby a user optionally enters a set of parameters (e.g. a selection over a subset of data) and the program then uses the input parameters to produce a report in the form of an interactive list. The output from the report program is interactive because it is not a passive display; instead it enables the user, through ABAP language constructs, to obtain a more detailed view on specific data records via drill-down functions, or to invoke further processing through menu commands, for instance to sort the data in a different way or to filter the data according to selection criteria. This method of presenting reports has great advantages for users who must deal with large quantities of information and must also have the ability to examine this information in highly flexible ways, without being constrained by the rigid formatting or unmanageable size of "listing-like" reports. The ease with which such interactive reports can be developed is one of the most striking features of the ABAP language.
    The term "report" is somewhat misleading in the sense that it is also possible to create report programs that modify the data in the underlying database instead of simply reading it.
    A customized screen created using Screen Painter,which is one of the tool available in ABAP workbench(T-code = SE51).
    Online programs
    Online programs (also called module pools) do not produce lists. These programs define more complex patterns of user interaction using a collection of screens. The term “screen” refers to the actual, physical image that the users sees. Each screen also has a “flow logic”; this refers to the ABAP code invoked by the screens, i.e. the logic that initializes screens, responds to a user’s requests and controls the sequence between the screens of a module pool. Each screen has its own Flow Logic, which is divided into a "PBO" (Process Before Output) and "PAI" (Process After Input) section. In SAP documentation the term “dynpro” (dynamic program) refers to the combination of the screen and its Flow Logic.
    Online programs are not invoked directly by their name, but are associated with a transaction code. Users can then invoke them through customizable, role-dependent, transaction menus.
    Apart from reports and online programs, it is also possible to develop sharable code units such as class libraries, function libraries and subroutine pools.
    Subroutine Pools
    Subroutine pools, as the name implies, were created to contain selections of subroutines that can be called externally from other programs. Before release 6.10, this was the only way subroutine pools could be used. But besides subroutines, subroutine pools can also contain local classes and interfaces. As of release 6.10, you can connect transaction codes to methods. Therefore, you can now also call subroutine pools via transaction codes. This is the closest to a Java program you can get in ABAP: a subroutine pool with a class containing a method – say – main connected to a transaction code!
    Type Pools
    Type pools are the precursors to general type definitions in the ABAP Dictionary. Before release 4.0, only elementary data types and flat structures could be defined in the ABAP Dictionary. All other types that should’ve been generally available had to be defined with TYPES in type pools. As of release 4.0, type pools were only necessary for constants. As of release 6.40, constants can be declared in the public sections of global classes and type pools can be replaced by global classes.
    Class Pools
    Class pools serve as containers for exactly one global class. Besides the global class, they can contain global types and local classes/interfaces to be used in the global class. A class pool is loaded into memory by using one of its components. For example, a public method can be called from any ABAP program or via a transaction code connected to the method. You maintain class pools in the class builder.
    Interface Pools
    Interface pools serve as containers for exactly one global interface—nothing more and nothing less. You use an interface pool by implementing its interface in classes and by creating reference variables with the type of its interface. You maintain interface pools in the class builder.
    ABAP Workbench
    The ABAP Workbench contains different tools for editing Repository objects. These tools provide you with a wide range of assistance that covers the entire software development cycle. The most important tools for creating and editing Repository objects are:
    ABAP Editor for writing and editing program code
    ABAP Dictionary for processing database table definitions and retrieving global types
    Menu Painter for designing the user interface (menu bar, standard toolbar, application toolbar, function key assignment)
    Screen Painter for designing screens (dynamic programs) for user dialogs
    Function Builder for displaying and processing function modules (routines with defined interfaces that are available throughout the system)
    Class Builder for displaying and processing ABAP Objects classes
    The ABAP Dictionary
    Enforces data integrity
    Manages data definitions without redundancy
    Is tightly integrated with the rest of the ABAP/4 Development Workbench.
    Enforcing data integrity is the process of ensuring that data entered into the system is logical, complete, and consistent. When data integrity rules are defined in the ABAP/4 Dictionary, the system automatically prevents the entry of invalid data. Defining the data integrity rules at the dictionary level means they only have to be defined once, rather than in each program that accesses that data.
    The following are examples of data lacking integrity:
    A date field with a month value of 13
    An order assigned to a customer number that doesn’t exist
    An order not assigned to a customer
    Managing data definitions without redundancy is the process of linking similar information to the same data definition. For example, a customer database is likely to contain a customer’s ID number in several places. The ABAP Dictionary provides the capability of defining the characteristics of a customer ID number in only one place. That central definition then can be used for each instance of a customer ID number.
    The ABAP Dictionary’s integration with the rest of the development environment enables ABAP programs to automatically recognize the names and characteristics of dictionary objects.
    Additionally, the system provides easy navigation between development objects and dictionary definitions. For example, as a programmer, you can double-click on the name of a dictionary object in your program code, and the system will take you directly to the definition of that object in the ABAP/4 Dictionary.
    When a dictionary object is changed, a program that references the changed object will automatically reference the new version the next time the program runs. Because ABAP is interpreted, it is not necessary to recompile programs that reference changed dictionary objects.
    ABAP Syntax
    The syntax of the ABAP programming language consists of the following elements:
    Statements
    An ABAP program consists of individual ABAP statements. Each statement begins with a keyword and ends with a period.
    "Hello World" PROGRAM
    WRITE 'Hello World'.
    This example contains two statements, one on each line. The keywords are PROGRAM and WRITE. The program displays a list on the screen. In this case, the list consists of the line "My First Program".
    The keyword determines the category of the statement. For an overview of the different categories, refer to ABAP Statements.
    Formatting ABAP Statements
    ABAP has no format restrictions. You can enter statements in any format, so a statement can be indented, you can write several statements on one line, or spread a single statement over several lines.
    You must separate words within a statement with at least one space. The system also interprets the end of line marker as a space.
    The program fragment
    PROGRAM TEST.
    WRITE 'This is a statement'.
    could also be written as follows:
    PROGRAM TEST. WRITE 'This is a statement'.
    or as follows:
    PROGRAM
    TEST.
    WRITE
    'This is a statement'.
    Use this free formatting to make your programs easier to understand.
    Special Case: Text Literals
    Text literals are sequences of alphanumeric characters in the program code that are enclosed in quotation marks. If a text literal in an ABAP statement extends across more than one line, the following difficulties can occur:
    All spaces between the quotation marks are interpreted as belonging to the text literal. Letters in text literals in a line that is not concluded with quotation marks are interpreted by the editor as uppercase. If you want to enter text literals that do not fit into a single line, you can use the ‘&’ character to combine a succession of text literals into a single one.
    The program fragment
    PROGRAM TEST.
    WRITE 'This
    is
    a statement'.
    inserts all spaces between the quotation marks into the literal, and converts the letters to uppercase.
    This program fragment
    PROGRAM TEST.
    WRITE 'This' &
    ' is ' &
    'a statement'.
    combines three text literals into one.
    Chained Statements
    The ABAP programming language allows you to concatenate consecutive statements with an identical first part into a chain statement.
    To concatenate a sequence of separate statements, write the identical part only once and place a colon ( after it. After the colon, write the remaining parts of the individual statements, separating them with commas. Ensure that you place a period (.) after the last part to inform the system where the chain ends.
    Statement sequence:
    WRITE SPFLI-CITYFROM.
    WRITE SPFLI-CITYTO.
    WRITE SPFLI-AIRPTO.
    Chain statement:
    WRITE: SPFLI-CITYFROM, SPFLI-CITYTO, SPFLI-AIRPTO.
    In the chain, a colon separates the beginning of the statement from the variable parts. After the colon or commas, you can insert any number of spaces.
    You could, for example, write the same statement like this:
    WRITE: SPFLI-CITYFROM,
    SPFLI-CITYTO,
    SPFLI-AIRPTO.
    In a chain statement, the first part (before the colon) is not limited to the keyword of the statements.
    Statement sequence:
    SUM = SUM + 1.
    SUM = SUM + 2.
    SUM = SUM + 3.
    SUM = SUM + 4.
    Chain statement:
    SUM = SUM + : 1, 2, 3, 4.
    Comments
    Comments are texts that you can write between the statements of your ABAP program to explain their purpose to a reader. Comments are distinguished by the preceding signs * (at the beginning of a line) and " (at any position in a line). If you want the entire line to be a comment, enter an asterisk (*) at the beginning of the line. The system then ignores the entire line when it generates the program. If you want part of a line to be a comment, enter a double quotation mark (") before the comment. The system interprets comments indicated by double quotation marks as spaces.
    PROGRAM SAPMTEST *
    WRITTEN BY KARL BYTE, 06/27/1995 *
    LAST CHANGED BY RITA DIGIT, 10/01/1995 *
    TASK: DEMONSTRATION *
    PROGRAM SAPMTEST.
    DECLARATIONS *
    DATA: FLAG " GLOBAL FLAG
    NUMBER TYPE I " COUNTER
    PROCESSING BLOCKS *
    Advantages of ABAP over Contemporary languages
    ABAP OBJECTS
    Object orientation in ABAP is an extension of the ABAP language that makes available the advantages of object-oriented programming, such as encapsulation, interfaces, and inheritance. This helps to simplify applications and make them more controllable.
    ABAP Objects is fully compatible with the existing language, so you can use existing statements and modularization units in programs that use ABAP Objects, and can also use ABAP Objects in existing ABAP programs.
    ABAP Statements – an Overview
    The first element of an ABAP statement is the ABAP keyword. This determines the category of the statement. The different statement categories are as follows:
    Declarative Statements
    These statements define data types or declare data objects which are used by the other statements in a program or routine. The collected declarative statements in a program or routine make up its declaration part.
    Examples of declarative keywords:
    TYPES, DATA, TABLES
    Modularization Statements
    These statements define the processing blocks in an ABAP program.
    The modularization keywords can be further divided into:
    · Defining keywords
    You use statements containing these keywords to define subroutines, function modules, dialog modules and methods. You conclude these processing blocks using the END statements.
    Examples of definitive keywords:
    METHOD ... ENDMETHOD, FUNCTION ... ENDFUNCTION, MODULE ... ENDMODULE.
    · Event keywords
    You use statements containing these keywords to define event blocks. There are no special statements to conclude processing blocks - they end when the next processing block is introduced.
    Examples of event key words:
    AT SELECTION SCREEN, START-OF-SELECTION, AT USER-COMMAND
    Control Statements
    You use these statements to control the flow of an ABAP program within a processing block according to certain conditions.
    Examples of control keywords:
    IF, WHILE, CASE
    Call Statements
    You use these statements to call processing blocks that you have already defined using modularization statements. The blocks you call can either be in the same ABAP program or in a different program.
    Examples of call keywords:
    CALL METHOD, CALL TRANSACTION, SUBMIT, LEAVE TO
    Operational Statements These keywords process the data that you have defined using declarative statements.
    Examples of operational keywords:
    MOVE, ADD
    Unique Concept of Internal Table in ABAP
    Internal tables provide a means of taking data from a fixed structure and storing it in working memory in ABAP. The data is stored line by line in memory, and each line has the same structure. In ABAP, internal tables fulfill the function of arrays. Since they are dynamic data objects, they save the programmer the task of dynamic memory management in his or her programs. You should use internal tables whenever you want to process a dataset with a fixed structure within a program. A particularly important use for internal tables is for storing and formatting data from a database table within a program. They are also a good way of including very complicated data structures in an ABAP program.
    Like all elements in the ABAP type concept, internal tables can exist both as data types and as data objects A data type is the abstract description of an internal table, either in a program or centrally in the ABAP Dictionary, that you use to create a concrete data object. The data type is also an attribute of an existing data object.
    Internal Tables as Data Types
    Internal tables and structures are the two structured data types in ABAP. The data type of an internal table is fully specified by its line type, key, and table type.
    Line type
    The line type of an internal table can be any data type. The data type of an internal table is normally a structure. Each component of the structure is a column in the internal table. However, the line type may also be elementary or another internal table.
    Key
    The key identifies table rows. There are two kinds of key for internal tables - the standard key and a user-defined key. You can specify whether the key should be UNIQUE or NON-UNIQUE. Internal tables with a unique key cannot contain duplicate entries. The uniqueness depends on the table access method.
    If a table has a structured line type, its default key consists of all of its non-numerical columns that are not references or themselves internal tables. If a table has an elementary line type, the default key is the entire line. The default key of an internal table whose line type is an internal table, the default key is empty.
    The user-defined key can contain any columns of the internal table that are not references or themselves internal tables. Internal tables with a user-defined key are called key tables. When you define the key, the sequence of the key fields is significant. You should remember this, for example, if you intend to sort the table according to the key.
    Table type
    The table type determines how ABAP will access individual table entries. Internal tables can be divided into three types:
    Standard tables have an internal linear index. From a particular size upwards, the indexes of internal tables are administered as trees. In this case, the index administration overhead increases in logarithmic and not linear relation to the number of lines. The system can access records either by using the table index or the key. The response time for key access is proportional to the number of entries in the table. The key of a standard table is always non-unique. You cannot specify a unique key. This means that standard tables can always be filled very quickly, since the system does not have to check whether there are already existing entries.
    Sorted tables are always saved sorted by the key. They also have an internal index. The system can access records either by using the table index or the key. The response time for key access is logarithmically proportional to the number of table entries, since the system uses a binary search. The key of a sorted table can be either unique or non-unique. When you define the table, you must specify whether the key is to be unique or not. Standard tables and sorted tables are known generically as index tables.
    Hashed tables have no linear index. You can only access a hashed table using its key. The response time is independent of the number of table entries, and is constant, since the system access the table entries using a hash algorithm. The key of a hashed table must be unique. When you define the table, you must specify the key as UNIQUE.
    Generic Internal Tables
    Unlike other local data types in programs, you do not have to specify the data type of an internal table fully. Instead, you can specify a generic construction, that is, the key or key and line type of an internal table data type may remain unspecified. You can use generic internal tables to specify the types of field symbols and the interface parameters of procedures . You cannot use them to declare data objects.
    Internal Tables as Dynamic Data Objects
    Data objects that are defined either with the data type of an internal table, or directly as an internal table, are always fully defined in respect of their line type, key and access method. However, the number of lines is not fixed. Thus internal tables are dynamic data objects, since they can contain any number of lines of a particular type. The only restriction on the number of lines an internal table may contain are the limits of your system installation. The maximum memory that can be occupied by an internal table (including its internal administration) is 2 gigabytes. A more realistic figure is up to 500 megabytes. An additional restriction for hashed tables is that they may not contain more than 2 million entries. The line types of internal tables can be any ABAP data types - elementary, structured, or internal tables. The individual lines of an internal table are called table lines or table entries. Each component of a structured line is called a column in the internal table.
    Choosing a Table Type
    The table type (and particularly the access method) that you will use depends on how the typical internal table operations will be most frequently executed.
    Standard tables
    This is the most appropriate type if you are going to address the individual table entries using the index. Index access is the quickest possible access. You should fill a standard table by appending lines (ABAP APPEND statement), and read, modify and delete entries by specifying the index (INDEX option with the relevant ABAP command). The access time for a standard table increases in a linear relationship with the number of table entries. If you need key access, standard tables are particularly useful if you can fill and process the table in separate steps. For example, you could fill the table by appending entries, and then sort it. If you use the binary search option with key access, the response time is logarithmically proportional to the number of table entries.
    Sorted tables
    This is the most appropriate type if you need a table which is sorted as you fill it. You fill sorted tables using the INSERT statement. Entries are inserted according to the sort sequence defined through the table key. Any illegal entries are recognized as soon as you try to add them to the table. The response time for key access is logarithmically proportional to the number of table entries, since the system always uses a binary search. Sorted tables are particularly useful for partially sequential processing in a LOOP if you specify the beginning of the table key in the WHERE condition.
    Hashed tables
    This is the most appropriate type for any table where the main operation is key access. You cannot access a hashed table using its index. The response time for key access remains constant, regardless of the number of table entries. Like database tables, hashed tables always have a unique key. Hashed tables are useful if you want to construct and use an internal table which resembles a database table or for processing large amounts of data.
    Advanced Topics
    Batch Input: Concepts
    Processing Sessions
    The above figure shows how a batch input session works.A batch input session is a set of one or more calls to transactions along with the data to be processed by the transactions. The system normally executes the transactions in a session non-interactively, allowing rapid entry of bulk data into an R/3 System.
    A session records transactions and data in a special format that can be interpreted by the R/3 System. When the System reads a session, it uses the data in the session to simulate on-line entry of transactions and data. The System can call transactions and enter data using most of the facilities that are available to interactive users.
    For example, the data that a session enters into transaction screens is subject to the same consistency checking as in normal interactive operation. Further, batch input sessions are subject to the user-based authorization checking that is performed by the system.
    Advantages of ABAP over Contemporary languages
    ABAP Objects offers a number of advantages, even if you want to continue using procedural programming. If you want to use new ABAP features, you have to use object-oriented interfaces anyway.
    Sharing Data: With ABAP shared objects, you can aggregate data once at a central location and the different users and programs can then access this data without the need for copying.
    Exception Handling: With the class-based exception concept of ABAP, you can define a special control flow for a specific error situation and provide the user with information about the error.
    Developing Persistency: For permanent storage of data in ABAP, you use relational database tables by means of database-independent Open SQL, which is integrated in ABAP. However, you can also store selected objects transparently or access the integrated database or other databases using proprietary SQL.
    Connectivity and Interoperability: The Exchange Infrastructure and Web services are the means by which developers can implement a service-oriented architecture. With Web services, you can provide and consume services independently of implementation or protocol. Furthermore, you can do so within NetWeaver and in the communication with other systems. With the features of the Exchange Infrastructure, you can enable, manage, and adapt integration scenarios between systems.
    Making Enhancements: With the Enhancement Framework, you can enhance programs, function modules, and global classes without modification as well as replace existing code. The Switch Framework enables you activate only specific development objects or enhancements in a system.
    Considerable Aspects
    It follows a list of aspects to be considered during development. The list of course is not complete.
    Dynpro persistence
    When implementing dynpros one has to care for himself to read out and persist the necessary fields. Recently it happened to me that I forgot to include a field into the UPDATE-clause which is an error not so easy to uncover if you have other problems to be solved in the same package. Here, tool-support or built-in mechanisms would help.
    The developer could help himself out by creating something like a document containing a cookbook or guide in which parts of a dynpro logic one has to care about persistence. With that at hand, it would be quite easy finding those bugs in short time. Maybe a report scanning for the definition of the dynpro fields to be persisted could scan the code automatically, too.
    Memory Cache
    It should be common-sense that avoiding select-statements onto the database helps reducing the server load. For that the programmer either can resort to function modules if available. This maybe is the case for important tables. Or the programmer needs to implement his own logic using internal tables. Here, the standard software package could provide the developer with a tool or a mechanism auto-generating memory cached tables resp. function modules implementing this.
    Sometimes buffering of database tables could be used, if applicable. But that would require an effort in customizing the system and could drain down system performance overall, especially if a table is involved that has a central role.
    Interfaces
    It should be noticed that some function modules available have an incomplete interface. That means, the interface does not include all parameters evaluated by the logic of the function module. For example, global variables from within the function group could be read out, which cannot be influenced by the general caller. Or memory parameters are used internally to feed the logic with further information.
    One workaround here would be copying the relevant parts of the logic to a newly created function module and then adapt it to the own context. This sometimes is possible, maybe if the copied code is not too lengthy and only a few or no calls to other logic is part of it.
    A modification of the SAP code could be considered, if the modification itself is unavoidable (or another solution would be not justifiable by estimated effort to spend on it) and if the location of the modification seems quite safe against future upgrades or hot fixes. The latter is something that could be evaluated by contacting the SAP hotline or working with OSS message (searching thru existing one, perhaps open a new one).
    Example
    'From SAP NetWeaver:'
    set an exclusive lock at level object-type & object-id
    IF NOT lf_bapi_error = true.
    IF ( NOT istourhd-doc_type IS INITIAL ) AND
    ( NOT istourhd-doc_id IS INITIAL )
    CALL FUNCTION 'ENQUEUE_/DSD/E_HH_RAREF'
    EXPORTING
    obj_typ = istourhd-doc_type
    obj_id = istourhd-doc_id
    EXCEPTIONS
    foreign_lock = 1
    system_failure = 2
    OTHERS = 3.
    IF sy-subrc <> 0.
    terminate processing...
    lf_bapi_error = true.—
    ...and add message to return table
    PERFORM set_msg_to_bapiret2
    USING sy-msgid gc_abort sy-msgno
    sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4
    gc_istourhd gc_enqueue_refdoc space
    CHANGING lt_return.
    ENDIF.
    ENDIF.
    ENDIF. " bapi error
    Example Report(Type - ALV(Advanced List Viewer))
    REPORT Z_ALV_SIMPLE_EXAMPLE_WITH_ITAB .
    *Simple example to use ALV and to define the ALV data in an internal
    *table
    *data definition
    tables:
    marav. "Table MARA and table MAKT
    Data to be displayed in ALV
    Using the following syntax, REUSE_ALV_FIELDCATALOG_MERGE can auto-
    matically determine the fieldstructure from this source program
    Data:
    begin of imat occurs 100,
    matnr like marav-matnr, "Material number
    maktx like marav-maktx, "Material short text
    matkl like marav-matkl, "Material group (so you can test to make
    " intermediate sums)
    ntgew like marav-ntgew, "Net weight, numeric field (so you can test to
    "make sums)
    gewei like marav-gewei, "weight unit (just to be complete)
    end of imat.
    Other data needed
    field to store report name
    data i_repid like sy-repid.
    field to check table length
    data i_lines like sy-tabix.
    Data for ALV display
    TYPE-POOLS: SLIS.
    data int_fcat type SLIS_T_FIELDCAT_ALV.
    select-options:
    s_matnr for marav-matnr matchcode object MAT1.
    start-of-selection.
    read data into table imat
    select * from marav
    into corresponding fields of table imat
    where
    matnr in s_matnr.
    Check if material was found
    clear i_lines.
    describe table imat lines i_lines.
    if i_lines lt 1.
    Using hardcoded write here for easy upload
    write: /
    'No materials found.'.
    exit.
    endif.
    end-of-selection.
    To use ALV, we need a DDIC-structure or a thing called Fieldcatalogue.
    The fieldcatalouge can be generated by FUNCTION
    'REUSE_ALV_FIELDCATALOG_MERGE' from an internal table from any
    report source, including this report.
    Store report name
    i_repid = sy-repid.
    Create Fieldcatalogue from internal table
    CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE'
    EXPORTING
    I_PROGRAM_NAME = i_repid
    I_INTERNAL_TABNAME = 'IMAT' "capital letters!
    I_INCLNAME = i_repid
    CHANGING
    CT_FIELDCAT = int_fcat
    EXCEPTIONS
    INCONSISTENT_INTERFACE = 1
    PROGRAM_ERROR = 2
    OTHERS = 3.
    *explanations:
    I_PROGRAM_NAME is the program which calls this function
    I_INTERNAL_TABNAME is the name of the internal table which you want
    to display in ALV
    I_INCLNAME is the ABAP-source where the internal table is defined
    (DATA....)
    CT_FIELDCAT contains the Fieldcatalouge that we need later for
    ALV display
    IF SY-SUBRC <> 0.
    write: /
    'Returncode',
    sy-subrc,
    'from FUNCTION REUSE_ALV_FIELDCATALOG_MERGE'.
    ENDIF.
    *This was the fieldcatlogue
    Call for ALV list display
    CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'
    EXPORTING
    I_CALLBACK_PROGRAM = i_repid
    IT_FIELDCAT = int_fcat
    TABLES
    T_OUTTAB = imat
    EXCEPTIONS
    PROGRAM_ERROR = 1
    OTHERS = 2.
    *explanations:
    I_CALLBACK_PROGRAM is the program which calls this function
    IT_FIELDCAT (just made by REUSE_ALV_FIELDCATALOG_MERGE) contains
    now the data definition needed for display
    I_SAVE allows the user to save his own layouts
    T_OUTTAB contains the data to be displayed in ALV
    IF SY-SUBRC <> 0.
    write: /
    'Returncode',
    sy-subrc,
    'from FUNCTION REUSE_ALV_LIST_DISPLAY'.
    ENDIF.
    OOPs ABAP uses Classes and Interfaces which uses Methods and events.
    If you have Java skills it is advantage for you.
    There are Local classes as well as Global Classes.
    Local classes we can work in SE38 straight away.
    But mostly it is better to use the Global classes.
    Global Classes or Interfaces are to be created in SE24.
    SAP already given some predefined classes and Interfaces.
    This OOPS concepts very useful for writing BADI's also.
    So first create a class in SE 24.
    Define attributes, Methods for that class.
    Define parameters for that Method.
    You can define event handlers also to handle the messages.
    After creation in each method write the code.
    Methods are similar to ABAP PERFORM -FORM statements.
    After the creation of CLass and methods come to SE38 and create the program.
    In the program create a object type ref to that class and with the help of that Object call the methods of that Class and display the data.
    Regards
    Anji

  • What is the difference between jsp :include and server side include

    what is the difference between jsp :include and server side include(request dispatcher include method)????
    i understand that both request dispatcher include method and jsp:include take dynamic data,so when would one use request dispatcher include and when jsp:include.
    Is the usage interchangeable?i believe jsp include is used only for jsp/html but include directive can be used to include servlets ,jsp and html....correct me if i m wrong and
    do suggest if u hav ny other diff in this context...

    The difference really is: in what format do you want your inclusions? If your environment has many Java developers and only a few designers that focus mainly on, say, Flash, that might push you more towards the server-side include() directive. Or, if you have a large set of pages that receive dynamic content that is displayed in a consistent fashion (such as a workflow header area on a page).
    If, on the other hand, you have more web designers, there may be a greater desire to deal in markup rather than Java code. Java developers themselves might prefer to view markup (JSP) that more resembles the eventual output than something occuring in Java code.
    Finally, there are considerations of tiering. While it is totally possible to (and I have previously) implement 'view classes' that render markup or generate layout templates, JSP's offer, IMO, a subtle, psychological advantage. By forcing a developer to work in a different format, markup versus Java source, the separation on view from controller and model becomes a bit easier. It is still possible to make mistakes, but if a developer at some point notices, "Wait, I'm in a JSP, should I be importing a java.sql class?", then the choice to use JSP includes has paid off in spades.
    - Saish

Maybe you are looking for

  • Could not find MessageClient for clientId in pushMessageToClients

    Hello everybody. I was stuck with unpleasent problem using LCDS 2.5.1 and theirs messaging service. My aim is sending real time messages to particular client which already subscribed to the defined destination within java code. I have following situa

  • MS-OFFICE interface in FORMS6i

    I would like to do the following : 1. Create a MS-Word document with certain field in the doc template filled up from database on Click of button in Forms6i web solution. IS IT POSSIBLE to call MS_OFFICE Products from FORMS6i web deployment?. VERY UR

  • API for video profile selection in Adobe Flash Player

    Thanks to ActionScript 3, we are able to do programming with regard to Flash Player behavior,  extract info, etc. Since now Adobe Flash Player supports adaptive bit rate video, I wonder if there is an API for Adobe Flash Player so that we can set a f

  • Rend:Error when attempting to send images

    I'm using iChat 4.0.2, communicating with my friend running 3.1.8. When I try to send him an image through direct connect, he receives this message: "An undefined AIM error has occurred. The server message was: Rend:Error" On my end, things look fine

  • Gift Card just stopped working?!?!?!

    Ok, i was just buying songs on iTunes when in the middle of purchasing the second selected song, it said that there was a payment issue and I had to use my credit card. what is up???