Applying field exclusion , if A then B.

Hi,
I am wondering if it's possible to 'switch' off fields based on the end-user's response.
To simplify things, I have this example:  I have 3 fields.  If the answer for the (3rd) field is checked, then it negates all responses from 1-2 and thus, those boxes will be come 'blank'.
I want to know how to 'cancel'/'exclude those 2 fields if the end user checks the 3rd field.
Is there a way to use Acrobat Pro X to make this work?
Does it matter what type of field I use (if there is a method to do so)?
I am still a novice with this software eventhough I've played with it for abit so I'd appreciate simple and clear instructions/responses.
Thanks,

Hi again,
Yes, I am using checkbox, radio button and also text boxes.
So for the checkbox/radio button option, I tried changing the script to (to reflect what I want to do):
if (event.target.value == 'No') {
     this.getField(Field_1').display = display.hidden
     this.getField(Field_2').display = display.hidden
} else {
     this.getField(Field_1').display = display.visible
     this.getField('Field_2').display = display.visible
In my case, I have Yes or No (radiobuttons set).  If answer is Yes, then they will need to fill in a few text-boxes.
I want to make it so, if the answer was <No>  then the boxes set for Yes responses would be off-limits (hidden in this case).
I tried the script, and it worked. However, I realized also that if my end user responded to YES and answer the text boxes for those then , found out they made a mistake, their responses for Yes remains eventhough it<s really a No.   The biggest problem is, when I export the data, I would still get the responses for YES.  Which would create havoc for me since I won't know if their answer is Yes or No since no I have both answers!
I assume that the script is for 1-way/alternative response only.   If a mistake happened, it could not be corrected?
I was hoping that the end-user (given they're humans) make mistakes but is allowed to correct them and when we receive the answers, we will get the correct ones.
Can there be something like that?   such that if the answer is 'No', then whatever that was filled in for the positive response would be wiped off or deleted automatically? so we won't have the trouble with the export data?
If I am not clear, please let me know.

Similar Messages

  • New itunes is destroying my life. It won't allow me to search. As soon as I type a single key in the search field. It freezes, then crashes. WHY??????

    It won't allow me to search. As soon as I type a single key in the search field. It freezes, then crashes. WHY??????

    Launch the Console application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
    Step 1
    Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left.
    Enter the name of the crashed application or process in the Filter text field. Post the messages from the time of the last crash, if any — the text, please, not a screenshot. 
    When posting a log extract, be selective. In most cases, a few dozen lines are more than enough.
    Please do not indiscriminately dump thousands of lines from the log into a message.
    Important: Some private information, such as your name, may appear in the log. Edit it out by search-and-replace in a text editor before posting.
    Step 2
    Still in the Console window, look under User Diagnostic Reports for crash reports related to the process. The report name starts with the name of the crashed process, and ends with ".crash". Select the most recent report and post the entire contents — again, the text, not a screenshot. In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.) Please don’t post shutdownStall, spin, or hang logs — they're very long and not helpful.

  • Hashing of the password field using MD5 and then store in the XML

    Hi,
    I need to design a form with User ID and a Password field. When i extract the XML from the form i need to hash the password field using MD5 and then store it. Does anyone have some kind of experience in doint it. Can you please suggest some way to do it.
    Thanks,
    Sayoni.

    Hi,
    To hash password you can use function from http://kevin.vanzonneveld.net/techblog/article/javascript_equivalent_for_phps_md5/ or try to find another implementation. Just call this function on some event like button click for example.
    Also I made some example. See attach.
    BR,
    Paul Butenko

  • Material Master Extract with some fields in legacy shorter then SAP

    Hi ,
         I need to Extract Material master data and send to Material Management System(MMS), i am able to fetch the data into internal table with fields of MMS structure. My problem is SAP has 18 characters for MATNR field and MMS has only 6 characters, like wise some fields are shorter length in MMS then in SAP. How can i truncate all the values of the corresponding fields in my output internal table so that i can download the file to MMS system.
    Regards
    Krishna

    There won't be any sort of one step transformation that you can do.
    You will have to loop through the records in your internal table and for each record:
    - Map your fields accross to a structure defined with the lenghts as you need them for the external system.  Do any truncating or transformation that you require.
    - Append the new record to a second internal table
    You will then use this second internal table to extract and send.
    ~Ian

  • How to apply an adjustment, make edits, then delete the adjustment (but keep the edits)?

    I've got a photo that was shot at a crooked angle which I tried correcting using the Straighten tool in CS5 Extended but the straightened version crops out far too much of the image for my liking.  So I manually rotated and cropped the photo so that it's straight and still includes what I want it to but of course I was left with large white spaces on all four corners of the photo.  After a lot of work I was able to fill in all the white spaces manually using the clone stamp and it looks fine the way it is now on my monitor but when the image is lightened even slightly many obvious cloning flaws begin to show and I'm afraid that people with monitors that display the image lighter will be able to see the obvious cloning work I did.
    So what I'd like to do is apply a layer or mask or filter that uses the Shadows/Highlights feature to lighten the image enough to expose everything and then use that lightened over-exposed version to make the necessary fixes with the clone stamp tool and fix all the flaws that show when the image is lighter -- then, after having fixed the cloning flaws, I'd like to get rid of the Shadows/Highlights layer/mask/filter so that the photo goes back to its original exposure, except this time with the flaws fixed.  I'm still fairly new to CS5 and I haven't found a way to do this yet.  So far every time I apply Shadows/Highlights using a layer or filter I either can't do the cloning work on the lightened image or I can but then it won't let me get rid of the Shadows/Highlights after the cloning work is done.
    Is there any way around this?
    Thanks in advance for any help!

    Try using the new Edit - Fill - Content Aware feature to fill corners exposed by the rotation.  Select first, taking a few pixels of the image as well in the selection, then try the fill.  You may need to touch things up a bit after, but I'm betting it will get you there more quickly than with manual cloning.
    I tried this but unfortunately kept getting the error: "Could not fill because there's not enough data to fill it in a Content-Aware manner."
    My solution is a custom bright color profile that I toggle with Ctrl + Y which is a shortcut for Color Proofing.
    Here's how to do it.
    Edit > Color Settings (Shift + Ctrl + K). In the Working Spaces section, using the RGB menu, scroll up and choose Custom RGB...
    For the name type myBrightRGB , change the Gamma to 0.75, and press OK
    From the same RGB menu, scroll up and choose Save RGB...  and save the profile in this location C:\Windows\System32\spool\drivers\color
    Click the Cancel button in the Color Settings
    With an image open, go to View > Proof Setup > Monitor RGB, then View > Proof Setup > Custom...  and from Device to Simulate menu choose myBrightRGB profile and press OK.
    From now on toggle the Color Proof with Ctrl + Y to edit your image in the prefered color space.
    This is also a perfect solution for checking how images will look on overbright miscalibrated displays.
    Sounds like a great solution, however after following all those steps I'm not seeing an option for "myBrightRGB" anywhere in the drop down menu next to Device to Simulate.  I tried restarting Photoshop, still not there.  I did notice that in the C:\Windows\system32\spool\drivers\color folder that "myBrightRGB.csf" was the only csf file in there -- all the rest of the files in that folder are ICC files.  Not sure if that makes a difference as far as this is concerned.  When I go to View > Proof Setup > Custom, the Customize Proof Condition window has an option to "Load..." and I tried selecting the myBrightRGB file that way but it'll only load .PSF files.  Is there something I'm missing?

  • Apply metadata to unlinked photos, then sync MD when files available

    I share my master catalog between a desktop and a laptop. The desktop has all the master files (on RAIDs, archived drives, etc.), so all I have access to when I use LR3 on my laptop are the previews of my files. While I know I obviously can't edit (develop) missing files, what I'd love to be able to do is annotate on my laptop, then when I copy the catalog over to the desktop, it will sync this metadata to the actual xmp sidecar files. As it stands now, one can only apply metadata when the linked files are attached.

    So, what the camera writes, the Exif metadata, is inside the photo file, or in another hidden file for each photo?
    It’s “inside” the file.
    How come then it happens that sometimes the date changes after you've written the pictures on a CD, and imported them from that later... shouldn't the metadata stay with the file? It happens mostly with early camera phone pictures...
    A photo can lose the metadata in imperfect copies, or - in the case of early camera phones - there may have been none at all. In which case iPhoto uses the File “Date Created” instead.
    I have a lot of pictures whose dates I really had to change because they were wrong - I just hope this work won't go down the drain further down the road... perhaps when importing into a new Mac, or when using a different program altogether...?
    In the case of moving to a new Mac:
    Simply move the Library to the new machine. That will get all the data, metadata, originals, edited versions and so on.
    In using a different application:
    1. If it understands the iPhoto Library (like Aperture, for instance) then you will have no issue
    2. If it doesn’t, then you export the Pics from iPhoto (File -> Export) and check the box at Title and Keywords. This will mean that your Titles, Keywords +and Descriptions+ (though not explicitly mentioned) will be written to the IPTC data.
    Regards
    TD

  • TOTAL_TIME_SEC field value is more then 2000 sec in S_NQ_ACCT table

    Hi Everyone,
    In a Usage tracking report, I am displaying report response time (which is total_time_sec field in S_NQ_ACCT table).
    For few reports, this field value is displayed as more than 2000 secs, but in reality, that report doesn't run more than 2 secs.
    In the database table S_NQ_ACCT also Time is recorded as more than 2000 secs. But the time is supposed to be 2 secs.
    Please let me know if anyone is having idea on this issue.
    Thanks in Advance.

    Check this post:
    http://sranka.wordpress.com/2010/06/22/the-myth-usage-tracking-measures-for-tracking-the-performance-of-report-retrieval-time/

  • TS3297 How do I connect to iTunes or some reasons I have two IDs one for apply that isign in with then an iTunes ID  that they have me enter when trying to download an upgrade for App .  That ID Is not working because no matter how many times I reset it e

    The error reads cannot connect to iTunes store at this time plz help I'm so lost!! rhiannonstthomas@me com

    First of all, a word of advice, don't post your email on the internet, it'll only lead to trouble.
    Second, you mention you have two apple IDs.  let's call them A & B.
    I'm assuming you downloaded the app you wish to upgrade with 'A'  and you're currently using 'B' for whatever reason.  If that's the case, then there's nothing to be done, apps are associated with the Apple ID you used to buy them originally and can't be transferred to a new one. If you wish to upgrade an App you bought using your Apple ID 'A' you'll need that ID's password. The alternative would be to repurchase the said app with your new Apple ID, in this case 'B'.

  • How to capture data in a field from a table then insert them it to a destination table

    Environment:
    SQL Server 2008 R2
    Introduction:
    I have three tables. one is staging, the other child, the last one is parent. Both parent and child table have referential integrity
    (exam_id) .  The definition of the child table is 
    CREATE TABLE [dbo].child
    [ind_id] [int] IDENTITY(1,1) NOT NULL,
    [exam_dt] [datetime] NULL, exam_id int not null, [sub_cd] [nvarchar](4) NOT NULL,
    [score] [varchar](2) NOT NULL,
    The parent table has the following definition 
    CREATE TABLE [dbo].[parent]
    [exam_id] [int] IDENTITY(1,1) NOT NULL,
    [pn_id] [char](9) NOT NULL,
    [sub_cd] [varchar](3) NULL
    when loading 1000 records to the table each record has exam_id generated. 
    Problem:
    I was able successfully to load data from staging to parent but, How would I load/copy from parent exam_id - identity (1,1 )generated upon loading data - to the destination table (child table)
    Please help 

    Environment:
    SQL Server 2008 R2
    Introduction:
    I have three tables. one is staging, the other child, the last one is parent. Both parent and child table have referential integrity
    (exam_id) .  The definition of the child table is 
    CREATE TABLE [dbo].child
    [ind_id] [int] IDENTITY(1,1) NOT NULL,
    [exam_dt] [datetime] NULL, exam_id int not null, [sub_cd] [nvarchar](4) NOT NULL,
    [score] [varchar](2) NOT NULL,
    The parent table has the following definition 
    CREATE TABLE [dbo].[parent]
    [exam_id] [int] IDENTITY(1,1) NOT NULL,
    [pn_id] [char](9) NOT NULL,
    [sub_cd] [varchar](3) NULL
    when loading 1000 records to the table each record has exam_id generated. 
    Problem:
    I was able successfully to load data from staging to parent but, How would I load/copy from parent exam_id - identity (1,1 )generated upon loading data - to the destination table (child table)
    Please help 
    I could be misunderstanding your requirements, but I get the feeling you're misunderstood. I can see the exam_id (better named parent_id) acts as a foreign key to exam_id (better named fk_parent_id) in the child table.
    Without seeing the data though, it's not immediately obvious how you identify the relationship between the two while loading. When the data is supplied, what is the format of the third, source table? Does this include parent and child as single entries including
    a relationship ie normalised data?
    I don't know if this is useful or not, but when inserting single records into a table with an identity key:
    insert into table1 (col2, col3) select 'text1','text2'
    insert into table2 (col2, col3, FK, col5) select 'text1','text2',@@identity, 'text3'
    @@identity provides the last inserted value. Obviously for larger scale operations this isn't what you're looking for.
    In the event your staging table happened to hold parent, child and a source record ID (identity column in staging, but just a secondary indexed column in the other tables) however, you would have the rather easy job of:
    update child
    set exam_id = parent.exam_id
    from child inner join parent on child.source_id = parent.source_id
    Really hard to guess without seeing more

  • PE4 File Export giving wrong field order

    In PE4, when I execute File-Export with the following settings:
    General/File Type: Microsoft DV AVI
    Video/Compressor: DV PAL
    Keyframe and Rendering/Fields: Upper Field First
    It creates the AVI OK, but GSPOT shows that the AVI is Lower Field First, not Upper Field First as specified in the settings.
    Why?  Is this a bug or does selecting DV force LFF (if so, then why isn't the UFF option greyed out in the settings?).
    What I am trying to do is create some smaller sub-projects in the form of AVI's, which I will eventually import into a final large project.  The source files for the subprojects are mpgs from an HD camcorder, so they are Upper Field First (UFF), and so I am using the PAL Harddisk project preset, which expects source files to be UFF.
    Since my final project will include both UFF mpgs and those AVI subprojects, I want the AVIs to be UFF also, so that I don't have to selectively reverse field orders etc.
    Is this wrong?
    Thanks
    Dave

    ==> "You can even use Premiere Elements for the conversion by applying field order reversal and then exporting to DV-AVI."
    Splitting hairs I know, but again to clarify for me:
    For the initial conversion to DV-AVI, if I start a project in PE4 with a UFF preset, bring in my UFF mpgs, then export to DV-AVI (WITHOUT applying field order reversal), is this doing the same as what you suggest?  That is, in this case, the field reversal is taken care of by PE4 behind the scenes because I told it to do so by using a UFF preset?  Or do I still need to manually reverse the fields?
    Sorry to be dense, but there seems to be many ways to do the same thing, and I'm trying to figure out the simplest and least error prone way to do it.
    Dave

  • Is it possible to store a field name in a variable, then assign it a value?

    Good day, everyone!
    I am working on a program in which there are many different amount fields in which an amount may be assigned.  For reusability purposes, I was wondering if it would be possible to write a routine that identifies the target amount field, stores it in a variable that is passed back to the calling program, and then assigns a value to it.  There may be different structures having the same field name; what I'm trying to do is avoid having to code a huge IF or CASE statement for each structure.  For example:
    Structures S1, S2, and S3 have some fields identically named.  Call one of them F1.
    What I'd like to do is call a routine that identifies "F1" as my target field to populate.  Then, upon return, I can assign it to the desired structure.  Kinda like this:
    S1-fieldname = 24.17.  (but fieldname isn't a true field in the structure -- it would hold the value of the true field, "F1").
    I realize this might not even be possible, but given how talented the folks are on this forum, I thought I should at least pose the question.
    As always, points given for all helpful answers, and thank you!!
    Dave

    Ok.  I gave that a shot, but what happens is that my ASSIGN COMPONENT statement doesn't work.  It gets a sy-subrc of 4, and <column> remains unassigned.  The program then abends on the line to assign <a1>-trbtr's value to the field because of <column> being unassigned.
      DATA:
        w_setname         TYPE setleaf-setname,
        w_column_name(20) TYPE c.
        ASSIGN COMPONENT w_column_name OF STRUCTURE wa_expense_ng_report
                      TO <column>.
        <column> = <a1>-trbtr.
    Any thoughts on what I might be doing wrong?

  • Add fields to Existing DSO and DS in R/3

    Hi Friends,
    I have got to change my LO datasource which is running on production, 2lis_va_vatim, i need to add 2 fields to the exisitng DS from Comm Stru, so could anyone point me inthe right direction, Hoow to Add the fields with out disturbing the production,
    and the same way i need to cgane my DSO aswell for new fields, please tell me how to meet this.
    Thanks,
    Kiran.

    Hi Kiran,
    Before applying your changes in Production do the below steps:
    1)run V3 job as immediate, which picks data to delta queue and delete the acive V3 job.
    2)run the IP which loads data to BW(Delta IP).
    3)Apply your changes to the 2lis_va_vatim and DSO.
      i)Do the changes(adding your fields to 2lis_va_vatim and DSO)in DEV and active the 2lis_va_vatim and DSO.(insert this in transports).
    ii)first apply the R3 transport and then BW side.
    4)from now on wards your 2 fileds will get populated in BW side.
    5)Maintain the V3 job for 2lis_va_vatim in R3.
    If you need any clarification how to add fields to 2lis_va_vatim and create transport req pelase check the below article.
    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/2050db8b-9d90-2c10-2980-b13a4b0938f6
    Hope this helps.
    Regards,
    Venkatesh.

  • Field Catalogs in ALV

    Hi Friends,
    Please help me out, I am new to ABAP.
    Please anybody explain me the functionality of Field catalogs in ALVs?
    How many methods are there to pass data to ALVs, i.e., in how many ways?
    Hope u will help me.

    hi,
    this will be very helpful for ALV REPORTING.....
    Sap provides a set of ALV (ABAP LIST VIEWER) function modules which can be put into use to embellish the output of a report. This set of ALV functions is used to enhance the readability and functionality of any report output. Cases arise in sap when the output of a report contains columns extending more than 255 characters in length.  In such cases, this set of ALV functions can help choose selected columns and arrange the different columns from a report output and also save different variants for report display. This is a very efficient tool for dynamically sorting and arranging the columns from a report output. The report output can contain upto 90 columns in the display with the wide array of display options.
    The commonly used ALV functions used for this purpose are;
    1.     REUSE_ALV_VARIANT_DEFAULT_GET
    2.     REUSE_ALV_VARIANT_F4
    3.     REUSE_ALV_VARIANT_EXISTENCE
    4.     REUSE_ALV_EVENTS_GET
    5.     REUSE_ALV_COMMENTARY_WRITE
    6.   REUSE_ALV_FIELDCATALOG_MERGE
    7.   REUSE_ALV_LIST_DISPLAY
    8.     REUSE_ALV_GRID_DISPLAY
    9.     REUSE_ALV_POPUP_TO_SELECT
    The different steps used for getting the above function modules into use are:
    Step 1
    DATA DECLARATION
    Sap standard type pools:  SLIS , KKBLO .
    Sap standard tables types taken from the type pools are:  SLIS_LAYOUT_ALV ,
                                             SLIS_T_FIELDCAT_ALV,
    SLIS_T_LISTHEADER,
    SLIS_T_EVENT,
    SLIS_SELFIELD.
    Internal tables to used in the program declared based on the above table types
    DATA:  I_LAYOUT TYPE SLIS_LAYOUT_ALV,
                I_FIELDTAB TYPE SLIS_T_FIELDCAT_ALV,
               I_HEADING TYPE SLIS_T_LISTHEADER,
    I_EVENTS TYPE SLIS_T_EVENT.
    TYPES:  KKBLO_SELFIELD TYPE SLIS_SELFIELD.
    Step 2 (Optional)
    SELECTING THE VARIANTS FOR INITIAL LIST DISPLAY (DEFAULT VARIANT)
    The variants in the list display can be both user-specific and general. The user can programmatically set the initial (default) variant for list display.
    The default variant can be found using the function module 'REUSE_ALV_VARIANT_DEFAULT_GET'.
    Sample code:
    CALL FUNCTION 'REUSE_ALV_VARIANT_DEFAULT_GET'
           EXPORTING
                i_save     = variant save condition ( A=all, U = user-specific )
           CHANGING
                cs_variant = internal table containing the program name (and the default variant---optional )
           EXCEPTIONS
                not_found  = 2.
    The user can also choose from the list of existing variants using the function module ‘REUSE_ALV_VARIANT_F4’.
    Step 3
    DEFININING OUTPUT CHARACTERISTICS: PREPARING DISPLAY FIELDS CATALOG
    A field catalog is prepared using the internal table (I_FIELDCAT) of type SLIS_T_FIELDCAT_ALV. Field catalog containing descriptions of the list output fields (usually a subset of the internal output table fields).
    A field catalog is required for every ALV list output to add desired functionality (i.e. Key, Hotspot, Specific headings, Justify, Col. position etc) to certain fields of the output. If not mentioned specifically, then the defaults are taken. The possible values and defaults are listed below.
    The field catalog for the output table is built-up in the caller's coding. The build-up can be completely or partially automated by calling the REUSE_ALV_FIELDCATALOG_MERGE module.
    The minimal field catalog is documented below. This can be done in a routine using a local variable. The user can use the other optional parameters to assign output attributes to different fields in the output, which differ from the default.
    A field catalog need not be built-up and passed explicitly only under the following conditions:
    1.     The internal table to be output has the same structure as a Data Dictionary structure which is referred to in the internal table declaration using LIKE or INCLUDE STRUCTURE. In this case the attributes of the different fields is taken directly from the table and the attributes (key fields, length, texts etc) need to state explicitly.
    2.     all fields in this structure are to be output
    3.     The structure name is passed to ALV in the parameter I_STRUCTURE_NAME of the function module REUSE_ALV_LIST_DISPLAY.
    All the values entered in the catalog is specific to the particular field whose name is entered in the fieldname FIELDNAME of the fieldcat structure. The name of the table is also entered in the corr. Fieldname TABNAME of the structure.
    The different possible attributes are:
    •     Row_pos (row position): Only relevant if the list output is to be multi-line (two or three lines) by default. So, this attribute can be used maintain certain level of alignment in the output.
                         Value set: 0, 1 – 3
    •     Col_pos (column position): This parameter is relevant when the fields in the output are to be different from the sequence of the fields in the internal table used for display.       The parameter specifies the relative column position of the field in the list output. The column order can be changed interactively by the user. If this parameter is initial for all field catalog entries, columns appear in the internal table field sequence.
    Value set: 0, 1 – 60
    •     Fieldname (field name): This is the name of the internal table field for which the parameters are passed in the catalog.
    Value set: internal output table field name (required parameter)
    •     Tabname (internal output table): Name of the internal output table that contains the field FIELDCAT-FIELDNAME above.
                         Value set: SPACE, internal output table name.
    •     Ref_fieldname (reference field name): Name of the Data Dictionary field referred to. This parameter is only used when the internal output table field described by the current field catalog entry has a reference to the Data Dictionary (not a program field), and the field name in the internal output table is different from the name of the field in the        Data Dictionary. If the field names are identical, naming the Data Dictionary structure or table in the FIELDCAT-REF_TABNAME parameter is sufficient.
        Value set: SPACE, Data Dictionary field name.
    •     Ref_tabname (reference table/structure field name): Structure or table name of the referred Data Dictionary field.        This parameter is only used when the internal output table field described by the current field catalog entry has a Data Dictionary reference (not a program field).
    Value set: SPACE, name of a Data Dictionary structure or table
    Link to currency unit
    •     Cfieldname (currency unit field name): This is used for currency fields that have a reference to any unit field. This is only relevant for amount columns with associated unit. This parameter contains the Name of the internal output table field containing the currency unit associated with the amount field FIELDCAT-FIELDNAME. The field in FIELDCAT-CFIELDNAME must have its own field catalog entry.
    Value set: SPACE, output table field name
    •     Ctabname (internal currency unit field output table): Name of the internal output table containing the FIELDCAT-CFIELDNAME field.
    Value set: SPACE, output table field name.
            Link to measurement unit
    •     Qfieldname (measurement unit field name): Only relevant for quantity columns with unit link. Name of the internal output table field containing the measurement unit associated with the quantity field FIELDCAT-FIELDNAME. The field in FIELDCAT-QFIELDNAME must have its own field catalog entry.
    Value set: SPACE, output table field name.
    •     Qtabname (internal measurement unit field output table): Name of the internal output table containing the FIELDCAT-QFIELDNAME field.
    Value set: SPACE, output table field name.
    •     Outputlen (column width): This parameter is used if the desired output length for a field is desired to be different from the internal output table field. For fields with a Data Dictionary link this parameter can be left initial. For fields without a Data Dictionary link (program field) the parameter must be given the value of the desired field list output length (column width).
    Initial = column width is the output length of the referred Data Dictionary field (domain).
    N = column width is n characters.
          Value set: 0 (initial), n.
    •     Key (key column): By default, the system makes some fields in the output as key fields, provided the fields are key fields in their referencing table. Using this parameter, fields other than key fields of the referencing table can be made key field. This parameter is most important if the output needs to contain some field which are not scrollable or cannot be hidden.
    If the internal output table contains fields that are key fields from different tables, then all those fields in the report output becomes unscrollable and cannot be hidden. So, the fields in the output internal table should not be referenced from tables in which they are key fields. Instead, they should be referenced to the tables in which they are not key fields, incase they are not desired as key field in the output.
    'X' = key field (key field output in color) and Key fields can not be interactively hidden. Parameter FIELDCAT-NO_OUT must be left initial.
          Value set: SPACE, 'X'.
    •     Key_sel (hideable key column): This parameter is only relevant for the fields which are made key fields using FIELDCAT-KEY = 'X'. Using this parameter the Key field can be hidden interactively.
    The key column sequence cannot be changed interactively by the user. The output is controlled by the FIELDCAT-NO_OUT parameter analogously to non-key fields.
    Value set: SPACE, 'X'.
    •     No_out (field in field list): This parameter is used to remove certain fields from the output during initial display.  The user can however interactively choose the field for output from the field list in the display variant.
                'X' = field is not displayed in the current list.
            Value set: SPACE, 'X'.
    •     Tech (technical field): This parameter is used to make certain field display only in the field catalog. The fields with this parameter set cannot be output in the list nor can they be displayed interactively from the catalog.
                        'X' = technical field.
           Value set: SPACE, 'X'.
    •     Emphasize (highlight columns in color): As name suggests, this field parameter is used to highlight certain field with chosen colors.
    Value set: SPACE, 'X' or 'Cxyz' (x:'1'-'9'; y,z: '0'=off ,'1'=on).
    'X' = column is colored with the default column highlight color.
                        'Cxyz' = column is colored with a coded color:
                      -  C: Color (coding must begin with C)
                     -  X: color number
                      -  Y: bold
                       -  Z: inverse
    •     Hotspot (column as hotspot): This parameter is used to make certain field appear as hotspot i.e. a hand is displayed if the cursor is positioned on the field value. Single click on such fields cause the PICK OR F2 events to happen.
             Value set: SPACE, 'X'.
                        'X' = column cells are output as hotspots.
    •     Fix_column (fix column): This parameter is used to fix certain columns in the output. All columns to be fixed must have this flag, starting from the left. If a column without this flag is output, only the columns to the left of this column are fixed. The user can change the column fixing interactively.
                         Value set: SPACE, 'X'.
            'X' = column fixed (does not scroll horizontally).
    •     Do_sum (sum over column): the user can also call this function interactively.
                      Value set: SPACE, 'X'.
    'X' = a sum is calculated over this internal output table field.
    •     No_sum (sums forbidden): No sum can be calculated over this field, although the data type of the field would allow summing.
             Value set: SPACE, 'X'.
    •     Icon: The parameter displays certain column contents as icons. The internal output table column contents must be valid icon strings.
                        Value set: SPACE, 'X'.
                         'X' = column contents to be output as an icon.
    •     Symbol: The internal output table column must be a valid symbol character.
    Value set: SPACE, 'X'
                        'X' = column contents are to be output as a symbol.
    •     Just (justification): This parameter is used for alignment of the contents of the output table. This is only relevant for CHAR or NUMC fields in the output internal table. The justification of the column header always follows the justification of the columns. Independent justification of the column header is not possible.
    Value set: SPACE, 'R', 'L', and ‘C’.
           ' ' = Default justification for this data type
           'R' = right-justified output
           'L' = left-justified output
           'C' = centered output.
    •     Lzero (leading zeros): By default ALV outputs NUMC fields right-justified without leading zeros. Using this parameter only the NUMC fields can be displayed with leading zeroes.
                       Value set: SPACE, 'X'.
                        'X' = output with leading zeros.
    •     No_sign (no +/- sign): This parameter is used to suppress the signs of the output fields. It is only relevant for the value fields.
        Value set: SPACE, 'X'.
               'X' = value output without +/ sign.
    •     No_zero (suppress zeros): Only relevant for value fields.
                 Value set: SPACE, 'X'.
                        'X' = suppress zeros.
    •     Edit_mask (field formatting): To apply the report output formatting options same as in the WRITE statement in report writing.
               Value set: SPACE, template.
    The following parameters are used for customizing the texts in the heading of the output of the columns. The texts are taken from the Data Dictionary for fields with a Data Dictionary reference. If this is not desired, the text parameters can also be specified. The Data Dictionary texts are then ignored.
    If the user changes the column width interactively, the column header text with the appropriate length is always used.
    The interactive function 'Optimize column width' takes account of both the field contents and the column headers: if all field contents are shorter than the shortest column header, the column width depends on the column header.
         The 'long field label' is also used in display variant definition,
            Sort, etc.  Popup.
    •     seltext_l (long field label)
    •     seltext_m (medium field label)
    •     seltext_s (short field label)
    •     reptext_ddic(header) Analogous to the Data element main header
    •     Ddictxt (specify text) : You can specify with values 'L', 'M',  and 'S', the keyword that should always be used as column header. If the column width changes, no attempt is made in this case to find an appropriate header for the new output width.
    Value set: SPACE, 'L', 'M', and ‘S’.
    Sample code:
    Suppose I_PO_DETAILS is an internal table containing two fields EBELN (PO number) and EBELP (PO item no).
    DATA: L_FIELDCAT TYPE SLIS_FIELDCAT_ALV.     “Local variable to hold the parameters                                                                               
    for a particular field of the field catalog
      CLEAR L_FIELDCAT.
      L_FIELDCAT-TABNAME   = 'I_PO_DETAILS'.
      L_FIELDCAT-FIELDNAME = 'EBELN'.
      L_FIELDCAT-KEY = 'X'.         “The PO no is made the key field,
                          “Colored and non scrollable
      L_FIELDCAT-HOTSPOT = 'X'.     “The po no becomes a hotspot
      L_FIELDCAT-SELTEXT_S = ‘P.O No’.
      L_FIELDCAT-SELTEXT_M = 'P order No'.
      L_FIELDCAT-SELTEXT_L = 'Purchase order No'.
      APPEND L_FIELDCAT TO I_FIELDTAB.
      CLEAR L_FIELDCAT
      L_FIELDCAT-TABNAME   = 'I_PO_DETAILS'.
      L_FIELDCAT-FIELDNAME = 'EBELN'.
      L_FIELDCAT-KEY = 'X'.         “The po item no is made the key field,
                               “Colored and non scrollable
      L_FIELDCAT-SELTEXT_S = 'Item No'.
      L_FIELDCAT-SELTEXT_M = 'Item No`.
      L_FIELDCAT-SELTEXT_L = 'PO Item No'.
      APPEND L_FIELDCAT TO I_FIELDTAB.
      CLEAR L_FIELDCAT
    Thus the catalog for the report output is prepared.
    Step 4
    The next step is to build an event table, which are used for firing both user commands and the system dependent events i.e. top of page, end of page etc.
    A list of possible events is populated into an event table (I_EVENTS) when this table is passed to the function module REUSE_ALV_EVENT_NAMES_GET. The return table from this function module contains all the possible events.
    The function module contains following import and export parameters.
    IMPORTING PARAMETERS: I_LIST_TYPE
    This parameter has possible values from 0-4.
    The parameter I_LIST_TYPE is of TYPE SLIS_LIST_TYPE and is DEFAULT 0 .
    EXPORTING PARAMETERS:  I_EVENTS table.
    This table is of TYPE SLIS_T_EVENT and returns to the program the name of all the possible events.
    The table structure contains the fields:
         I_EVENTS-NAME: Name of the Callback event.
    I_EVENTS-FORM: Name of the form routine that should be called in the calling program at the event.
    Only events with a form routine name are processed.
    The I_EVENTS table returns with the following possible constants:
    1.     Slis_ev_item_data_expand TYPE slis_formname VALUE 'ITEM_DATA_EXPAND'.     
    Only relevant for hierarchical-sequential lists using the layout parameter IS_LAYOUT-EXPAND_FIELDNAME of the structure IS_LAYOUT. Exit for passing item entries (ITEM table) for a header record that was expanded interactively by the user.
    2.     Slis_ev_reprep_sel_modify TYPE slis_formname VALUE 'REPREP_SEL_MODIFY'.
    RS_SELFIELD-TABINDEX contains the header table index for which the item entries are to       be put in the global item output table (T_OUTTAB_SLAVE). The Callback is only called if ALV has no items for a header that is to be expanded.
    RFLG_ALL is passed with 'X' if the user shows all items. The application must ensure that    entries are not repeated in the item table.
        RS_SELFIELD is initial in this case.         
    3.     Slis_ev_caller_exit_at_start TYPE slis_formname VALUE 'CALLER_EXIT'.
    Is called at the beginning of the function module to make special settings. It is not usually used.          
    4.     Slis_ev_user_command TYPE slis_formname VALUE 'USER_COMMAND'.
    As this is a frequently-used Callback event, the form routine can also be passed        directly in the interface by passing the user command in the IMPORTING parameter           I_CALLBACK_USER_COMMAND.
    5.     Slis_ev_top_of_page TYPE slis_formname VALUE 'TOP_OF_PAGE'.
       Equivalent to the list processing TOP-OF-PAGE event.           
    6.     Slis_ev_top_of_coverpage TYPE slis_formname VALUE 'TOP_OF_COVERPAGE'.       
    The selection information and list status are output together (if they exist) on a separate page by default
    7.     Slis_ev_end_of_coverpage TYPE slis_formname VALUE 'END_OF_COVERPAGE'.       
    Analogously to TOP_OF_COVERPAGE the user can add other information
    to the information output by ALV (selection information, list status) at this event.
    8.     Slis_ev_foreign_top_of_page TYPE slis_formname VALUE ‘FOREIGN_TOP_OF_PAGE'.
    The Top-of-page event is always processed in ALV and is only passed to the caller via the Callback mechanism. This is still the case if the caller, e.g. by a user action, processes a branch list which was not formatted by ALV (e.g. a popup with additional information about the list record selected and displayed by ALV).
    In this case, top-of-page cannot be formatted by ALV analogously to the basic list, it must be handled completely by the caller. The event top-of-page still occurs in ALV. When ALV notices a top-of-page which was not caused by an ALV output, the form routine in FOREIGN_TOP_OF_PAGE is called.
    9.     Slis_ev_foreign_end_of_page TYPE slis_formname VALUE 'FOREIGN_END_OF_PAGE'.  
    The event end-of-page is always processed in ALV and only passed to the caller via callback. This is still the case, e.g. when the caller processes a details list which was not formatted by ALV (e.g. a popup with further information about selected list records which were displayed by ALV).
    In this case, end-of-page cannot be formatted by ALV analogously to the basic list, it must be handled completely by the caller. The event end-of-page still occurs in ALV. When ALV notices an end-of-page that was not caused by an ALV output, the form routine in FOREIGN_END_OF_PAGE is called.                             
    10.     Slis_ev_pf_status_set TYPE slis_formname VALUE 'PF_STATUS_SET'.
    If a user list status is to be set, it must be done in the form routine assigned to this event. The ALV function codes, which must not be active, are in the Parameter RT_EXTAB. This table must be passed with the SET PF-STATUS command (with inactive user function codes as well, if necessary).
    The STANDARD status of the function group SALV should be used as a          template for a user-specific status. As this is a frequently used Callback event, its form routine can also be passed directly in the interface in the IMPORTING parameter I_CALLBACK_PF_STATUS_SET.
    11.     Slis_ev_list_modify TYPE slis_formname VALUE 'LIST_MODIFY'.     
    LIST_MODIFY USING R_TABNAME TYPE SLIS_TABNAME
                                             R_INDEX LIKE SY-TABIX
                                             R_INDEX_ITEM LIKE SY-TABIX
                                             R_INDEX_SUM LIKE SY-TABIX.
    12.     Slis_ev_top_of_list TYPE slis_formname VALUE 'TOP_OF_LIST'.  
    Information output at the start of the list     
    13.     Slis_ev_end_of_page TYPE slis_formname VALUE 'END_OF_PAGE'.
    Information output at the end of a page. This is only called for printing.
    14.     Slis_ev_end_of_list TYPE slis_formname VALUE 'END_OF_LIST'.     
    Information output at the end of the list
    15.     Slis_ev_after_line_output TYPE slis_formname VALUE 'AFTER_LINE_OUTPUT'.
    Output information after each output line. Should only be used in justified cases because it costs a lot of performance.
    16.     Slis_ev_before_line_output TYPE slis_formname VALUE   'BEFORE_LINE_OUTPUT'.       
    Output information before each output line. Should only be used in justified cases because it costs a lot of performance.         
    17.     Slis_ev_subtotal_text TYPE slis_formname VALUE  'SUBTOTAL_TEXT'.                        
    This event table (I_EVENTS) is now checked with the desired constants. If the desired constant is found, then the corresponding field for the FORM NAME is populated with the name of the routine containing the corresponding event.
    Sample code :
    FORMNAME_TOP_OF_PAGE TYPE SLIS_FORMNAME VALUE 'TOP_OF_PAGE',
    FORMNAME_END_OF_PAGE TYPE SLIS_FORMNAME VALUE 'END_OF_PAGE', FORMNAME_USER_COMMAND TYPE SLIS_FORMNAME VALUE 'USER_COMMAND'.
    DATA: L_I_EVENT TYPE SLIS_ALV_EVENT.
      CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
           EXPORTING
               I_LIST_TYPE = 0
           IMPORTING
                ET_EVENTS   = I_EVENTS.
      READ TABLE I_EVENTS WITH KEY NAME = SLIS_EV_TOP_OF_PAGE
                               INTO L_I_EVENT.
      IF SY-SUBRC = 0.
        MOVE FORMNAME_TOP_OF_PAGE TO L_I_EVENT-FORM.
        APPEND L_I_EVENT TO I_EVENTS.
      ENDIF.
      READ TABLE I_EVENTS WITH KEY NAME = SLIS_EV_END_OF_PAGE
                               INTO L_I_EVENT.
      IF SY-SUBRC = 0.
        MOVE FORMNAME_END_OF_PAGE TO L_I_EVENT-FORM.
        APPEND L_I_EVENT TO I_EVENTS.
      ENDIF.
      CLEAR L_I_EVENT.
      READ TABLE I_EVENTS WITH KEY NAME = SLIS_EV_USER_COMMAND
                               INTO L_I_EVENT.
      IF SY-SUBRC = 0.
        MOVE FORMNAME_USER_COMMAND TO L_I_EVENT-FORM.
        APPEND L_I_EVENT TO I_EVENTS.
      ENDIF.
    This will prepare the events table for the report.
    The report will contain three forms for the above events:
    1.     FORM TOP_OF_PAGE : This form will contain the top of page event for the report i.e header etc
    Using the function module ‘REUSE_ALV_COMMENTARY_WRITE’, the internal table containing the headings for top of page event can be passed to the list output. Also, any logo specific to the report can be passed to the function module.
    2.     FORM END_OF_PAGE : This form will contain the end of page event for the report i.e footer etc
    3.     FORM USER_COMMAND : This form will contain the desired user command i.e pick/line selection
    Step 5
    A layout is build for the report output list description USING the internal table declared above (I_LAYOUT).
    Output list description structure.
         The parameters are described under the following heads:
    •     Display options
    •     Exceptions
    •     Totals
    •     Interaction
    •     Detail screen
    •     Display variants (only for hierarchical-sequential lists)
    •     Color
    •     Other
    The layout table is of type slis_layout_alv_spec and has the following fields:
    Display options                                                
    1. Colwidth_optimize (1) TYPE c: This parameter optimizes the length of the different columns in the output. The width of the different col. now depends on the max. Length of the data in the column.
    Value set: SPACE, 'X'
    'X' = optimizes the column width so that all contents are displayed completely.                   
    2. No_colhead(1) TYPE c : This parameter suppresses the column headings                    
    Value set: SPACE, 'X'.
    'X' = column headers are not output
    3. No_hotspot(1) TYPE c :  The heading of the report output are not output as hotspot.       
    Value set: SPACE, 'X'.
    'X' = column headers are not output as hotspot
    4. Zebra(1) TYPE c : The report is output in the striped pattern.             
    Value set: SPACE, 'X'.
    'X' = striped pattern (e.g. for wide lists)
    5. No_vline(1) TYPE c : The report output contains columns only separated by space and no lines.  It is not relevant for: hierarchical-sequential lists and multiple-line lists.
    Value set: SPACE, 'X'.
    'X' = columns separated by SPACE
    6. No_min_linesize(1) TYPE c : The report  line size is equal to the width of the list. It is not relevant for block lists.
    Value set: SPACE, 'X’.
    'X' = line size depends on list width
    '  ' = Line size is set to 80 or MIN_LINESIZE (if > 0) .
    7. Min_linesize LIKE sy-linsz: The report output contains a minimum possible length of line. If initial min_linesize is set to 80 by default, then this parameter is used to customize it. The prerequisite for this is that the parameter no_min_linesize should be ' '.
    Value set: 0, 10 - 250
    If the list is wider, the format uses the list width (maximum 250 or MAX_LINESIZE (if > 0)).
    8. Max_linesize LIKE sy-linsz: The default max. Linesize is 250. To change this default value, this parameter can interactively-define the maximum list width setting.
    Value set: 0, 80 - 1020
    9. Window_titlebar LIKE rsmpe-tittext: To set the titlebar on the report output.                            
               10. No_uline_hs(1) TYPE c.
    Exceptions                                                 
    11. Lights_fieldname TYPE slis_fieldname: Internal output table field containing the codes of exceptions to be output.
                      Output table field code:  '1' = red traffic light
                                    '2' = yellow traffic light
                                         '3' = green traffic light Fieldname for exception 
         Value set: SPACE, internal output table field name.
    12. Lights_tabname TYPE slis_tabname: Name of the internal output table that contains the field in the parameter LIGHTS_FIELDNAME. If LIGHTS_FIELDNAME is not empty, this field must also be filled for hierarchical-sequential lists. Only relevant for hierarchical-sequential lists.
    .     Value set: SPACE, internal output table name.
    13. Lights_rollname LIKE dfies-rollname: The documentation of this data element is displayed when you call F1 help for an exception column.
    Value set: SPACE, data element name.
               14. Lights_condense(1) TYPE c : If a list record is output with 'red traffic light', each
               Subtotal that includes this record is also output with 'red traffic light'.
               Value set: SPACE, 'X'
               'X' = the 'maximum' exception of the items in the subtotal is output at subtotal level.
    Sums                                                       
    15. No_sumchoice(1) TYPE c : This parameter allows the choice for summing up
    Only by fieldcatalog.
    Value set: SPACE, 'X'
    'X' = fields which are to be summed, passed by the calling program (FIELDCAT-DO_SUM = 'X'). The user should not be able to change this value interactively.
    16. No_totalline(1) TYPE c : Removes the option of having totals after sub-totals.
    Value set: SPACE, 'X'
    'X' = no total record is to be output. Subtotals can still be calculated and output. The fields in the subtotals are flagged DO_SUM = 'X' in the field list.
    17. No_subchoice(1) TYPE c : Does not allow the user to interactively change the field chosen for subtotals.
    Value set: SPACE, 'X'
    'X' = value whose change triggers subtotals, provided by the calling program. The user should not be able to change this value interactively.
    18. No_subtotals(1) TYPE c : No subtotals possible          
    Value set: SPACE, 'X'
    'X' = no subtotals.
    19. Numc_sum(1)  TYPE c : Totals only possible for NUMC-Fields.
    20. No_unit_splitting TYPE c: No separate total lines by inh.units   
    21.totals_before_items TYPE c: Display totals before the items   
    22. Totals_only(1) TYPE c :  Show only totals      
    Value set: SPACE, 'X'
    'X' = only total records are output.
    23. Totals_text(60) TYPE c : Text for 1st col. in totals   
    Value set: SPACE, string (max.60)
    ' ' = The first column in the total record contains an appropriate number of '*'s to indicate the total by default. If the first column is wide enough, the string 'Total' is output after the asterisks.
    'String’ = The string passed is output after the total indicated by '*', if the column is wide enough.
    24. Subtotals_text(60) TYPE c : Texts for subtotals
    Value set: SPACE, string (max.60)
    ' ' = In the first column of subtotal records, the subtotal is indicated by an appropriate number of '*' by default. If the first column is not a subtotal criterion, the string 'Total' is output after the asterisks, if the column is wide enough.
    'String’ = the string passed is output after the subtotal indicated by '*', if the column is wide enough and the first column is not a subtotal criterion. If it is a subtotal criterion, its value is repeated after the total, if the column is wide enough.
    Interaction                                                      
    25. Box_fieldname TYPE slis_fieldname: Fieldname for checkbox in the report output. If the list has checkboxes at the start of records (for selecting several records), this parameter contains the internal output table field name indicated by the checkbox selection column. The field is a checkbox at the start of list records without a list header.
    Value set: SPACE, internal output table field name
    26. Box_tabname TYPE slis_tabname: Name of the internal output table that contains the field in the parameter BOX_FIELDNAME. If BOX_FIELDNAME is not empty, this field must also be filled for hierarchical-sequential lists.
    Value set: SPACE, internal output table name.
    27. Box_rollname LIKE dd03p-rollname: rollname for checkbox          
    28. Expand_fieldname TYPE slis_fieldname: fieldname flag ‘expand’. The user can show or hide the items by clicking on the folder symbol (hotspot). If the items for a header entry are only to be read by the calling program and passed to ALV when a header has been expanded interactively, this can be controlled via the CALLBACK event        'ITEM_DATA_EXPAND'.
    29. Hotspot_fieldname TYPE slis_fieldname: Used to make the fieldname flag hotspot.
    30. No_input(1) TYPE c : The fields are only display fields.
            Value set: SPACE, 'X'
    'X' = all ready-for-input fields in a list are displayed as not ready-for-input. (Record selection checkboxes and fields which can be made ready-for-input via the field list parameter FIELDCAT-INPUT = 'X')
    31. F2code LIKE sy-ucomm: To assign an ALV standard function code to double-click (F2), assign the function code to this parameter. Ex.: to assign the ALV standard function 'Detail' ('&ETA') to F2.
                      => LAYOUT-F2CODE = '&ETA'.
    Value set: SPACE, function code
    32. Confirmation_prompt: confirm. Prompt when leaving       
    Value set: SPACE, 'X'
    'X' = if one of the functions ‘Back (F03)', ‘Exit (F15)' or ‘Cancel (F12)' occurs, a confirmation prompt appears.
    33. Key_hotspot(1) TYPE c : The key fields are displayed as hotspot. The columns defined in the field catalog as key fields (FIELDCAT-KEY = 'X') are output as hotspots, i.e. clicking on a key column (highlighted in color in the list) calls the function under F2.
    Value set: SPACE, 'X'.
    34. Reprep(1) TYPE c :  report report interface active.     
    35. Group_buttons(1) TYPE c :  group-buttons for COL1 - COL5 . Group output fields via FIELDCAT-SP_GROUP in the field list, and pass the group name to the list module in the interface parameter IT_SPECIAL_GROUPS.           
    Value set: SPACE, 'X'.
    36. No_keyfix(1) TYPE c : Used to make the key fields scrollable.
    Value set: SPACE, 'X'.
    ' ' = The key columns defined in the field catalog by FIELDCAT-KEY = 'X' are fixed in the list output. These columns do not scroll horizontally. The item table key columns are fixed in hierarchical-sequential lists. The header table key fields are not considered here.
    'X' = key columns not fixed
    37. Get_selinfos(1) TYPE c : To read selection screen.
    Value set: SPACE, 'X'.
    If the calling program is a report with an ABAP/4 selection screen, setting this parameter makes ALV read the selection screen again. If the selections are read successfully, a pushbutton, via which the user can call a popup which lists the report selections in a simple form, becomes active on the results list output by ALV.
    38.     group_change_edit(1) TYPE c :  Settings by user for new group     
    Value set: SPACE, 'X'
    'X' = the user can enter a format option for each sort criterion in the sort/subtotal popup, for the list format when this value changes (e.g. new page or underline).
    39.     No_scrolling(1) TYPE c : Does not allow scrolling of the list to the right.
    Value set: SPACE, 'X'.
    40. Expand_all(1) TYPE c : Expand all positions                   
    Detailed screen                                                    
    40.     Detail_popup(1) TYPE c : show detail in popup.
    Value set: SPACE, 'X'
    '  '  = List record detail display in full-screen mode, with top-of-page.
    'X'  = list record detail display in popup (without top-of-page).
    41. Detail_initial_lines(1) TYPE c : show also initial lines   
    Value set: SPACE, 'X'
    '  ' = Only fields whose contents are not initial are output in the detail view.
    'X' = initial field contents are also output in detail.
    41.     detail_titlebar(30) type c : Titlebar for detail screen
    Value set: SPACE, string (max.30)
    ` ' = ' Detail: Display' is output as the title of the detail window.
                  'String’ = the string passed is output as the title of the detail window. 
    Display variants                                                   
    42. Header_text (20) TYPE c: Text for header button. Only relevant for hierarchical-sequential lists. You can toggle between display field and field list views via pushbuttons in the display variant definition popup for hierarchical-sequential lists. The views refer to the hierarchy level of the fields. This is technically a toggle between the header table and item table fields.   
    Value set: SPACE, CHAR (20)
    ' ' = The header table field pushbutton text is 'Header' by default.
    CHAR (20) = header table field pushbutton text.
    43.item_text(20) TYPE c : Text for item button. Only relevant for hierarchical-sequential lists. You can toggle the view between the display fields and the field list via pushbuttons in the display variant definition popup for hierarchical-sequential lists. The views refer to the hierarchy level of the fields. This is technically a toggle between the header table and item table fields.        
    Value set: SPACE, CHAR (20)
    ' ' = The pushbutton text for the item table fields is 'Item' by default.
    CHAR (20) = item table field pushbutton text.
    44.default_ item(1) TYPE c : Items as default. Only relevant for hierarchical-sequential lists.
         Value set: SPACE, 'X'
    ' ' = The header table fields are displayed by default in the display variant definition popup. The user can switch to the item table fields interactively.
    'X' = the item table fields are displayed by default in the display variant Definition Popup.    The user can switch to the header table fields interactively.
    Colour                                                       
    45. Info_fieldname TYPE slis_fieldname: infofield for listoutput. A whole list record can be colored individually using a color code in a column of the internal output table for the record. Assign the name of the field containing the color code to this parameter.
    Value set: SPACE, internal output table field name
    The internal output table field must be of type CHAR(3).
    The code must have the following syntax:  'Cxy':
            C = color (all codes must start with 'C')
            X = color number ('1'-'9')
            Y = bold ('0' = off, '1' = on)
    46. Coltab_fieldname TYPE slis_fieldname: Cells can be colored individually using a color code which is contained in a column of the internal output table for the record containing the cell. Assign the name of the field to this parameter.       
    Others                                                
    47. List_append(1) TYPE c :  no call screen. It is only useful to output block-lists without specifying the above modules if the number of list blocks exceeds, or may exceed, the maximum number specified in the block module documentation. These operations are not possible for user-defined block lists.
    Example code :
           I_LAYOUT-f2code       = ws_fcode.
           I_LAYOUT-zebra        = 'X'.
    I_LAYOUT-colwidth_optimize = 'X'.
    I_LAYOUT-no_keyfix = 'X'.
    I_LAYOUT-get_selinfos = 'X'.
    I_LAYOUT-no_hotspot = 'X'.
           I_LAYOUT-no_input = 'X'.
    I_LAYOUT-hotspot_fieldname = FIELDNAME.
    I_LAYOUT-no_input          = ‘X’.
    I_LAYOUT-no_vline          = `X’.
    I_LAYOUT-no_colhead        = ‘ ‘.
    I_LAYOUT-lights_condense   = ` `.
    I_LAYOUT-totals_text       = ` `.
    I_LAYOUT-subtotals_text    = ` `.
    I_LAYOUT-totals_only       = ` `.
    I_LAYOUT-key_hotspot       = ‘X’.
    I_LAYOUT-detail_popup      = ‘X’.
    I_LAYOUT-group_change_edit = ‘X’.
    I_LAYOUT-GROUP_BUTTONS     = ‘X’.
    Step 6
    This step is required to get the selection screen information in the report output.
    The prerequisite for this is to set the parameter LAYOUT-GET_SELINFOS of the IMPORTING structure.
    The parameters to be passed in the IS_SEL_HIDE table are:
    o mode:              'R' = only the entries passed in the internal table IS_SEL_HIDE-T_ENTRIES       
    Are output in the pop up. Selection info, which the list tool read in the selection screen (when called by a report with a selection screen), is replaced by the values passed.
    'S' = the selection info which the list tool read in the selection screen of the calling report are modified by the entries in the table IS_SEL_HIDE-T_ENTRIES.
    o t_entries:         Selection info table
    o t_entries-mode:   'A' = output the selection info for the current table record in the info popup.
    'D' = do not output select option or SELNAME parameter selection info in   the popup.
    o t_entries-selname: (only used in t_entries-mode = 'D') : Name of the select option or parameter.
    The following table fields are only used in t_entries-mode = 'A'. They contain the selection information to be added.
    •     t_entries-field:  DDIC field name of the field for which selection information is to be output.
    •     t_entries-table:  DDIC table names of t_entries-field.
    •     t_entries-stext:  Field name in info popup.
    •     If t_entries-field and t_entries-table have been entered, this text is taken from DDIC.
    •     t_entries-valuf:  Selection condition 'from' value (external format)
    •     t_entries-valut:  Selection condition 'to' value (external format)
    •     t_entries-sign0:  (I)nclusive (E)xclusive
    •     t_entries-option:  All values of the select options Option field allowed.
    Step 6
    The Table IT_SORT is populated with the sort criteria for the different fields.
    The caller specifies the sorting and/or subtotaling of the basic list in the internal table IT_SORT.
    This internal table has the following fields:
         o spos :  Sort sequence
         o fieldname :  Internal output table field name
         o tabname : Only relevant for hierarchical-sequential lists. Name of the internal output table.
         o up : 'X' = sort in ascending order
         o down : 'X' = sort in descending order
         o subtot : 'X' = subtotal at group value change
         o group : '* ' = new page at group value change ,'UL' = underline at group value change
                             Step 7
    The final step in the output of the report is the use of two ALV functions modules.
    1.     REUSE_ALV_FIELDCATALOG_MERGE
    2.     REUSE_ALV_LIST_DISPLAY
    The first function module is used to pass the field catalog to the report output and merge it with the internal output table.
    FUNCTION reuse_alv_fieldcatalog_merge.                                
    ""Lokale Schnittstelle:                                             
    *” IMPORTING                                                    
    *"             VALUE(I_PROGRAM_NAME) LIKE  SY-REPID OPTIONAL          
    *"             VALUE(I_INTERNAL_TABNAME) TYPE  SLIS_TABNAME OPTIONAL  
    *"             VALUE(I_STRUCTURE_NAME) LIKE  DD02L-TABNAME OPTIONAL   
    *"             VALUE(I_CLIENT_NEVER_DISPLAY) TYPE  SLIS_CHAR_1        
    *"                             DEFAULT 'X'                            
    *"             VALUE(I_INCLNAME) LIKE  TRDIR-NAME OPTIONAL            
    *"       CHANGING                                                     
    *"             VALUE(CT_FIELDCAT) TYPE  SLIS_T_FIELDCAT_ALV           
    *"       EXCEPTIONS                                                   
    *"              INCONSISTENT_INTERFACE                                
    *"              PROGRAM_ERROR                                         
    Import parameters 
    I_PROGRAM_NAME: Program in which the internal output table is declared and populated   
    I_INTERNAL_TABNAME: Internal output table name
    I_STRUCTURE_NAME: Structure name (structure, table, and view)
    I_CLIENT_NEVER_DISPL: Hide client fields default ‘X’
    I_INCLNAME: Data declarations include name
    CHANGING parameter
    CT_FIELDCAT: Field catalog with field descriptions
    The variant based on a program-internal table should only be used for rapid prototyping since the following restrictions apply:                                                                               
    1.   Performance is affected since the code of the table definition must always be read and interpreted at runtime.                                                                               
    2.   Dictionary reference are only considered if the keywords LIKE or  INCLUDE STRUCTURE (not TYPE) are used.
    Step 8
    The other function module is used to display the internal output table with the contents
    FUNCTION reuse_alv_list_display.                                          
    ""Lokale Schnittstelle:                                                 
    *” IMPORTING                                                        
    *"             VALUE(I_INTERFACE_CHECK) DEFAULT SPACE                     
    *"             VALUE(I_CALLBACK_PROGRAM) LIKE  SY-REPID DEFAULT SPACE     
    *"             VALUE(I_CALLBACK_PF_STATUS_SET) TYPE  SLIS_FORMNAME        
    *"                             DEFAULT SPACE                              
    *"             VALUE(I_CALLBACK_USER_COMMAND) TYPE  SLIS_FORMNAME         
    *"                             DEFAULT SPACE                              
    *"             VALUE(I_STRUCTURE_NAME) LIKE  DD02L-TABNAME OPTIONAL       
    *"             VALUE(IS_LAYOUT) TYPE  SLIS_LAYOUT_ALV OPTIONAL            
    *"             VALUE(IT_FIELDCAT) TYPE  SLIS_T_FIELDCAT_ALV OPTIONAL      
    *"             VALUE(IT_EXCLUDING) TYPE  SLIS_T_EXTAB OPTIONAL            
    *"             VALUE(IT_SPECIAL_GROUPS) TYPE  SLIS_T_SP_GROUP_ALV         
    *"                             OPTIONAL                                   
    *"             VALUE(IT_SORT) TYPE  SLIS_T_SORTINFO_ALV OPTIONAL          
    *"             VALUE(IT_FILTER) TYPE  SLIS_T_FILTER_ALV OPTIONAL          
    *"             VALUE(IS_SEL_HIDE) TYPE  SLIS_SEL_HIDE_ALV OPTIONAL        
    *"           VALUE(I_DEFAULT) DEFAULT 'X'
    "             VALUE(I_SAVE) DEFAULT SPACE                             
    "             VALUE(IS_VARIANT) LIKE  DISVARIANT                      
    "                             STRUCTURE  DISVARIANT DEFAULT SPACE     
    "             VALUE(IT_EVENTS) TYPE  SLIS_T_EVENT OPTIONAL            
    "             VALUE(IT_EVENT_EXIT) TYPE  SLIS_T_EVENT_EXIT OPTIONAL   
    "             VALUE(IS_PRINT) TYPE  SLIS_PRINT_ALV OPTIONAL           
    "             VALUE(IS_REPREP_ID) TYPE  SLIS_REPREP_ID OPTIONAL       
    "             VALUE(I_SCREEN_START_COLUMN) DEFAULT 0                  
    "             VALUE(I_SCREEN_START_LINE) DEFAULT 0                    
    "             VALUE(I_SCREEN_END_COLUMN) DEFAULT 0                    
    "             VALUE(I_SCREEN_END_LINE) DEFAULT 0                      
    "       EXPORTING                                                     
    "             VALUE(E_EXIT_CAUSED_BY_CALLER)                          
    "             VALUE(ES_EXIT_CAUSED_BY_USER) TYPE  SLIS_EXIT_BY_USER   
    "       TABLES                                                        
    "              T_OUTTAB                                               
    "       EXCEPTIONS                                                    
    "              PROGRAM_ERROR
    Import parameters
    I_INTERFACE_CHECK: Interface consistency check log output.
    I_CALLBACK_PROGRAM: Name of the calling program
    I_CALLBACK_PF_STATUS_SET: Set EXIT routine to status.   
    I_CALLBACK_USER_COMMAND: EXIT routine for command handling
    I_STRUCTURE_NAME: Internal output table structure name     
    IS_LAYOUT: List layout specifications 
    IT_FIELDCAT: Field catalog with field descriptions
    IT_EXCLUDING: Table of inactive function codes   
    IT_SPECIAL_GROUPS: Grouping fields for column selection
    IT_SORT: Sort criteria for first list display
    IT_FILTER: Filter criteria for first list output
    IS_SEL_HIDE     : Selection information modification
    I_DEFAULT:      Initial variant active/inactive logic
    I_SAVE: Variants can be saved
    IS_VARIANT     : Variant information
    IT_EVENTS: Table of events to perform  IT_EVENT_EXIT :  Standard fcode exit requests table 
    IS_PRINT: Print information
    IS_REPREP_ID: Initialization keys for Re/Re interface
    I_SCREEN_START_COLUMN: Coordinates for list in dialog box
    I_SCREEN_START_LINE: Coordinates for list in dialog box
    I_SCREEN_END_COLUMN: Coordinates for list in dialog box        
    I_SCREEN_END_LINE: Coordinates f

  • How to create a pdf/a-1b with a text field

    hello, I'm trying to execute a very simple task: create a pdf/a-1b containig a text field.
    using Acrobat XI pro, I created a simple pdf form with 1 form field of type text , then tried to save as pdf/A-1b. The pdf is saved but the form field is removed from resulting pdf.
    Here in detail the steps I made:
    0) configure adobe pdf printer to save as pdf/A-1b
    1) creat a test.txt with notepad
    2) print using acrobat pdf printer
    3) open the generated pdf with Acrobat XI
    4) in 'Standards' panel I see that pdf conform
    5) now go to 'Tools\Modules' and 'Modify'
    6) add a textbox field
    7) exit from 'Modify' mode and save
    8) in 'Standards' panel I see that pdf doesn't conform.
    9) I opened the preflight tool and see two errors
         a) "XMP property for a page object not predefined and no extension schema present".
         page reports the following Trigger values:
         - Extension schema is present in XMP: is not true
         - Property exists in PDF/A Standard: is not true
         b) Form field does not have an appearance dictionary
         page reports the following Trigger values:
         - Form field has an appearance dictionary: is not true
    I'm quite new to Acrobat: simply downloaded the Actobat XI evaluation version, created the file and added the text field. No special settings nor other configurations was applied,
    I'm wondering if someone else was able to reproduce this behavior.
    thank you for any comment

    First, about invalidating the PDF/A. I was told, but never had this confirmed nor tested, that editing a PDF/A will automatically cause the PDF/A status to be deleted from the file. This is because Acrobat does not know about the compatibility of every edit with every current (and future) PDF subset standard, so it is safest just to remove the indicator - if you turn off Adobe's PDF/A view mode which will prevent editing anyway.
    Now, you have a problem with the signatures. Possibly a very big one. Your description "2) fill the text field with some annotations and then sign the signature field 3) save the pdf" is a little too separated. At the time a file is signed it is saved, the hash calculated, and written to the file. So signing and saving are just one action. Yet an unsigned digital signature needs, it seems to me, no appearance.
    I think the solution is a simple one. Sign it, but not with a signature field. If it is PDF/A when you start it is probably PDF/A when you finish. Signature fields seem a distraction and obstacle to the important thing, signing.

  • Error while applying patchset 11.1.0.7 to 11.1.0.6

    Hi, I am a new DBA and would appreciate any help on this.
    I am in the process of upgrading my database from 10.2.0.4 to 11.1.0.7. I installed 11.1.0.6 and was applying the 11.1.0.7 patch. I installed the 11g patchset successfully and was working on 'Upgrading Oracle Database 11g Release 11.1.0.6 to Oracle Database 11g Release 11.1.0.7' - Section 9.2 of the readme of the 11.1.0.7 patchset. After starting the dbua and selecting the 11g home that needed to be upgraded, the dbua gave the error -
    The upgrade Assistant failed in bringing up the database proddb1. Oracle Home /opt/oracle/product/11.1.0/dev obtained from file /etc/oratab was used to connect to the database. Either the database is not running from Oracle Home /opt/oracle/product/11.1.0/dev or the pfile /oravol00/oracle/product/11.1.0/dev/dbs/init.ora used is incorrect. Correct the error and run the Upgrade Assistant again.
    Here are some more details about my system - I have a 10g dev instance and a 10g production instance also running on the same box. The 11g instance location is /oravol00/opt/oracle/product/11.1.0/dev and has a soft link to /opt/oracle/product/11.1.0/dev.
    I read another thread on the OTN where another person had the same problem and was asked to start the database in the upgrade mode from sqlplus and then try the dbua again. I tried that - started the databse in startup upgrade mode and it gave me this error -
    SQL> startup upgrade;
    ORACLE instance started.
    Total System Global Area 1.0088E+10 bytes
    Fixed Size 2162320 bytes
    Variable Size 5502927216 bytes
    Database Buffers 4563402752 bytes
    Redo Buffers 19697664 bytes
    ORA-03113: end-of-file on communication channel
    Process ID: 19677
    Session ID: 170 Serial number: 3
    Can someone please give me some clue on what I did wrong here and how to correct it? Any help is appreciated.
    Edited by: user12158503 on Mar 12, 2010 7:47 PM

    I checked my alert log and see errors from the day I installed the 11g instance. When DBUA said the installation is complete, I thought everything went fine. But now I see alert log had errors since then. I created the database on March 12th and tried to install the 11.1.0.7 patch on March 14th by around 3pm. Here is more clarification on the upgrade. I am trying to upgrade my dev environment. I plan to upgrade using export/import. For this I created the 11g instance and am applying the 11.1.07 patch. Next, I need to apply the PSU patch and then do the upgrade.
    I am pasting the alert log errors here. Please advice on what I need to do.
    I see these errors from the day I created the database -
    alter database "progdev" open resetlogs
    RESETLOGS after incomplete recovery UNTIL CHANGE 844220
    Errors in file /opt/oracle/diag/rdbms/progdev/progdev/trace/progdev_ora_29547.trc:
    z00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: '/oravol00/oradata/progdev/redo01.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    2010-03-11 14:23:24.757000 -06:00
    Errors in file /opt/oracle/diag/rdbms/progdev/progdev/trace/progdev_ora_29547.trc:
    ORA-00313: open failed for members of log group 2 of thread 1
    ORA-00312: online log 2 thread 1: '/oravol00/oradata/progdev/redo02.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    2010-03-11 14:23:27.729000 -06:00
    And these from when I tried to do the patch install -
    Shutting down instance (immediate)
    License high water mark = 71
    ORA-1089 : opidrv aborting process unknown ospid (1452_47151230037104)
    2010-03-12 16:20:31.653000 -06:00
    All dispatchers and shared servers shutdown
    2010-03-12 16:20:33.732000 -06:00
    ALTER DATABASE CLOSE NORMAL
    SMON: disabling tx recovery
    SMON: disabling cache recovery
    2010-03-12 16:20:34.730000 -06:00
    Shutting down archive processes
    Archiving is disabled
    Archive process shutdown avoided: 0 active
    Thread 1 closed at log sequence 4
    Successful close of redo thread 1
    2010-03-12 16:20:48.060000 -06:00
    Completed: ALTER DATABASE CLOSE NORMAL
    ALTER DATABASE DISMOUNT
    Completed: ALTER DATABASE DISMOUNT
    ARCH: Archival disabled due to shutdown: 1089
    Shutting down archive processes
    Archiving is disabled
    Archive process shutdown avoided: 0 active
    2010-03-12 16:20:49.267000 -06:00
    ARCH: Archival disabled due to shutdown: 1089
    Shutting down archive processes
    Archiving is disabled
    Archive process shutdown avoided: 0 active
    Stopping background process VKTM:
    2010-03-12 16:20:58.416000 -06:00
    System State dumped to trace file /opt/oracle/diag/rdbms/progdev/progdev/trace/progdev_ora_10281.trc
    2010-03-12 16:20:59.757000 -06:00
    Instance shutdown complete
    2010-03-12 17:03:02.814000 -06:00
    Adjusting the default value of parameter parallel_max_servers
    from 160 to 135 due to the value of parameter processes (150)
    Starting ORACLE instance (normal)
    2010-03-12 17:03:04.837000 -06:00
    LICENSE_MAX_SESSION = 0
    LICENSE_SESSIONS_WARNING = 0
    Shared memory segment for instance monitoring created
    Picked latch-free SCN scheme 3
    2010-03-12 17:03:08.261000 -06:00
    Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
    Autotune of undo retention is turned on.
    IMODE=BR
    ILAT =18
    LICENSE_MAX_USERS = 0
    SYS auditing is disabled
    Starting up ORACLE RDBMS Version: 11.1.0.7.0.
    Using parameter settings in server-side spfile /opt/oracle/product/11.1.0/dev/dbs/spfileprogdev.ora
    System parameters with non-default values:
    processes = 150
    memory_target = 9664M
    control_files = "/oravol00/oradata/progdev/control01.ctl"
    control_files = "/oravol00/oradata/progdev/control02.ctl"
    control_files = "/oravol00/oradata/progdev/control03.ctl"
    db_block_size = 8192
    compatible = "11.1.0.0.0"
    db_recovery_file_dest = "/opt/oracle/flash_recovery_area"
    db_recovery_file_dest_size= 2G
    undo_tablespace = "UNDOTBS1"
    remote_login_passwordfile= "EXCLUSIVE"
    db_domain = ""
    dispatchers = "(PROTOCOL=TCP) (SERVICE=progdevXDB)"
    audit_file_dest = "/opt/oracle/admin/progdev/adump"
    audit_trail = "DB"
    db_name = "progdev"
    open_cursors = 300
    diagnostic_dest = "/opt/oracle"
    PMON started with pid=2, OS id=26304
    VKTM started with pid=3, OS id=26306 at elevated priority
    VKTM running at (20)ms precision
    DIAG started with pid=4, OS id=26310
    DBRM started with pid=5, OS id=26312
    PSP0 started with pid=6, OS id=26314
    DIA0 started with pid=7, OS id=26316
    MMAN started with pid=8, OS id=26318
    DBW0 started with pid=9, OS id=26320
    DBW1 started with pid=10, OS id=26322
    LGWR started with pid=11, OS id=26324
    CKPT started with pid=12, OS id=26326
    SMON started with pid=13, OS id=26328
    RECO started with pid=14, OS id=26330
    MMON started with pid=15, OS id=26332
    starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
    MMNL started with pid=16, OS id=26334
    starting up 1 shared server(s) ...
    ORACLE_BASE from environment = /opt/oracle
    ALTER DATABASE MOUNT
    2010-03-12 17:03:12.994000 -06:00
    Errors in file /opt/oracle/diag/rdbms/progdev/progdev/trace/progdev_mman_26318.trc:
    ORA-27103: internal error
    Linux-x86_64 Error: 17: File exists
    Additional information: -1
    Additional information: 1
    MMAN (ospid: 26318): terminating the instance due to error 27103
    ORA-1092 : opitsk aborting process
    Instance terminated by MMAN, pid = 26318
    2010-03-12 17:12:46.811000 -06:00
    Adjusting the default value of parameter parallel_max_servers
    from 160 to 135 due to the value of parameter processes (150)
    Starting ORACLE instance (normal)
    2010-03-12 17:12:48.769000 -06:00
    LICENSE_MAX_SESSION = 0
    LICENSE_SESSIONS_WARNING = 0
    Picked latch-free SCN scheme 3
    2010-03-12 17:12:51.909000 -06:00
    Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
    Autotune of undo retention is turned on.
    IMODE=BR
    ILAT =18
    LICENSE_MAX_USERS = 0
    SYS auditing is disabled
    Starting up ORACLE RDBMS Version: 11.1.0.7.0.
    Using parameter settings in server-side spfile /opt/oracle/product/11.1.0/dev/dbs/spfileprogdev.ora
    System parameters with non-default values:
    processes = 150
    memory_target = 9664M
    control_files = "/oravol00/oradata/progdev/control01.ctl"
    control_files = "/oravol00/oradata/progdev/control02.ctl"
    control_files = "/oravol00/oradata/progdev/control03.ctl"
    db_block_size = 8192
    compatible = "11.1.0.0.0"
    db_recovery_file_dest = "/opt/oracle/flash_recovery_area"
    db_recovery_file_dest_size= 2G
    undo_tablespace = "UNDOTBS1"
    remote_login_passwordfile= "EXCLUSIVE"
    db_domain = ""
    dispatchers = "(PROTOCOL=TCP) (SERVICE=progdevXDB)"
    audit_file_dest = "/opt/oracle/admin/progdev/adump"
    audit_trail = "DB"
    db_name = "progdev"
    open_cursors = 300
    diagnostic_dest = "/opt/oracle"
    PMON started with pid=2, OS id=28723
    VKTM started with pid=3, OS id=28725 at elevated priority
    VKTM running at (20)ms precision
    DIAG started with pid=4, OS id=28729
    DBRM started with pid=5, OS id=28731
    PSP0 started with pid=6, OS id=28733
    DIA0 started with pid=7, OS id=28735
    MMAN started with pid=8, OS id=28737
    DBW0 started with pid=9, OS id=28739
    DBW1 started with pid=10, OS id=28741
    LGWR started with pid=11, OS id=28743
    CKPT started with pid=12, OS id=28745
    SMON started with pid=13, OS id=28747
    RECO started with pid=14, OS id=28749
    MMON started with pid=15, OS id=28751
    starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
    MMNL started with pid=16, OS id=28753
    starting up 1 shared server(s) ...
    ORACLE_BASE from environment = /opt/oracle
    ALTER DATABASE MOUNT
    2010-03-12 17:12:55.989000 -06:00
    Errors in file /opt/oracle/diag/rdbms/progdev/progdev/trace/progdev_mman_28737.trc:
    ORA-27103: internal error
    Linux-x86_64 Error: 17: File exists
    Additional information: -1
    Additional information: 1
    MMAN (ospid: 28737): terminating the instance due to error 27103
    ORA-1092 : opitsk aborting process
    Instance terminated by MMAN, pid = 28737
    2010-03-12 21:09:24.016000 -06:00
    Adjusting the default value of parameter parallel_max_servers
    from 160 to 135 due to the value of parameter processes (150)
    Starting ORACLE instance (normal)
    2010-03-12 21:09:25.986000 -06:00
    LICENSE_MAX_SESSION = 0
    LICENSE_SESSIONS_WARNING = 0
    Picked latch-free SCN scheme 3
    2010-03-12 21:09:29.084000 -06:00
    Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
    Autotune of undo retention is turned on.
    IMODE=BR
    ILAT =18
    LICENSE_MAX_USERS = 0
    SYS auditing is disabled
    Starting up ORACLE RDBMS Version: 11.1.0.7.0.
    Using parameter settings in server-side spfile /opt/oracle/product/11.1.0/dev/dbs/spfileprogdev.ora
    System parameters with non-default values:
    processes = 150
    memory_target = 9664M
    control_files = "/oravol00/oradata/progdev/control01.ctl"
    control_files = "/oravol00/oradata/progdev/control02.ctl"
    control_files = "/oravol00/oradata/progdev/control03.ctl"
    db_block_size = 8192
    compatible = "11.1.0.0.0"
    db_recovery_file_dest = "/opt/oracle/flash_recovery_area"
    db_recovery_file_dest_size= 2G
    undo_tablespace = "UNDOTBS1"
    remote_login_passwordfile= "EXCLUSIVE"
    db_domain = ""
    dispatchers = "(PROTOCOL=TCP) (SERVICE=progdevXDB)"
    audit_file_dest = "/opt/oracle/admin/progdev/adump"
    audit_trail = "DB"
    db_name = "progdev"
    open_cursors = 300
    diagnostic_dest = "/opt/oracle"
    PMON started with pid=2, OS id=19640
    VKTM started with pid=3, OS id=19642 at elevated priority
    VKTM running at (20)ms precision
    DIAG started with pid=4, OS id=19646
    DBRM started with pid=5, OS id=19648
    PSP0 started with pid=6, OS id=19650
    DIA0 started with pid=7, OS id=19652
    MMAN started with pid=8, OS id=19654
    DBW0 started with pid=9, OS id=19657
    DBW1 started with pid=10, OS id=19659
    LGWR started with pid=11, OS id=19661
    CKPT started with pid=12, OS id=19663
    SMON started with pid=13, OS id=19665
    RECO started with pid=14, OS id=19667
    MMON started with pid=15, OS id=19669
    starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
    MMNL started with pid=16, OS id=19671
    starting up 1 shared server(s) ...
    ORACLE_BASE from environment = /opt/oracle
    ALTER DATABASE MOUNT
    2010-03-12 21:09:33.214000 -06:00
    Errors in file /opt/oracle/diag/rdbms/progdev/progdev/trace/progdev_mman_19654.trc:
    ORA-27103: internal error
    Linux-x86_64 Error: 17: File exists
    Additional information: -1
    Additional information: 1
    MMAN (ospid: 19654): terminating the instance due to error 27103
    2010-03-12 21:09:34.222000 -06:00
    Instance terminated by MMAN, pid = 19654
    2010-03-12 21:10:15.072000 -06:00
    Adjusting the default value of parameter parallel_max_servers
    from 160 to 135 due to the value of parameter processes (150)
    Starting ORACLE instance (normal)
    2010-03-12 21:10:17.067000 -06:00
    LICENSE_MAX_SESSION = 0
    LICENSE_SESSIONS_WARNING = 0
    Picked latch-free SCN scheme 3
    2010-03-12 21:10:20.227000 -06:00
    Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
    Autotune of undo retention is turned on.
    IMODE=BR
    ILAT =18
    LICENSE_MAX_USERS = 0
    SYS auditing is disabled
    Starting up ORACLE RDBMS Version: 11.1.0.7.0.
    Using parameter settings in server-side spfile /opt/oracle/product/11.1.0/dev/dbs/spfileprogdev.ora
    System parameters with non-default values:
    processes = 150
    memory_target = 9664M
    control_files = "/oravol00/oradata/progdev/control01.ctl"
    control_files = "/oravol00/oradata/progdev/control02.ctl"
    control_files = "/oravol00/oradata/progdev/control03.ctl"
    db_block_size = 8192
    compatible = "11.1.0.0.0"
    db_recovery_file_dest = "/opt/oracle/flash_recovery_area"
    db_recovery_file_dest_size= 2G
    undo_tablespace = "UNDOTBS1"
    remote_login_passwordfile= "EXCLUSIVE"
    db_domain = ""
    dispatchers = "(PROTOCOL=TCP) (SERVICE=progdevXDB)"
    audit_file_dest = "/opt/oracle/admin/progdev/adump"
    audit_trail = "DB"
    db_name = "progdev"
    open_cursors = 300
    diagnostic_dest = "/opt/oracle"
    PMON started with pid=2, OS id=20310
    VKTM started with pid=3, OS id=20312 at elevated priority
    VKTM running at (20)ms precision
    DIAG started with pid=4, OS id=20316
    DBRM started with pid=5, OS id=20318
    PSP0 started with pid=6, OS id=20320
    DIA0 started with pid=7, OS id=20322
    MMAN started with pid=8, OS id=20324
    DBW0 started with pid=9, OS id=20326
    DBW1 started with pid=10, OS id=20328
    LGWR started with pid=11, OS id=20330
    CKPT started with pid=12, OS id=20332
    SMON started with pid=13, OS id=20334
    RECO started with pid=14, OS id=20336
    MMON started with pid=15, OS id=20338
    starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
    MMNL started with pid=16, OS id=20340
    starting up 1 shared server(s) ...
    ORACLE_BASE from environment = /opt/oracle
    ALTER DATABASE MOUNT
    2010-03-12 21:10:24.263000 -06:00
    Errors in file /opt/oracle/diag/rdbms/progdev/progdev/trace/progdev_mman_20324.trc:
    ORA-27103: internal error
    Linux-x86_64 Error: 17: File exists
    Additional information: -1
    Additional information: 1
    MMAN (ospid: 20324): terminating the instance due to error 27103
    ORA-1092 : opitsk aborting process
    Instance terminated by MMAN, pid = 20324
    2010-03-12 22:02:04.524000 -06:00
    Adjusting the default value of parameter parallel_max_servers
    from 160 to 135 due to the value of parameter processes (150)
    Starting ORACLE instance (normal)
    2010-03-12 22:02:06.715000 -06:00
    LICENSE_MAX_SESSION = 0
    LICENSE_SESSIONS_WARNING = 0
    Picked latch-free SCN scheme 3
    2010-03-12 22:02:10.003000 -06:00
    Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
    Autotune of undo retention is turned on.
    IMODE=BR
    ILAT =18
    LICENSE_MAX_USERS = 0
    SYS auditing is disabled
    Starting up ORACLE RDBMS Version: 11.1.0.7.0.
    Using parameter settings in server-side spfile /opt/oracle/product/11.1.0/dev/dbs/spfileprogdev.ora
    System parameters with non-default values:
    processes = 150
    memory_target = 9664M
    control_files = "/oravol00/oradata/progdev/control01.ctl"
    control_files = "/oravol00/oradata/progdev/control02.ctl"
    control_files = "/oravol00/oradata/progdev/control03.ctl"
    db_block_size = 8192
    compatible = "11.1.0.0.0"
    db_recovery_file_dest = "/opt/oracle/flash_recovery_area"
    db_recovery_file_dest_size= 2G
    undo_tablespace = "UNDOTBS1"
    remote_login_passwordfile= "EXCLUSIVE"
    db_domain = ""
    dispatchers = "(PROTOCOL=TCP) (SERVICE=progdevXDB)"
    audit_file_dest = "/opt/oracle/admin/progdev/adump"
    audit_trail = "DB"
    db_name = "progdev"
    open_cursors = 300
    diagnostic_dest = "/opt/oracle"
    PMON started with pid=2, OS id=32493
    VKTM started with pid=3, OS id=32495 at elevated priority
    VKTM running at (20)ms precision
    DIAG started with pid=4, OS id=32499
    DBRM started with pid=5, OS id=32501
    PSP0 started with pid=6, OS id=32503
    DIA0 started with pid=7, OS id=32505
    MMAN started with pid=8, OS id=32507
    DBW0 started with pid=9, OS id=32509
    DBW1 started with pid=10, OS id=32511
    LGWR started with pid=11, OS id=32513
    CKPT started with pid=12, OS id=32515
    SMON started with pid=13, OS id=32517
    RECO started with pid=14, OS id=32519
    MMON started with pid=15, OS id=32521
    starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
    MMNL started with pid=16, OS id=32523
    starting up 1 shared server(s) ...
    ORACLE_BASE from environment = /opt/oracle
    2010-03-12 22:02:11.216000 -06:00
    ALTER DATABASE MOUNT
    2010-03-12 22:02:14.385000 -06:00
    Errors in file /opt/oracle/diag/rdbms/progdev/progdev/trace/progdev_mman_32507.trc:
    ORA-27103: internal error
    Linux-x86_64 Error: 17: File exists
    Additional information: -1
    Additional information: 1
    MMAN (ospid: 32507): terminating the instance due to error 27103
    ORA-1092 : opitsk aborting process
    Instance terminated by MMAN, pid = 32507
    oracle@<progdev>:/home/oracle $
    Thanks,
    Anu

Maybe you are looking for

  • ABAP Inbound Proxy Error !

    Hi , I am forwarding Vendor Data from SRM EBP to SUS with the predifined proxies given by SAP, bu t i get below error when it reaches SUS System.Message processing both in SAP EBP and SAP XI is fine.   <?xml version="1.0" encoding="UTF-8" standalone=

  • Adobe Reader Update causes weird printing issues

    I recently updated my Adobe Reader to Adobe Reader X. I have a Toshiba with Windows 7 68-bit I believe. After updating to Reader X, I noticed that when I go to print a document, the print settings in Adobe are default set to Print on both sides. I wa

  • Subvi execution/closing

    Hi all, I'm currently working on a project using LV7.1 that invloves the use of multiple subvi's linked back to the top level VI, acting as a main menu screen. However, I am running into a spot of bother when attempting to close a particular subvi pa

  • Invoice Smartform  Printing Multiple Line Items

    Hi Floks, I have a billing Document with multiple items like labor ,material,miscellaneous and more .. i want to print all line items description and data also in smartform . It's possible to print all this requirement in Normal Windows or  How is it

  • Search resources based on created date

    Hi, I am unable to search the resources based on creation date. I used the code as follows. sqb = new SearchQueryListBuilder(); Timestamp ts3 = new Timestamp(d3.getTime()); String searchCreDt = "default:created(value>"ts3.toString()")"; sqb.setSelect