AF grouping element that renders as a DIV?

Hello,
Is there an ADF component similar to an af:panelGroup that renders as a DIV rather than a SPAN? I need to explicitly set the width, and you cannot set width on a "span" element. I need to enclose more ADF components inside this grouping(in particular, af:commandLink"), which is why I'm under the impression that it has to be an ADF component enclosing it.. (I'm trying not to use an afh:tableLayout to do this!)
Any suggestions?
Thanks in advance,
- Visser

Alright I've thrown in the towel, wrote a custom tag to act as a DIV, and it works swell. Here is the URL to a tutorial that shows exactly how to do it:
http://www.it-eye.nl/weblog/2006/04/25/creating-a-jsf-div-component/
For anyone else searching the forums with the seemingly unsolved question of how to make the width of a column in an ADF table fixed, you can:
1. Integrate the custom DIV tag implementing the styleClass property as shown in the above tutorial
2. Set the width of the DIV element to the size you want the column to be
3. Set the CSS property "overflow-x" to be hidden, or scroll, or whatever suits your fancy
Then all you have to do is make sure the column width is set to less than what you set the width of your DIV and it will no longer stretch to the content of the cell!
I hope that helps someone, thanks for everyone's input into this problem.
Branden

Similar Messages

  • Problem with minimal height of components that renders as DIV in FF

    I noticed this when I wanted to put af:spacer with height less then 10px.
    In panelGroupLayout (property layout set to vertical) I wanted to set vertical spacing
    between images to 5px. af:spacer that renders as img (width:1px / height:5px) was in DIV
    which hed height of minimal 13px.
    In IE7 everything is OK, but IE7 is not an option.

    SOVIET,
    In the latest build using FireFox 2.0.0.6 the af:spacer renders as follows which is as it is designed to do. Therefore, the issue is no longer present within the product. Thanks for your tremendous attention to detail.
    Regards,
    Ric
    For a height of 5 and width of 10 the af:spacer renders:
    <div><img id="spacer1" src="/testcase-testcase-context-root/adf/images/t.gif" alt="" width="10" height="5"/></div>For a height and width of 10 the af:spacer renders:
    <div><img id="spacer1" src="/testcase-testcase-context-root/adf/images/t.gif" alt="" width="10" height="10"/></div>For a height of 5 and width of 0 the af:spacer renders:
    <div><img id="spacer1" src="/testcase-testcase-context-root/adf/images/t.gif" alt="" width="0" height="5"/></div>For a height 10 and width of 0 the af:spacer renders:
    <div><img id="spacer1" src="/testcase-testcase-context-root/adf/images/t.gif" alt="" width="0" height="10"/></div>

  • Display grouping elements r repective page footers in hyp:IR STUDIO

    Hi All ,
    I am facing a problem with Hyperion IR Studio at the time of display grouping elements in receptive page footers.
    eg: say I have a group 'A' and its corresponding elements are like A1,A2,A3....
    If query(from dashboard) for report related to Group 'A'..My report shows the data related to all its elements(A1,A2,...).I need to show these grouping elements in the page footer on their corresponding pages, for example, my report has generated with first 4 pages related to Grouping element 'A1' and next two pages(5th,6th) for grouping element 'A2'..here I need to show 'A1' in the page footer on first 4 pages and 'A2' on 5th & 6th pages and like-wise.
    Is there any possibility that we can show grouping elements in their receptive page footers...
    Hyperion :-
    Version : IR reporting studio 11.1.1.3
    Thanks in Advance,
    Srini

    hey, I just realised, that you have the same problem as me, though mine is a studio xps1340 with a 9500M.
    Did you make any progress in configuring your xorg.conf or anything else? Please say yes...

  • Grouping elements on a slide

    I am using Captivate v4.
    Is it possible to select different elements placed onto a slide and create a "group" - as is possible in PowerPoint ?
    For example - I have created an magnified view of an area visible on the slide itself. I have placed around the magnified view a highlight box and lines that direct the user to the location of the smaller item on the main image on the slide. In total I have 5 elements that make up my "magnified" view and it would be good to turn the whole magnified view into a group so their timings etc could be done just once, not for each seperate element that make up the magnified view.
    Here's hoping.....
    Noel

    Sorry.  This is not something that Captivate can do as yet.
    You'll be happy to know that others feel as you do that this would be a useful addition to the feature set.
    Feel free to log and enhancement request for it.

  • How to add an attribute to "group" element in the DataTemplate dataStructur

    Hi,
    I want to add an attribute to the group element in the dataStructure section of DataTemplate. I want my output XML file to look like:
    <G_EMP xmlns:xsd="http://www.w3.org">
    <ENAME>John</ENAME>
    </G_EMP>
    This can be done in Oracle Reports 6i by setting a value to the XMLTag attribute in the property pallette of G_EMP group in the report. Please let me know if there is a way to do the same in the Data Template.
    So far I've observed only three attibutes that can be used with group element (name,dataType,source). Is there any other attribute that I can use to get the afore mentioned XML structure.

    Moved to the LiveCycle Designer forum: http://forums.adobe.com/community/livecycle/livecycle_modules_and_development_tools/livecy cle_designer_es?view=discussions

  • Problem in repetetion of the value of parent group element in each PDFpage

    I am using data template in BI PUB. I have table containing Region_Name , Sales_Rep_Name and amount. I need to show the region_name(parent group element) on the top(not in header) of the next and subsequent pages . under same region_name if sales_rep_name(child group element) is large enough not to fit in a single page, then same region_name should appear in the next page. But this name is not repeting in every page of the generated PDF.
    QUERY: SELECT region_name,sales_rep_name,SUM(amount) amount FROM edwods_bipub_test
    GROUP BY region_name,sales_rep_name
    ORDER BY region_name,sales_rep_name
    Data Structure for the above query: <dataStructure>
              <group name="g_region" dataType="varchar2" source="Q_weekly_summary_by_salesrep">
                   <element name="region_name" dataType="varchar2" value="REGION_NAME"/>
                   <group name="g_sales_rep" dataType="varchar2" source="Q_weekly_summary_by_salesrep">
                        <element name="sales_rep_name" dataType="varchar2" value="sales_rep_name"/>
                        <element name="amount" dataType="number" value="amount"/>
                   </group>
              </group>
         </dataStructure>
    Please help me at [email protected]

    create a formula column
    function Cf_clientaddressformula
    return varchar
    is
    clientaddress VarChar2(1000);
    begin
    Select DeCode(:Address1, Null, Null, :Address1)||
    DeCode(:AddressN, Null, Null, Chr(10)||:AddressN)||
    DeCode(:City, Null, Null, Chr(10)||:City)||
    DeCode(:State, Null, Null, Chr(10)||:State)
    DeCode(:Country, Null, Null, Chr(10)||:Country)
    DeCode(:PostalCode, Null, Null, Chr(10)||:PostalCode)
    Into ClientAddress
    From Dual;
    ClientAddress := LTrim(RTrim(ClientAddress,Chr(10)),Chr(10));
    return(ClientAddress);
    End;
    assign this cf to the address field in your report and set that field "Vertical Elasticity" to "Variable"
    Hope this will solve your problem.
    Sumanth

  • Group elements, price classes etc

    Hi "U" guru's,
    I'm trying to understand the following config aspects of DM. Can someone help me with understanding of each point and what would be the values related to this and why these will be used?
    1)Group elements (register grp, command grp) for device category->what are the different possible values and Use?
    2)Price classes and price levels in the billing master data in contract billing-->what are the different possible values and Use?
    3)Reference material for creating material/device category->what are the different possible values and Use?
    4)What are functional and cosntruction classes? e.g?
    5)Defined different manufacturers of devices and installations---> Is this pure customization in each project implementations? or SAP has std values?
    Thanks
    raj

    Hi Raj,
    1)There are following grouping:
    a. Register groups:- Group of registers that belong to one or more devices or device categories.e.g. no of registers to the device i.e. 0,1,2,4..
    b.Grouping together of several commands in a logical way. Example: for street lighting, the command group is made up of the commands turn on, diminish power, and turn off.
    c.Group of interfaces of one or more device categories or devices. Example: a group of several pulse input points and a modem interface in the case of remote meters.
    2)The Price classes and price levels are Classification of device categories that are treated with respect to price. Example: In conjunction with the price level, the price class is used to determine the rental price.
    3)Reference material for creating material/device category->what are the different possible values and Use?
    4) Construction classes : First summarization level in the classification of device categories.Several similar device categories can be grouped into one construction class.
    The functional classes are Second summarization level in the classification of device categories. e.g. Several device categories or construction classes (each containing several device categories) can be grouped into one function class.
    With regards,
    Sunil

  • List items as grouped elements

    Hi,
    In 'Select List Item' , I want to display list items as grouped elements. Assume that grouping the child items based on its master code.
    Eg: [ Fruits ]
    Apple
    Orange
    Goa
    [ Animals ]
    Tiger
    Lion
    Elephant
    [ Birds ]
    ...... etc
    How can I do it?
    Regards
    Mohan

    Mohan wrote:
    In 'Select List Item' , I want to display list items as grouped elements. Assume that grouping the child items based on its master code.
    Eg: [ Fruits ]
    Apple
    Orange
    Goa
    [ Animals ]
    Tiger
    Lion
    Elephant
    [ Birds ]
    ...... etc
    How can I do it?The select list item must generate HTML <tt>optgroup</tt> elements, via an item plug-in or some other technique, e.g.
    {thread:id=1115902}
    {message:id=4516761}

  • I am new to pages and want to know how to link elements together to create one unified element that I can then duplicate several times on the same page?

    I am new to pages and want to know how to link elements together to create one unified element that I can then duplicate several times on the same page?

    I think you are talking about grouping objects.
    1. They must all be floating objects
    2. Command click on each in turn
    Menu > Arrange > Group
    Peter

  • Failed to get hierarchy group elements from middleware

    When iam configuring the Mobile Infrastructure and clicked on Hierarchy Grouping i got the following error.
    Error:Failed to get hierarchy group elements from middleware. Reason: Could not connect to middleware
    Could anyone tell meaning the above statement and why it is occuring.
    Secondly when iam trying to start the MI Webconsole from the below URL, I was getting Page Cannot be Displayed Error.
    https://server:50300/me/WebConsole/login. Can anyone tell why this error is coming.

    Hi Siva,
    Sorry for the delay reply. I have a few things to ask.
    First my problem is not solved, still iam getting the error.
    Secondly, i have done the configuration for Mobile Administrator, but during the configuration When deploying the JRA File (Standard Installation and Installation of Cluster both needs to be done or Standard Installation is sufficient).
    Not only that after configuring the Mobile Administrator do i need configure the CCMS also, if so if i configure the CCMS would my error be resolved.
    My User has all the required Authorizations but why am i getting the error i could not able to trace out
    Lastly do i need to configure the Mobile Applications part also.
    I need to have a quick reply on this. Can anyone help me in this issue.

  • Vectors shapes dissapear or group elements are mooved to another coordinates

    A month ago, I experiment some bugs on fireworks. There are shapes, that dissapear, or group elements thah disappear and when you try to select his layer, the shape appears in another coordiantes, and it's impossible to select. Mask boxes change you height by 1px and it's impossible to modify. The rounded shapes are deformed, like someone move the paths to the right.
    I have a lot of desings mades with fireworks, and many files become corrupt, with this case of bugs that I've mentioned at the beginning.
    A friend that also have fireworks has proved the same file, and it is perfect, but if I open the file, happens all this thing that explain on top.
    What is happening?@

    1.) forget "Vector" if you're talking about (modern) Java Code. You most likely want to use a implementation of List instead (usually ArrayList or LinkedList), Vector is a legacy class and should usually not be used in new code.
    2.) You could keep everything in XML all the time, for this you would use the DOM tree of your document. In my opinion that's usually too much hassle, as you'd have to convert each data access.
    3.) Do you mean to use the list to store the objects or the properties of the objects?
    4.) A standalone application is no reason not to use a database. HSQLDB provides almost everything you need from a database without having to install anything. Of course a XML file might still be the better idea, but you should think about it.
    Good Luck

  • Bee_table element gets rendered multiple times

    Hi Everybody,
    i'm using a bee_table that holds a tableview an a treeview. For the tableview I implemented an iterator.
    Now the problem is, everytime the bee_table with its elements is rendered to string another table occurs on screen.....
    When i don't use the iterator this doesn't happen!
    Any comments on this are appreciated!
    Michael

    Okay
    I think it's not a problem with the bee_table, there is a problem with the iterator itself. Now, I instantiate the tableview again everytime it comes to rendering. So this is sufficient solution for me.
    Over and Out!
    Michael

  • VARRAY STORE AS on xsd:group elements

    Hi,
    I have an XSD that includes several other XSD's. In the "root" XSD a xsd:group is included (<xsd:group ref="someDefinition" ....> ) inside one of the elements.
    My problem is that I can't figure out how to create a table for this on the form:
    CREATE TABLE WELL OF XMLTYPE
    XMLSCHEMA "obj_foo.xsd"
    ELEMENT "foo"
    VARRAY "XMLDATA"."bar"."elementInGroup"
    STORE AS TABLE group_element_table1
    ((PRIMARY KEY (NESTED_TABLE_ID, SYS_NC_ARRAY_INDEX$)))
    The above code gives me "An attempt was made to access a non-existent attribute of an object type"
    Is there a special way to do this, or have I most likely some other error?

    Nice answer, thanks!
    But I still don't get it right. Can it be because of my XSD registration? I would not be surprised :)
    The schemas:
    The object:
    <?xml version="1.0" encoding="WINDOWS-1252"?>
    <xsd:schema elementFormDefault="qualified" attributeFormDefault="unqualified" targetNamespace="http://www.witsml.org/schemas/131" xmlns:witsml="http://www.witsml.org/schemas/131" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xdb="http://xmlns.oracle.com/xdb" xdb:flags="8499" xdb:schemaURL="obj_well.xsd" xdb:schemaOwner="TTUSER" xdb:numProps="7">
      <!--                                                         -->
      <!-- POSC License Agreement
         This file is distributed under the POSC License Agreement at
         http://www.posc.org/about/license.shtml.
         Use of this file constitutes agreement with the POSC License Agreement.
         -->
      <!--                                                         -->
      <xsd:include schemaLocation="cs_documentInfo.xsd"/>
      <xsd:include schemaLocation="grp_well.xsd"/>
      <xsd:include schemaLocation="cs_commonData.xsd"/>
      <xsd:include schemaLocation="cs_customData.xsd"/>
      <xsd:include schemaLocation="attgrp_uid.xsd"/>
      <!--                                                         -->
      <xsd:annotation>
        <xsd:documentation> Well master information that supports the WITSML standard. </xsd:documentation>
      </xsd:annotation>
      <!--                                                         -->
      <xsd:element name="wells" type="witsml:obj_wells" xdb:defaultTable="OBJ_WELL" xdb:propNumber="5008" xdb:global="true" xdb:SQLName="wells" xdb:SQLType="obj_wells786_T" xdb:SQLSchema="TTUSER" xdb:memType="258" xdb:defaultTableSchema="TTUSER">
        <xsd:annotation>
          <xsd:documentation>The WITSML API mandated plural root element which allows
                   multiple singular objects to be sent. The plural name is formed by adding
                   an &quot;s&quot; to the singular name.</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
      <!--                                                         -->
      <xsd:complexType name="obj_wells" xdb:SQLType="obj_wells786_T" xdb:SQLSchema="TTUSER">
        <xsd:sequence>
          <xsd:element name="documentInfo" type="witsml:cs_documentInfo" minOccurs="0" maxOccurs="1" xdb:propNumber="5010" xdb:global="false" xdb:SQLName="documentInfo" xdb:SQLType="cs_documentInfo719_T" xdb:SQLSchema="TTUSER" xdb:memType="258" xdb:MemInline="false" xdb:SQLInline="true" xdb:JavaInline="false">
            <xsd:annotation>
              <xsd:documentation>Information about the XML message instance.  </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
          <xsd:element name="well" type="witsml:obj_well" minOccurs="1" maxOccurs="unbounded" xdb:propNumber="5011" xdb:global="false" xdb:SQLName="well" xdb:SQLType="obj_well785_T" xdb:SQLSchema="TTUSER" xdb:memType="258" xdb:MemInline="false" xdb:SQLInline="true" xdb:JavaInline="false" xdb:SQLCollType="well787_COLL" xdb:SQLCollSchema="TTUSER">
            <xsd:annotation>
              <xsd:documentation>Information about a single well.
                             A well is a unique surface location from which wellbores are drilled
                             into the Earth for the purpose of either (1) finding or producing
                             underground resources; or (2) providing services related to the
                             production of underground resources.  </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
        <xsd:attribute name="version" type="witsml:schemaVersionString" use="required" xdb:propNumber="5009" xdb:global="false" xdb:SQLName="version" xdb:SQLType="VARCHAR2" xdb:memType="1">
          <xsd:annotation>
            <xsd:documentation>Data object schema version.  The fourth level must match the
                        version of the schema constraints (enumerations and XML loader files) that are assumed
                        by the document instance.</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
      </xsd:complexType>
      <!--                                                         -->
      <xsd:complexType name="obj_well" xdb:SQLType="obj_well785_T" xdb:SQLSchema="TTUSER">
        <xsd:sequence>
          <xsd:element name="name" type="witsml:nameString" minOccurs="1" maxOccurs="1" xdb:propNumber="5012" xdb:global="false" xdb:SQLName="name" xdb:SQLType="VARCHAR2" xdb:memType="1" xdb:MemInline="true" xdb:SQLInline="true" xdb:JavaInline="true">
            <xsd:annotation>
              <xsd:documentation>Human recognizable context for the well.  </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
          <xsd:group ref="witsml:grp_well" minOccurs="0" maxOccurs="1">
            <xsd:annotation>
              <xsd:documentation>The non-contextual elements for general well information.</xsd:documentation>
            </xsd:annotation>
          </xsd:group>
          <xsd:element name="commonData" type="witsml:cs_commonData" minOccurs="0" maxOccurs="1" xdb:propNumber="5013" xdb:global="false" xdb:SQLName="commonData" xdb:SQLType="cs_commonData722_T" xdb:SQLSchema="TTUSER" xdb:memType="258" xdb:MemInline="false" xdb:SQLInline="true" xdb:JavaInline="false">
            <xsd:annotation>
              <xsd:documentation>A container element that contains elements that are common to all data
                             objects.  </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
          <xsd:element name="customData" type="witsml:cs_customData" minOccurs="0" maxOccurs="1" xdb:propNumber="5014" xdb:global="false" xdb:SQLName="customData" xdb:SQLType="cs_customData723_T" xdb:SQLSchema="TTUSER" xdb:memType="258" xdb:MemInline="false" xdb:SQLInline="true" xdb:JavaInline="false">
            <xsd:annotation>
              <xsd:documentation>A container element that can contain custom or user defined
                             data elements.</xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
        <xsd:attributeGroup ref="witsml:attgrp_uid">
          <xsd:annotation>
            <xsd:documentation>Unique identifier for the well.  </xsd:documentation>
          </xsd:annotation>
        </xsd:attributeGroup>
      </xsd:complexType>
    </xsd:schema>
    and the group:
    <?xml version="1.0" encoding="WINDOWS-1252"?>
    <xsd:schema elementFormDefault="qualified" attributeFormDefault="unqualified" targetNamespace="http://www.witsml.org/schemas/131" xmlns:witsml="http://www.witsml.org/schemas/131" xmlns:xsd="http://www.w3.org/2001/XMLSchema" version="1.3.1" xmlns:oraxdb="http://xmlns.oracle.com/xdb" oraxdb:flags="8503" oraxdb:schemaURL="grp_well.xsd" oraxdb:schemaOwner="TTUSER" oraxdb:numProps="29">
      <!--                                                         -->
      <!-- POSC License Agreement
         This file is distributed under the POSC License Agreement at
         http://www.posc.org/about/license.shtml.
         Use of this file constitutes agreement with the POSC License Agreement.
         -->
      <!--                                                         -->
      <xsd:include schemaLocation="cs_location.xsd"/>
      <xsd:include schemaLocation="cs_referencePoint.xsd"/>
      <xsd:include schemaLocation="cs_wellCRS.xsd"/>
      <xsd:include schemaLocation="cs_wellDatum.xsd"/>
      <!--                                                         -->
      <xsd:group name="grp_well">
        <xsd:annotation>
          <xsd:documentation>The non-contextual content of a WITSML Well object.</xsd:documentation>
        </xsd:annotation>
        <xsd:sequence>
          <xsd:element name="nameLegal" type="witsml:nameString" minOccurs="0" maxOccurs="1" oraxdb:propNumber="4965" oraxdb:global="false" oraxdb:SQLName="nameLegal" oraxdb:SQLType="VARCHAR2" oraxdb:memType="1" oraxdb:MemInline="true" oraxdb:SQLInline="true" oraxdb:JavaInline="true">
            <xsd:annotation>
              <xsd:documentation>Legal name of the well.  </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
          <xsd:element name="numLicense" type="witsml:nameString" minOccurs="0" maxOccurs="1" oraxdb:propNumber="4966" oraxdb:global="false" oraxdb:SQLName="numLicense" oraxdb:SQLType="VARCHAR2" oraxdb:memType="1" oraxdb:MemInline="true" oraxdb:SQLInline="true" oraxdb:JavaInline="true">
            <xsd:annotation>
              <xsd:documentation>License number of the well.  </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
          <xsd:element name="numGovt" type="witsml:nameString" minOccurs="0" maxOccurs="1" oraxdb:propNumber="4967" oraxdb:global="false" oraxdb:SQLName="numGovt" oraxdb:SQLType="VARCHAR2" oraxdb:memType="1" oraxdb:MemInline="true" oraxdb:SQLInline="true" oraxdb:JavaInline="true">
            <xsd:annotation>
              <xsd:documentation>Government assigned well number.  </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
          <xsd:element name="dTimLicense" type="witsml:timestamp" minOccurs="0" maxOccurs="1" oraxdb:propNumber="4968" oraxdb:global="false" oraxdb:SQLName="dTimLicense" oraxdb:SQLType="TIMESTAMP" oraxdb:memType="180" oraxdb:MemInline="true" oraxdb:SQLInline="true" oraxdb:JavaInline="true">
            <xsd:annotation>
              <xsd:documentation>Date and time license  was issued.  </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
          <xsd:element name="field" type="witsml:nameString" minOccurs="0" maxOccurs="1" oraxdb:propNumber="4969" oraxdb:global="false" oraxdb:SQLName="field" oraxdb:SQLType="VARCHAR2" oraxdb:memType="1" oraxdb:MemInline="true" oraxdb:SQLInline="true" oraxdb:JavaInline="true">
            <xsd:annotation>
              <xsd:documentation>Name of the field in which the well is located.  </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
          <xsd:element name="country" type="witsml:str32" minOccurs="0" maxOccurs="1" oraxdb:propNumber="4970" oraxdb:global="false" oraxdb:SQLName="country" oraxdb:SQLType="VARCHAR2" oraxdb:memType="1" oraxdb:MemInline="true" oraxdb:SQLInline="true" oraxdb:JavaInline="true">
            <xsd:annotation>
              <xsd:documentation>Country in which well is located.  </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
          <xsd:element name="state" type="witsml:str32" minOccurs="0" maxOccurs="1" oraxdb:propNumber="4971" oraxdb:global="false" oraxdb:SQLName="state" oraxdb:SQLType="VARCHAR2" oraxdb:memType="1" oraxdb:MemInline="true" oraxdb:SQLInline="true" oraxdb:JavaInline="true">
            <xsd:annotation>
              <xsd:documentation>State or province in which well is located.  </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
          <xsd:element name="county" type="witsml:str32" minOccurs="0" maxOccurs="1" oraxdb:propNumber="4972" oraxdb:global="false" oraxdb:SQLName="county" oraxdb:SQLType="VARCHAR2" oraxdb:memType="1" oraxdb:MemInline="true" oraxdb:SQLInline="true" oraxdb:JavaInline="true">
            <xsd:annotation>
              <xsd:documentation>County in which the well is located.  </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
          <xsd:element name="region" type="witsml:str32" minOccurs="0" maxOccurs="1" oraxdb:propNumber="4973" oraxdb:global="false" oraxdb:SQLName="region" oraxdb:SQLType="VARCHAR2" oraxdb:memType="1" oraxdb:MemInline="true" oraxdb:SQLInline="true" oraxdb:JavaInline="true">
            <xsd:annotation>
              <xsd:documentation>Geo-political region.  </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
          <xsd:element name="district" type="witsml:str32" minOccurs="0" maxOccurs="1" oraxdb:propNumber="4974" oraxdb:global="false" oraxdb:SQLName="district" oraxdb:SQLType="VARCHAR2" oraxdb:memType="1" oraxdb:MemInline="true" oraxdb:SQLInline="true" oraxdb:JavaInline="true">
            <xsd:annotation>
              <xsd:documentation>Geo-political district name.  </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
          <xsd:element name="block" type="witsml:str32" minOccurs="0" maxOccurs="1" oraxdb:propNumber="4975" oraxdb:global="false" oraxdb:SQLName="block" oraxdb:SQLType="VARCHAR2" oraxdb:memType="1" oraxdb:MemInline="true" oraxdb:SQLInline="true" oraxdb:JavaInline="true">
            <xsd:annotation>
              <xsd:documentation>Block name in which well is located.  </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
          <xsd:element name="timeZone" type="witsml:timeZone" minOccurs="0" maxOccurs="1" oraxdb:propNumber="4976" oraxdb:global="false" oraxdb:SQLName="timeZone" oraxdb:SQLType="VARCHAR2" oraxdb:memType="1" oraxdb:MemInline="true" oraxdb:SQLInline="true" oraxdb:JavaInline="true">
            <xsd:annotation>
              <xsd:documentation>The time zone in which well is located. 
                             It is the deviation in hours and minutes from UTC.
                             This should be the normal time zone at the well and not a seasonally
                             adjusted value such as daylight savings time.
                             While the time zone is optional in a date time value, it is strongly
                             advised that the zone always be specified in each date time value.
                             The time zone in a date time value may use seasonally adjusted values.</xsd:documentation>
            </xsd:annotation>
          </xsd:element>
          <xsd:element name="operator" type="witsml:nameString" minOccurs="0" maxOccurs="1" oraxdb:propNumber="4977" oraxdb:global="false" oraxdb:SQLName="operator" oraxdb:SQLType="VARCHAR2" oraxdb:memType="1" oraxdb:MemInline="true" oraxdb:SQLInline="true" oraxdb:JavaInline="true">
            <xsd:annotation>
              <xsd:documentation>Operator company name.  </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
          <xsd:element name="operatorDiv" type="witsml:nameString" minOccurs="0" maxOccurs="1" oraxdb:propNumber="4978" oraxdb:global="false" oraxdb:SQLName="operatorDiv" oraxdb:SQLType="VARCHAR2" oraxdb:memType="1" oraxdb:MemInline="true" oraxdb:SQLInline="true" oraxdb:JavaInline="true">
            <xsd:annotation>
              <xsd:documentation>Division of operator company.  </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
          <xsd:element name="pcInterest" type="witsml:dimensionlessMeasure" minOccurs="0" maxOccurs="1" oraxdb:propNumber="4979" oraxdb:global="false" oraxdb:SQLName="pcInterest" oraxdb:SQLType="dimensionlessMeasure688_T" oraxdb:SQLSchema="TTUSER" oraxdb:memType="258" oraxdb:MemInline="false" oraxdb:SQLInline="true" oraxdb:JavaInline="false">
            <xsd:annotation>
              <xsd:documentation>Interest for Operator. Commonly in percent.  </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
          <xsd:element name="numAPI" type="witsml:str32" minOccurs="0" maxOccurs="1" oraxdb:propNumber="4980" oraxdb:global="false" oraxdb:SQLName="numAPI" oraxdb:SQLType="VARCHAR2" oraxdb:memType="1" oraxdb:MemInline="true" oraxdb:SQLInline="true" oraxdb:JavaInline="true">
            <xsd:annotation>
              <xsd:documentation>American Petroleum Institute well number.  </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
          <xsd:element name="statusWell" type="witsml:WellStatus" minOccurs="0" maxOccurs="1" oraxdb:propNumber="4981" oraxdb:global="false" oraxdb:SQLName="statusWell" oraxdb:SQLType="XDB$ENUM_T" oraxdb:SQLSchema="XDB" oraxdb:memType="259" oraxdb:MemInline="true" oraxdb:SQLInline="true" oraxdb:JavaInline="true">
            <xsd:annotation>
              <xsd:documentation>POSC Well status.  </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
          <xsd:element name="purposeWell" type="witsml:WellPurpose" minOccurs="0" maxOccurs="1" oraxdb:propNumber="4982" oraxdb:global="false" oraxdb:SQLName="purposeWell" oraxdb:SQLType="XDB$ENUM_T" oraxdb:SQLSchema="XDB" oraxdb:memType="259" oraxdb:MemInline="true" oraxdb:SQLInline="true" oraxdb:JavaInline="true">
            <xsd:annotation>
              <xsd:documentation>POSC well purpose.  </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
          <xsd:element name="fluidWell" type="witsml:WellFluid" minOccurs="0" maxOccurs="1" oraxdb:propNumber="4983" oraxdb:global="false" oraxdb:SQLName="fluidWell" oraxdb:SQLType="XDB$ENUM_T" oraxdb:SQLSchema="XDB" oraxdb:memType="259" oraxdb:MemInline="true" oraxdb:SQLInline="true" oraxdb:JavaInline="true">
            <xsd:annotation>
              <xsd:documentation>POSC well fluid. The type of fluid being produced from or injected
                             into a well facility. </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
          <xsd:element name="directionWell" type="witsml:WellDirection" minOccurs="0" maxOccurs="1" oraxdb:propNumber="4984" oraxdb:global="false" oraxdb:SQLName="directionWell" oraxdb:SQLType="XDB$ENUM_T" oraxdb:SQLSchema="XDB" oraxdb:memType="259" oraxdb:MemInline="true" oraxdb:SQLInline="true" oraxdb:JavaInline="true">
            <xsd:annotation>
              <xsd:documentation>POSC well direction. The direction of flow of the fluids in a well facility
                             (generally, injected or produced, or some combination). </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
          <xsd:element name="dTimSpud" type="witsml:timestamp" minOccurs="0" maxOccurs="1" oraxdb:propNumber="4985" oraxdb:global="false" oraxdb:SQLName="dTimSpud" oraxdb:SQLType="TIMESTAMP" oraxdb:memType="180" oraxdb:MemInline="true" oraxdb:SQLInline="true" oraxdb:JavaInline="true">
            <xsd:annotation>
              <xsd:documentation>Date and time at which well was spudded.  </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
          <xsd:element name="dTimPa" type="witsml:timestamp" minOccurs="0" maxOccurs="1" oraxdb:propNumber="4986" oraxdb:global="false" oraxdb:SQLName="dTimPa" oraxdb:SQLType="TIMESTAMP" oraxdb:memType="180" oraxdb:MemInline="true" oraxdb:SQLInline="true" oraxdb:JavaInline="true">
            <xsd:annotation>
              <xsd:documentation>Date and time at which well was plugged and abandoned.  </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
          <xsd:element name="wellheadElevation" type="witsml:wellElevationCoord" minOccurs="0" maxOccurs="1" oraxdb:propNumber="4987" oraxdb:global="false" oraxdb:SQLName="wellheadElevation" oraxdb:SQLType="wellElevationCoord697_T" oraxdb:SQLSchema="TTUSER" oraxdb:memType="258" oraxdb:MemInline="false" oraxdb:SQLInline="true" oraxdb:JavaInline="false">
            <xsd:annotation>
              <xsd:documentation>Elevation of wellhead relative to a wellDatum.  </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
          <xsd:element name="wellDatum" type="witsml:cs_wellDatum" minOccurs="0" maxOccurs="unbounded" oraxdb:propNumber="4988" oraxdb:global="false" oraxdb:SQLName="wellDatum" oraxdb:SQLType="cs_wellDatum758_T" oraxdb:SQLSchema="TTUSER" oraxdb:memType="258" oraxdb:MemInline="false" oraxdb:SQLInline="true" oraxdb:JavaInline="false" oraxdb:SQLCollType="wellDatum760_COLL" oraxdb:SQLCollSchema="TTUSER">
            <xsd:annotation>
              <xsd:documentation>A datum to which elevations and depths are referenced. </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
          <xsd:element name="groundElevation" type="witsml:wellElevationCoord" minOccurs="0" maxOccurs="1" oraxdb:propNumber="4989" oraxdb:global="false" oraxdb:SQLName="groundElevation" oraxdb:SQLType="wellElevationCoord697_T" oraxdb:SQLSchema="TTUSER" oraxdb:memType="258" oraxdb:MemInline="false" oraxdb:SQLInline="true" oraxdb:JavaInline="false">
            <xsd:annotation>
              <xsd:documentation>Elevation of ground level (land rigs).  </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
          <xsd:element name="waterDepth" type="witsml:wellVerticalDepthCoord" minOccurs="0" maxOccurs="1" oraxdb:propNumber="4990" oraxdb:global="false" oraxdb:SQLName="waterDepth" oraxdb:SQLType="wellVerticalDepthCoord698_T" oraxdb:SQLSchema="TTUSER" oraxdb:memType="258" oraxdb:MemInline="false" oraxdb:SQLInline="true" oraxdb:JavaInline="false">
            <xsd:annotation>
              <xsd:documentation>Depth of water (not land rigs).  </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
          <xsd:element name="wellLocation" type="witsml:cs_location" minOccurs="0" maxOccurs="unbounded" oraxdb:propNumber="4991" oraxdb:global="false" oraxdb:SQLName="wellLocation" oraxdb:SQLType="cs_location746_T" oraxdb:SQLSchema="TTUSER" oraxdb:memType="258" oraxdb:MemInline="false" oraxdb:SQLInline="true" oraxdb:JavaInline="false" oraxdb:SQLCollType="wellLocation761_COLL" oraxdb:SQLCollSchema="TTUSER">
            <xsd:annotation>
              <xsd:documentation>the 2D coordinates of the well surface point in one coordinate reference system.
                             This is where the well crosses ground level on land and crosses the platform offshore.  </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
          <xsd:element name="referencePoint" type="witsml:cs_referencePoint" minOccurs="0" maxOccurs="unbounded" oraxdb:propNumber="4992" oraxdb:global="false" oraxdb:SQLName="referencePoint" oraxdb:SQLType="cs_referencePoint749_T" oraxdb:SQLSchema="TTUSER" oraxdb:memType="258" oraxdb:MemInline="false" oraxdb:SQLInline="true" oraxdb:JavaInline="false" oraxdb:SQLCollType="referencePoint762_COLL" oraxdb:SQLCollSchema="TTUSER">
            <xsd:annotation>
              <xsd:documentation>Defines a reference point within the context of the well.  </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
          <xsd:element name="wellCRS" type="witsml:cs_wellCRS" minOccurs="0" maxOccurs="unbounded" oraxdb:propNumber="4993" oraxdb:global="false" oraxdb:SQLName="wellCRS" oraxdb:SQLType="cs_wellCRS755_T" oraxdb:SQLSchema="TTUSER" oraxdb:memType="258" oraxdb:MemInline="false" oraxdb:SQLInline="true" oraxdb:JavaInline="false" oraxdb:SQLCollType="wellCRS763_COLL" oraxdb:SQLCollSchema="TTUSER">
            <xsd:annotation>
              <xsd:documentation>A coordinate reference system that was used within
                             the context of this well.  </xsd:documentation>
            </xsd:annotation>
          </xsd:element>
        </xsd:sequence>
      </xsd:group>
    </xsd:schema>
    Registration:
    DECLARE
      fil BFILE;
    BEGIN
      dbms_lob.filecloseall();
      fil := bfilename('witsmlny','grp_well.xsd');
      DBMS_XMLSCHEMA.registerSchema(
        SCHEMAURL => 'grp_well.xsd',
        SCHEMADOC => fil,
        GENTYPES =>TRUE,
        GENTABLES => TRUE,
        CSID => nls_charset_id('AL32UTF8')
      dbms_lob.close(fil);
      dbms_lob.fileclose(fil);
    END;
    DECLARE
      fil BFILE;
    BEGIN
      dbms_lob.filecloseall();
      fil := bfilename('witsmlny','obj_well.xsd');
      DBMS_XMLSCHEMA.registerSchema(
        SCHEMAURL => 'obj_well.xsd',
        SCHEMADOC => fil,
        GENTYPES =>TRUE,
        GENTABLES => TRUE,
        CSID => nls_charset_id('AL32UTF8')
      dbms_lob.close(fil);
      dbms_lob.fileclose(fil);
    END;
    /*...and finally the CREATE TABLE*
    CREATE TABLE WELL OF XMLTYPE
      XMLSCHEMA "obj_well.xsd"
      ELEMENT "wells"
      VARRAY "XMLDATA"."well"
        STORE AS TABLE well_table
                       ((PRIMARY KEY (NESTED_TABLE_ID, SYS_NC_ARRAY_INDEX$)))
      VARRAY "XMLDATA"."well"."wellDatum"
        STORE AS TABLE well_wellDatum_table1
                       ((PRIMARY KEY (NESTED_TABLE_ID, SYS_NC_ARRAY_INDEX$)));Edited by: user10853405 on Apr 24, 2009 12:53 AM

  • Does BI Data Template allows calling of a package insite group element

    Hi
    Is it possible to call a package inside the group element tag.
    When i try to call a package outside the group element it works out, but when I try to call it inside the group element it doesnt return any result.
    Am currently using BI Publisher version of 5.6.3 in Oracle Applications 12.1.3
    Regards
    Anoop

    Thanks for your detailed answer!!
    I am trying to call a package just to understand how it works .This package just inserts a row in "suppliers" table.I ma calling this package through 'beforeReprot' trigger and querying the table after that.
    I have written a package "test_pack" :
    create or replace
    package test_pack as
    function test_insert_fun return boolean;
    end test_pack;
    create or replace
    package body test_pack as
    function test_insert_fun return boolean is
    begin
    insert into suppliers values (1,'p1','p2');
    return (TRUE);
    end;
    end test_pack;
    Data Template :
    <dataTemplate name="test" dataSourceRef="demo" defaultpackage="test_pack">
         <dataQuery>
              <sqlStatement name="Q1">
                   <![CDATA[SELECT * from suppliers]]>
              </sqlStatement>
         </dataQuery>
         <dataTrigger name="beforeReport" source="test_pack.test_insert_fun()"/>
    </dataTemplate>
    However after this , when I try to view data , I amnot seeing any output.When i go nad check the suppliers table in db, i dont see any values.
    I believe this package should be executed everytime i view the data.
    Please advice!!

  • Repeating a group element on each page of a report.

    I have a report where I need to repeat a group element on each page. The element is from the first group in the data. It is in the center group. Currently, the values from this group only print when the group changes. Everything I try does not work. Does anyone have any ideas. I am attaching a sample of the data. Along with the rtf document. I am using the BI Publisher plug in in Word to create the template.
    Data
    <?xml version="1.0" encoding="UTF-8"?>
    <POLLEDTICKETRPT>
    <USERCD>klockhar</USERCD><POLLDATE>03/24/2009</POLLDATE>
    <LIST_CENTER>
    <CENTER>
    <CENTER_CD>0039</CENTER_CD>
    <CENTER_NAME>CROSS PLAINS QUARRY</CENTER_NAME>
    <LIST_TRANSDATE>
    <TRANSDATE>
    <TRANS_DATE>03/11/2009</TRANS_DATE>
    <LIST_CUSTOMER>
    <CUSTOMER>
    <CUSTOMER_NBR>33221477</CUSTOMER_NBR>
    <CUST_NAME>TDOT DISTRICT 32-GALLATIN</CUST_NAME>
    <LIST_JOB>
    <JOB>
    <JOB_CUST>33221477</JOB_CUST>
    <JOB_CUST_NAME>TDOT DISTRICT 32-GALLATIN</JOB_CUST_NAME>
    <RGI_JOB_NBR>2008</RGI_JOB_NBR>
    <QUOTE_ID>0</QUOTE_ID>
    <LIST_COSTCODE>
    <COSTCODE>
    <COSTCODING/>
    <COST_CNTR/>
    <COST_ACCT/>
    <PROJECT_NBR/>
    <PROJECT_TASK/>
    <LIST_TICKET>
    <TICKET>
    <TICKET_NBR>5000021</TICKET_NBR>
    <ORIGIN_CD>TSCC</ORIGIN_CD>
    <REFERENCE_NBR>254510</REFERENCE_NBR>
    <VOID_IND>N</VOID_IND>
    <STATE_CD>TN</STATE_CD>
    <MEASURE_SYSTEM>S</MEASURE_SYSTEM>
    <LOCATION>THANK YOU</LOCATION>
    <PO_NBR>POS-254510-C</PO_NBR>
    <TAX_CODE>4</TAX_CODE>
    <PRODUCT_CD>000003</PRODUCT_CD>
    <HAUL_ZONE_CD/>
    <INVENTORY_STATUS>PR</INVENTORY_STATUS>
    <HAULER_NBR/>
    <RGI_TRANSPORT_CD>FU96</RGI_TRANSPORT_CD>
    <HAUL_RATE> .00</HAUL_RATE>
    <MAT_RATE> 8.50</MAT_RATE>
    <NET_TONS> -7.96</NET_TONS>
    <MAT_SALES_AMT> -67.66</MAT_SALES_AMT>
    <HAUL_AMT>0</HAUL_AMT>
    <TAX_AMT>0</TAX_AMT>
    <SEV_TAX_AMT>0</SEV_TAX_AMT>
    <SEV_TAX_IND>N</SEV_TAX_IND>
    <VALID_NET_TONS> -7.96</VALID_NET_TONS>
    <VALID_SALES_AMT> -67.66</VALID_SALES_AMT>
    <VALID_HAUL_AMT> .00</VALID_HAUL_AMT>
    <VALID_TAX_AMT> .00</VALID_TAX_AMT>
    <VALID_SEV_TAX_AMT> .00</VALID_SEV_TAX_AMT>
    <CASH_TONS> .00</CASH_TONS>
    <CASH_SALES_AMT> .00</CASH_SALES_AMT>
    <CASH_TAX_AMT> .00</CASH_TAX_AMT>
    <CASH_SEVTAX_AMT> .00</CASH_SEVTAX_AMT>
    <CASH_HAUL_AMT> .00</CASH_HAUL_AMT>
    <TRADE_TONS> -7.96</TRADE_TONS>
    <TRADE_SALES_AMT> -67.66</TRADE_SALES_AMT>
    <TRADE_TAX_AMT> .00</TRADE_TAX_AMT>
    <TRADE_SEVTAX_AMT> .00</TRADE_SEVTAX_AMT>
    <TRADE_HAUL_AMT> .00</TRADE_HAUL_AMT>
    <INTRA_TONS> .00</INTRA_TONS>
    <INTRA_SALES_AMT> .00</INTRA_SALES_AMT>
    <INTRA_TAX_AMT> .00</INTRA_TAX_AMT>
    <INTRA_SEVTAX_AMT> .00</INTRA_SEVTAX_AMT>
    <INTRA_HAUL_AMT> .00</INTRA_HAUL_AMT>
    <INTER_TONS> .00</INTER_TONS>
    <INTER_SALES_AMT> .00</INTER_SALES_AMT>
    <INTER_TAX_AMT> .00</INTER_TAX_AMT>
    <INTER_SEVTAX_AMT> .00</INTER_SEVTAX_AMT>
    <INTER_HAUL_AMT> .00</INTER_HAUL_AMT>
    <CASH_PR_TONS> .00</CASH_PR_TONS>
    <CASH_NP_TONS> .00</CASH_NP_TONS>
    <CASH_MI_TONS> .00</CASH_MI_TONS>
    <TRADE_PR_TONS> -7.96</TRADE_PR_TONS>
    <TRADE_NP_TONS> .00</TRADE_NP_TONS>
    <TRADE_MI_TONS> .00</TRADE_MI_TONS>
    <INTER_PR_TONS> .00</INTER_PR_TONS>
    <INTER_NP_TONS> .00</INTER_NP_TONS>
    <INTER_MI_TONS> .00</INTER_MI_TONS>
    <INTRA_PR_TONS> .00</INTRA_PR_TONS>
    <INTRA_NP_TONS> .00</INTRA_NP_TONS>
    <INTRA_MI_TONS> .00</INTRA_MI_TONS>
    </TICKET>
    </LIST_TICKET>
    </COSTCODE>
    </LIST_COSTCODE>
    </JOB>
    </LIST_JOB>
    </CUSTOMER>
    </LIST_CUSTOMER>
    </TRANSDATE>
    RTF Template
    DISPLAY CENTER
    S M
    FOR EACH CENTER
    SET CENTER
    CENTER: CENTER_CD CENTER_NAME
    FOR EACH TRANSDATE
    TRANSACTION DATE: TRANS_DATE
    FOR EACH CUSTOMER
    FOR EACH JOB
    Customer: JOB_CUST JOB_CUST_NAME
    Job: RGI_JOB_NBR Quote Id: QUOTE_ID
    FCC
    group COSTCODE by COSTCODING
    Cost Center: COST_CNTR Cost Acct: COST_ACCT Project: PROJECT_NBR Task: PROJECT_TASK
    Ticket Nbr     ORGCD     OrigTck     V     ST     Location     Po Nbr     Tax Cd     Prod Code     ZN     Hauler      Truck     Haul Rate     UnitPrice     Tons     SalesAmount
    F TCK#M     CODE     OTCK#     V     ST     LOCATION     PO_NBR      TC     PROD     HZ     HAULER     TRUCK     0.00     0.00     0.00 *      0.00 E

    Post Author: Guy
    CA Forum: General
    Hi,
    You should add a first level of grouping in your subreport on a fake formula field with a constant value.  Put your header and footer information in this group header and footer.  In the group option make sure to check the "repeat group header on each page option".
    This group will act as a page header + footer within your subreport.
    good luck!
    Guy

Maybe you are looking for

  • Error while compiling a program from api....URGENT

    i am trying to use a api for apell checking, and their is one program that i am trying to compile using command javac -Xlint org\tiling\didyoumean\DidYouMeanIndexer.java and it gives me an error like this org\tiling\didyoumean\DidYouMeanIndexer.java:

  • Update to iOS 5.1 causes iPhone to crash on "Restoring iPhone Firmware"

    Hello everyone. I have been vry please with my iPhone 4 on Verizon for the last 6 months.  I was on iOS 5 which worked great.  Then this morning the AppStore icon had the familiar red circle indicating some apps had updates available.  I clicked Upda

  • Only one Application can be created at a time?

    We are using enhanced model of SAP-WCM and are in the EHP6 version. We have additional applications, in addition to main application. We do not use Work permit. Our users are creating work approval, applications & WCDs, manually as well as automatica

  • Create a SPDT switch

    can any one tell me how to create a SP3T switch in Labview. It should look like switch symbol?

  • EM logon fails for Oracle App Server (10.1.3.1.0)

    I am trying to logon to the Enterprise Manger 10g Grid Control. My OS is HP-UX 11.11 I am receiving Invalid/Password. I have change this password twice and still receiving the error. Does anyone know what's going on with this Application? Please Help