Display Structure Hierarchy (Root node appears below)

Dear Expert,
I have a requirement to create a hierarchy in Query Designer (I cannot use the hierarchy maintained at the infoobject). However, I want to display it as the root node appears below (like the option set at the hierarchy maintenance). Is there any way to do the same thing in Query Designer?
I think the option display Result below can apply to non-hierarchy data only.
Thanks

Hello,
yes there is an option in QDesigner:
in 7.X:
activate the hierarchy in the hierarchy-tab of the relevant infoobject (->properties). In the same tab you will find an option
"Position of Lower-Level Nodes" -> select "above".
You will have the same option in 3.X QDesigner: -> properties -> activate hierarchy in "Display Hierarchy" and set the option
for "Position of Lower-level Nodes" by clicking on "User Settings" -> select value "up".
Now you should see the parent-nodes below its children.
best regards,
Jerome

Similar Messages

Display key and text by WAD command in custom structure hierarchy

Hi everybody,
I have a query using a custom structure with hierarchy layout. As usual the structure does only display its text as descriptions but I can enable the display the key in BEx Web by right-click on the analysis item --> Properties --> Characteristic --> Display. Unfortunately these setting can not be defined directly in the structure within the Query Designer.
For a workaround I put the query into a web template, in which I used the Set Presentation (SET_PRESENTATION) command to enable key and text display from the start. Hence I put that command in the wem template parameters Action Before First Rendering (ACTION_BEFORE_FIRST_RENDERING). Everything is working properly and makes me very happy.
But... there is one thing missing, I would like to implement... I want a toggle button, which allows the user to switch between key and text display and text display. Unfortunately setting the same command from Action Before First Rendering (ACTION_BEFORE_FIRST_RENDERING on a various button does not working. The button command only affects data rows of the leaves of the structure hierarchy. All parent nodes do not change their appearance.
Any ideas how to solve this?
Thank you for any helps and comments!
Sebastian

Hi Sebastian,
I have a similar problem. Can you help me? How did you set the entry in Member Presentation of Command SET_PRESENTATION to display key and text? I just found the values to set the only text or only key.
best regards,
Barbara

How to create Hierarchy Tree Node structure?

Hi experts,
          I want to know how to create a tree with kind of below Structure:
Root A
         NodeA1
              ITEMA1_IT1
              ITEMA1_IT2
              ITEMA1_IT3
         NodeA2
              ITEMA2_IT1
              ITEMA2_IT2
         NodeA3
              ITEMA3_IT1
              ITEMA3_IT2
              ITEMA3_IT3
              ITEMA3_IT4
So when i click on Root A it shows me, NODEA1, NODEA2 & NODEA3....
when further i click on NODEA1, it shows me items like ITEMA1_IT1,ITEMA1_IT2, ITEMA1_IT3.
when further i click on NODEA2, it shows me items like ITEMA2_IT1,ITEMA2_IT2.
SO item will get loaded when i click on perticular node.
how its possible.
I have gone through SDN so many threads, bt i didn't get exactly for webdynpro ABAP.
Please guide me for the same.
Thanks ,
Saurin Shah

Hi,
you can create the tree you wanted as follows:
1) create a node under your context say "root_node" with cardinality 1..1
2) now create an attribute under it called "text" with type string.
3) now create three nodes under this "root_node" called nodeA1 nodeA2 and nodeA3 with cardinality 0..n
4) now under nodeA1 , nodeA2 and nodeA3 create an attribute called "text" with type string...so each node will have one attribute called "text" of type string...
5) now create a node under nodeA1 called "itemA1" with cardinlity 0..n
6) now create an attribute called "text" of type string under this node "itemA"...
7) repeat step 5 and 6 for the other two nodes...nodeA2 and nodeA3
8) now create six supply functionsthese functions will supply the text values for your nodes-
I created like this:
FILL_ITEM1
FILL_ITEM2
FILL_ITEM3
FILL_NODEA1
FILL_NODEA2
FILL_NODEA3
Note:*******************my view is called MAIN******************
hence the coding is
data
    lt_elements type if_main=>elements_nodea1.
if you view is called view1...than the data declaration would be
data
    lt_elements type if_view1=>elements_nodea1.
9) go to each node and assign the supply function respectively....you can assign this by going to context tab and selecting the node you want to assign the supply function to and just type in the name of the supply funciton or do the help for that field by clicking on the little square btn...
10) now we go the layout tab and put the tree ui on the layout....bind the datasource property to the context node "root_node"
and bind the rootText property to the attribute "text" of the root_node...
11) now right click on this tree ui element under the ROOTUIELEMENTCONTAINER and select "insert node type" ...a box will appear where you can see it has two types of node for you....one is tree_node_type and other one is tree_item_type...
create three nodes with tree_node_type with names "nodeA1" nodeA2 and nodeA3 and three with tree_item_type with names "itemA1" itemA2 and itemA3...
12) now bind all these node types and item types data sources and texts with corresponding nodes and attributes under your context...
so nodeA1datasource will get bind to context nodeA1 and itemA1 data source will get bind to itemA1 from context..and so on...
13) now in the wddoinit method: I setup the text for the root node.....
DATA lo_nd_root_node TYPE REF TO if_wd_context_node.
DATA lo_el_root_node TYPE REF TO if_wd_context_element.
DATA ls_root_node TYPE wd_this->element_root_node.
DATA lv_root_txt TYPE wd_this->element_root_node-root_txt.
navigate from <CONTEXT> to <ROOT_NODE> via lead selection
lo_nd_root_node = wd_context->get_child_node( name = wd_this->wdctx_root_node ).
get element via lead selection
lo_el_root_node = lo_nd_root_node->get_element( ).
@TODO fill attribute
lv_root_txt = 'Root Node'.
set single attribute
lo_el_root_node->set_attribute(
    name = `ROOT_TXT`
    value = lv_root_txt ).
hope this will give you the solution you are looking for...
Thanks...
AS...........

How to display the Hierarchy Node Level in BEx

Hi Folks,
In my report I have a Hierarchy. I have to display the Node level of the Hierarchy in the output.
For Eg:
If I have BB under AA root node then in the output it should display Level 1 for AA and Level 2 for BB.
Thanks in Advance.
Regards,
Srikanth N

I don't think it is possble to display the hierarchy level in the report itself.
However, if you go to properties of the characteristic where you have the hierarchy defined, there you can expand the hierarchy to a pre-defined level...I guess you know that.
AT

How do i get to display the nodes under the root node in a JTree?

In my JTree there is a root node.This root node has 4 child nodes.Each child node in turn has nodes under it.What i need to do is just display the child nodes under the root node i.e., the four child nodes and keep these child nodes in a collapsed state.How do i go sbout this?

Please try this:
tree.expandRow(0);
SwingUtilities.invokeLater(new Runnable(){
    public void run(){
        tree.setRootVisible(false);
});If you want to show the RootHandles:
tree.setShowsRootHandles(true);If you want to keep nodes in collapsed state (not expandable):
        tel = new TreeWillExpandListener() {
            public void treeWillExpand(TreeExpansionEvent event) throws ExpandVetoException {
                throw new ExpandVetoException( event, "Don't want" );
            public void treeWillCollapse(TreeExpansionEvent event) throws ExpandVetoException {
        tree.addTreeWillExpandListener(tel);Some reading material:
http://java.sun.com/docs/books/tutorial/uiswing/components/tree.html
http://java.sun.com/docs/books/tutorial/uiswing/events/treewillexpandlistener.html
Edited by: Andre_Uhres on Nov 14, 2007 5:17 PM
Edited by: Andre_Uhres on Nov 14, 2007 5:33 PM
Edited by: Andre_Uhres on Nov 14, 2007 5:39 PM

Display of Hierarchy Nodes as Medium Text in Web Report

Hello everyone,
Does anybody know how to display the hierarchy nodes as medium text instead of short text (default) in web report?
I know it is possible to change the display setting directly (by right clicking on hierarchy node > properties) from the web report.
However, I would love to know if there is any other way to change the settings such as through Query designer or Hierarchy maintenance in SAP GUI so that users do not need to change the display settings every time they view the web report.
Your help is kindly appreciated.

Thank you Shabar for you quick reply.
What if a Hierarchy is created under an InfoObject? How can I change the Text view of each name of the Hierarchy nodes?
In Query Designer, I tried to change the Text View to Long but it only affects the text of the InfoObject but not the Hierarchy nodes.
I tried the 2nd suggestion too. I only can find the BEx description for the InfoObject but not the Hierarchy nodes.
It would be great if anyone could tell me how to do so.
Thanks in advance.

How to change a generated root node for a hierarchy?

Hello,
we are loading hierarchies from an ECC system. Some of those hierarchies don't have a root node in the source system.
For those hierarchies, the root node is generated during the loading. This node is generated in english (ie : FUNDS CENTER HIERARCHY for fund centers). Is there a way to change the description and the technical name of this node to have it in another language.
We have tryied to change the language of ALEREMOTE in BI but it did not solve this problem.
Thanks,
Philippe

Hi Simon,
the language that triggered the loading was french.
BI Learner,
- to create a custom hierarchy in a BI system, you can use RSH1 transaction.
- if you want to load it from a SAP source system, you can use standard datasource provided in the business content (usually named *_HIER)
-if you need to load it from a flat file, you can follow the steps of this blog, it will help you:
Hierarchy Upload from Flat files
you can have more information about hierarchies on the help.sap web site :
http://help.sap.com/saphelp_nw70/helpdata/EN/a8/6b023b6069d22ee10000000a11402f/frameset.htm
Regards,
Philippe

How to hide root node of hierarchy?

Hi,
can anyone give me a hint how to hide the root node of a hierarchy?
Thank you very much in advance, best regards
Frank

Hi Frank,
Another way would be to restrict the hierarchy in the query definition. Select all nodes, except the root. You can do the same in excel and save the query as a view. Of course, you have to maintain this selection every time the hierarchy gets new nodes.
Natali

Tree with multiple root nodes does not display

I am trying to create a tree to display some hierarchical data which contains several root nodes.
I have specifed that the TREE_ROOT value is always Null as the root nodes have a null value for the PARENT_ID. The page displays yet none of the data is displayed.
I have manage to get it to work by creating a dummy single root that I reference from the existing root values?

Phattam,
The TREE_ROOT identifies the root node's ID, not its PARENT_ID.
For example, if we build a tree on the oehr_employees table, the ID is EMPLOYEE_ID and the PARENT_ID is MANAGER_ID. therefore, to identify the start of the tree, we could populate the TREE_ROOT with a select statement e.g.
SELECT employee_id FROM oehr_employees WHERE employee_id = 100This identifies a single value and the tree starts from employee_id 100.
If we used a select statement that retrieves more than one row, e.g.
SELECT employee_id FROM oehr_employees WHERE manager_id = 100then the tree starts at one of the children of employee_id 100 - ApEx will not show a tree that has more than one starting node. If you want to show these alternative starting points, you'll need to do exactly what you have done - create a 'dummy' root node.
Hope this helps,
Bryan.

Problem in Swing tree root node when displaying Japanese

I'm trying to create a tree using DefaultTreeModel. The root node will display text in Japanese and the other child nodes are in English. My problem is the root node fails to show Japanese correctly (only squares are shown).
I've already set my font.properties.ja to display Japanese font for virtual font "dialog":
dialog.plain.0=Arial,ANSI_CHARSET
dialog.plain.1=\uff2d\uff33 \u30b4\u30b7\u30c3\u30af,SHIFTJIS_CHARSET
dialog.plain.2=WingDings,SYMBOL_CHARSET,NEED_CONVERTED
dialog.plain.3=Symbol,SYMBOL_CHARSET,NEED_CONVERTED
And I've checked the "Tree.font" of UIManager is:
Tree.font = javax.swing.plaf.FontUIResource[family=dialog,name=Dialog,style=plain,size=12]
I'm quite sure that my font.properties.ja is correct as all message dialogs in my app. shows Japanese correctly (also using the same dialog font).
I got stuck. Can anyone please give me some advice? Thanks in advance.

hello!
first of all i am sorry that i cannot help u.
i am a java developer and start work on
Arabic ( one of the langugae supported by
unicode) text editing.If u have any knowledge that
what i should do to display the text in this language
in a textarea.when i run a code,this display only
square.
plz help me.i will be realy thankful to u.
Qaiser Mehmood
[email protected]

How to Create Instances in the Transient Root Node and Sub Nodes from Root Node Query Method ?

Hi All,
I am Creating a BOPF BO with 3 Nodes,
Node 1) ROOT -- > contains a query,
using Root Node I have created Search UIBB Configuration in FBI.
In testing -- > when i enter Data in the Search Criteria Fields am able to get the details in to the query method
from Imporing parameter : 'IT_SELECTION_PARAMETERS'.
HERE I am fetching data from a standard table and trying to fill the data in the Node : 'MNR_SEARCH_RESULT'.
How to Append data to the Sub node 'MNR_SEARCH_RESULT' when there is no Node instance created in the ROOT Node ?
For This I have created an instance in the ROOT Node and Using that I tried to create Instance in the Sub Node 'MNR_SEARCH_RESULT'.
Below is my code which i have placed in the Query method ..
DATA : LR_DATA TYPE REF TO ZBO_S_ROOT1.
DATA : LR_SEARCH_RES TYPE REF TO ZBO_S_MNR_SEARCH_RESULT.
DATA : LO_CI_SERVICE_MANAGER TYPE REF TO /BOBF/IF_TRA_SERVICE_MANAGER,
        LO_TRANSACTION_MANAGER TYPE REF TO /BOBF/IF_TRA_TRANSACTION_MGR.
   LO_CI_SERVICE_MANAGER = /BOBF/CL_TRA_SERV_MGR_FACTORY=>GET_SERVICE_MANAGER( IV_BO_KEY = ZIF_BO_TEST_PO_C=>SC_BO_KEY ).
   LO_TRANSACTION_MANAGER = /BOBF/CL_TRA_TRANS_MGR_FACTORY=>GET_TRANSACTION_MANAGER( ).
CREATE DATA LR_DATA.
LR_DATA->KEY = LO_CI_SERVICE_MANAGER->GET_NEW_KEY( ).
LR_DATA->ROOT_KEY   = IS_CTX-ROOT_NODE_KEY.
LR_DATA->PIPO_MAT_ID = '100100'.
LR_DATA->PIPO_MAT_DESC = 'MATERIAL'.
LR_DATA->PIPO_SPRAS = 'E'.
LR_DATA->PIPO_MATL_TYPE = 'ZPMI'.
LR_DATA->PIPO_MATL_GROUP = 'ZKK'.
     DATA lt_mod      TYPE /bobf/t_frw_modification.
     DATA lo_change   TYPE REF TO /bobf/if_tra_change.
     DATA lo_message TYPE REF TO /bobf/if_frw_message.
     FIELD-SYMBOLS: <ls_mod> LIKE LINE OF lt_mod.
    APPEND INITIAL LINE TO lt_mod ASSIGNING <ls_mod> .
    <ls_mod>-node        =   ZIF_BO_TEST_PO_C=>sc_node-ROOT.
    <ls_mod>-change_mode = /bobf/if_frw_c=>sc_modify_create.
    <ls_mod>-key         = LR_DATA->KEY.
    <ls_mod>-data        = LR_DATA.
DATA : LT_CHG_FIELDS TYPE /BOBF/T_FRW_NAME.
DATA : LS_CHG_FIELDS LIKE LINE OF LT_CHG_FIELDS.
DATA : LV_KEY TYPE /BOBF/CONF_KEY.
CALL METHOD IO_MODIFY->CREATE
   EXPORTING
     IV_NODE            = ZIF_BO_TEST_PO_C=>sc_node-ROOT
     IV_KEY             = LR_DATA->KEY
     IS_DATA            = LR_DATA
     IV_ROOT_KEY        = IS_CTX-ROOT_NODE_KEY
   IMPORTING
     EV_KEY             = LV_KEY .
CREATE DATA LR_SEARCH_RES.
LR_SEARCH_RES->KEY           = LO_CI_SERVICE_MANAGER->GET_NEW_KEY( )..
LR_SEARCH_RES->PARENT_KEY    = LV_KEY.
LR_SEARCH_RES->ROOT_KEY    = LV_KEY.
LR_SEARCH_RES->MATNR    = '123'.
LR_SEARCH_RES->ERSDA    = SY-DATUM.
LR_SEARCH_RES->ERNAM    = SY-UNAME.
**LR_SEARCH_RES->LAEDA    = .
**LR_SEARCH_RES->AENAM    = .
**LR_SEARCH_RES->VPSTA    = .
*LR_SEARCH_RES->LVORM    = .
LR_SEARCH_RES->MTART    = 'ZPI'.
LR_SEARCH_RES->MBRSH    = 'ZTP' .
LR_SEARCH_RES->MATKL    = 'MAT'.
**LR_SEARCH_RES->BISMT    = ''
**LR_SEARCH_RES->MEINS    =
CALL METHOD io_modify->create
           EXPORTING
             iv_node            = ZIF_BO_TEST_PO_C=>sc_node-MNR_SEARCH_RESULT
             is_data            = LR_SEARCH_RES
             iv_assoc_key       = ZIF_BO_TEST_PO_C=>sc_association-root-MNR_SEARCH_RESULT
             iv_source_node_key = ZIF_BO_TEST_PO_C=>sc_node-root
             iv_source_key      = LV_KEY
             iv_root_key        = LV_KEY.
I am Unable to set data to the Node . I did not get any error message or Dump while executing . when i tried to retrive data I got the details from the node but am unable to view those details in the FBI UI and BOBT UI while testing .
Please provide your valuable Suggestions.
Thanks in Adv.
Thanks ,
Kranthi Kumar M.

Hi Kranthi,
For your requirement you need only two nodes. Root Node and Result node. Use the same structure for both.
To create Instance while search.
Create Query method with input type which has the required fields for selection criteria.
Fetch the data and create instance in the root node.
Pass the new instance key as exporting parameter form Query Method.
To Move data from ROOT to Result.
Create a action at root node.
Write a code to create new entries in Result node.
Then configure the Search UIBB and display result in List UIBB. Add button and assign the action MOVE_MAT_2_RESULT.
Create another List uibb to display data from Result node.
Connect the UIBBs using wire schema. SEARCH -> LIST(ROOT) ---> LIST(RESULT).
Give src node association for ROOT to RESULT Configuration.
Regards,
Sunil

How do i add a root node to a XMLType

Hi all
I have a problem inserting a root node in a xml document generated by DBMS_XMLGEN.newcontextfromhierarchy. The function get_site_map_nodes generates a document like this:
<?xml version="1.0"?>
<siteMapNode f_page_id="1" title="rot" PATH="1">
<siteMapNode f_page_id="2" title="1.1" PATH="1.1">
<siteMapNode f_page_id="4" title="1.1.1" PATH="1.1.1"/>
</siteMapNode>
<siteMapNode f_page_id="3" title="1.2" PATH="1.2"/>
<siteMap/>
</siteMapNode>
This is correct but i want to add a root node so the result shows as below:
<?xml version="1.0"?>
<siteMap>
<siteMapNode f_page_id="1" title="rot" PATH="1">
<siteMapNode f_page_id="2" title="1.1" PATH="1.1">
<siteMapNode f_page_id="4" title="1.1.1" PATH="1.1.1"/>
</siteMapNode>
<siteMapNode f_page_id="3" title="1.2" PATH="1.2"/>
<siteMap/>
</siteMapNode>
</siteMap>
The problem is that i have no clue how to accomplish this.
Best regards
Daniel Carlsson
PACKAGE BODY PKG_PAGE_STRUCTURE
IS
FUNCTION get_level_path (in_page_id IN page_structure.f_page_id%TYPE)
RETURN VARCHAR2
IS
l_path VARCHAR2 (4000) := '';
BEGIN
SELECT MAX (SYS_CONNECT_BY_PATH (f_show_order, '.'))
INTO l_path
FROM page_structure
START WITH f_page_id = in_page_id
CONNECT BY PRIOR f_parent_page = f_page_id;
l_path := RTRIM (l_path, '.');
RETURN l_path;
END get_level_path;
FUNCTION get_site_map_nodes (in_page_id IN page_structure.f_page_id%TYPE)
RETURN XMLTYPE
IS
qryctx DBMS_XMLGEN.ctxhandle;
l_xml XMLTYPE;
BEGIN
qryctx :=
DBMS_XMLGEN.newcontextfromhierarchy
('select level, xmlelement("siteMapNode", XMLAttributes(f_page_id as "f_page_id",
f_title_phrase as "title", pkg_page_structure.get_level_path(f_page_id) as path))
FROM PAGE_STRUCTURE
START WITH f_page_id = :in_page_id
connect by f_parent_page = prior f_page_id
ORDER siblings BY f_show_order'
DBMS_XMLGEN.setbindvalue (qryctx, 'in_page_id', TO_CHAR (in_page_id));
l_xml := DBMS_XMLGEN.getxmltype (qryctx);
DBMS_XMLGEN.closecontext (qryctx);
RETURN l_xml;
END get_site_map_nodes;
END PKG_PAGE_STRUCTURE;
CREATE TABLE page_structure
(f_page_id NUMBER(10,0) NOT NULL,
f_parent_page NUMBER(10,0),
f_show_order NUMBER(10,0),
f_title_phrase VARCHAR2(20),
f_created_by NUMBER(10,0),
f_created_date DATE,
f_updated_by NUMBER(10,0),
f_updated_date DATE)
INSERT INTO page_structure
(F_PAGE_ID,F_PARENT_PAGE,F_SHOW_ORDER,F_TITLE_PHRASE,F_CREATED_BY,F_CREATED_DATE,F_UPDATED_BY,F_UPDATED_DATE)
VALUES
(1,NULL,1,'rot',1,'30-MAR-2006',NULL,NULL)
INSERT INTO page_structure
(F_PAGE_ID,F_PARENT_PAGE,F_SHOW_ORDER,F_TITLE_PHRASE,F_CREATED_BY,F_CREATED_DATE,F_UPDATED_BY,F_UPDATED_DATE)
VALUES
(2,1,1,'1.1',1,'30-MAR-2006',NULL,NULL)
INSERT INTO page_structure
(F_PAGE_ID,F_PARENT_PAGE,F_SHOW_ORDER,F_TITLE_PHRASE,F_CREATED_BY,F_CREATED_DATE,F_UPDATED_BY,F_UPDATED_DATE)
VALUES
(3,1,2,'1.2',1,'30-MAR-2006',NULL,NULL)
INSERT INTO page_structure
(F_PAGE_ID,F_PARENT_PAGE,F_SHOW_ORDER,F_TITLE_PHRASE,F_CREATED_BY,F_CREATED_DATE,F_UPDATED_BY,F_UPDATED_DATE)
VALUES
(4,2,1,'1.1.1',1,'30-MAR-2006',NULL,NULL)
/

Please try below steps.
1. Complete Prerequisite for adding cluster node
2. Verify the node is accessible to all other nodes in the cluster. Run the following command from the existing node in the cluster.
cluvfy stage -pre crsinst -n newNode
3. Run cluvfy from any existing node
cluvfy stage -pre nodeadd -n <New Node>
Note : If cluvfy in above step shows any errors fix those and then proceed with this step
4. Change Directory to Clusterware Home and execute addNode scripts from any existing node.
cd $CRS_HOME/oui/bin
./addNode.sh -silent "CLUSTER_NEW_NODES={ <NewNode > } CLUSTER_NEW_PRIVATE_NODE_NAMES={ <Interconnect >} CLUSTER_NEW_VIRTUAL_HOSTNAMES={ < Virtual Host Name >}"
At the end of addNode, script will prompt to run for root.sh on newly added node.
5. Verify Node is successfully added
cluvfy stage -post nodeadd -n <NewNode >
6. Verify CRS Stack is running on the new Node.
$CRS_HOME/bin/crs_stat -t
7. To extend the Oracle RAC Installation to include the new Node, run addNode from $ORACLE_HOME/oui/bin from existing node in the cluster
cd $CRS_HOME/oui/bin
./addNode.sh
When OUI displays the Specify Cluster Nodes to Add to Installation window, select the node to be added, then click Next .
Verify the summary and run root.sh on new node when it prompts.
8. Adding New Instance on the New Node
$CRS_HOME/bin/lsnrctl status
9.Run $ORACLE_HOME/bin/dbca from any of the existing RAC Instances Oracle Home.
Select Oracle Real Application Clusters database , and then click Next .
Select Instance Management , and then click Next .
Select Add an Instance , then click Next .
Click Next to accept default instance name or it can be changed.
Check the summary window.
Note: Please check these steps in test environment first.
HTH

Display structure in crystal report using structure created in BEx.

I created a structure in BEx query designer and trying to display the structure as a hierarchy in crystal report.
Iam not able to accomplish it. the crystal report is displaying the structure with no nodes. please help

Hi,
in case you created a BEx query with 2 structure - one for keyfigures and one as characteristic structure - then the structure for the characteristics will result in Crystal REports using the BW MDX Driver as a single field and each element of the structure will result in a row of data.
regards
Ingo Hilgefort

How to get the Figure Title to appear below the graphic, not above

I have valid XML that I am importing into FrameMaker just for printing.
My <figure> element contains a <title> and a <graphic> element. The graphic comes in within an anchored frame, appearing after the figure title. The figure title needs to be below the graphic. How do I get this to work? I read a couple of threads that used tables to wrap the graphic & the title and to make the title appear below, but that was during an export function to XML, not an import. Short of editing the DTD, EDD & all of the XML data to have the graphic element structure come before the title within <figure>, how would this be accomplished? Thanks in advance.

You're saying the xrefid should go in the <title> instead of in <figure>, but where in what document do I point to that ID?
First, to cross-reference an element, the target element has to have an ID attribute. You do not have to expicitly put a value into that attribute. When you create the cross-reference in FrameMaker, you list the elements, select the title element, and select the particular instance of that element as the target. FrameMaker adds a value to the target ID attribute for you.
Second, FrameMaker basically treats every element as a paragraph unless the EDD specifically states that it is to have character formatting. When you create a cross-reference to an element, the TEXT of the element is the text of the first paragraph IN the element. In your case, the graphic element is the first paragraph inside the figure element; it has a phantom (blank) paragraph above the graphic to hold the graphic marker. Then the title element is the second paragraph in the figure element. So, when you reference the figure element, the text of the first paragraph inside it is blank.
Third, the same applies to autonumbering. If the cross-reference is to show the autonumber and you target the figure element, then the first paragraph in the figure is the graphic element which has that blank paragraph above it. Your EDD does not treat apply formatting, that is the autonumbering to the graphic element. Hence, the autonumbering does not display in the cross-reference. FrameMaker has no way to dig down into the figure element and extract autonumbering from its second child element. Thus, you need to target the title element itself.
Rereading your post, I may not be actually answering your questions, but maybe this will clear up a few things.
In the EDD, I have:
Element (Conatiner): title
Text format rules
1. If context is: {notfirst} < subfig
    Use paragraph format: subfigs
    Else, if context is: {first} < subfig
    Use paragraph format: subfig
2. If context is {only} < figure
    Use paragarph format: figuretitle
Element (Container): figure
Text format rules
    Element paragraph format: figure
Element (CrossReference): xref
Initial cross-reference format
1. If context is: [type="figure"]
    Use cross-reference format: figure
You do not give an example of how you are using the subfig element. But there is a problem with the title element in a figure element. The context {only} < figure means "the only child element in the figure element". This will NEVER be satisfied because title is not the only element in figure; figure also has a graphic element. NOTE {only} means only ELEMENT NOT only TITLE element. This confused me when I started creating EDDs.
NOW, if I assume the subfig structure should be something like:
<figure>
<subfig><graphic/><title></subfig>
<subfig><graphic/><title></subfig>
<subfig><graphic/><title></subfig>
</figure>
Then the context {first} < subfig is NEVER satisfied because title is NEVER the first element inside subfig but {notfirst} < subfig is always true, because title is never the first element inside subfig. Hence, all title elements inside subfig elements are tagged with the subfigs tag, never subfig.
I am thinking the contexts should be:
subfig {first} < figure
subfig {notfirst} < figure
Remember these are contexts for the title element. The first is a title element in the first subfig element in a figure element; and the second is a title in a subfig that is not the first element in a figure element.
Figure 1-1. ABCD                     <-- figuretitle
Figure 1-2. EFGH (Sheet 1)     <-- subfig
Figure 1-2. EFGH (Sheet 2)     <-- subfigs
Figure 1-2. EFGH (Sheet 3)     <-- subfigs
For instructions A - D, see Figure 1-1. For instructions E - H, see Figure 1-2.
I am assuming you are manually entering Sheet 1, Sheet 2, etc in the title elements of each subfig element. It is not clear from your posts where the autonumber is displayed. Is it displayed in front of the title or above the graphic? If the title element carries the autonumbering, then you need to target the title element and not the figure element. If the autonumber is in that "blank" line above the graphic, then you can target the figure element because its first paragraph displays the autonumber.
I believe I have gone on way too much, but hope something in the above is the answer to your problem. See if any of this helps and then post again. Maybe we can get this figured out...pun intended.
Van

HTMLTree to display BW Hierarchy

Hi,
is there any way to to display bw hierarchy tree with <htmlb:tree>?
The structure of BW NODEs is like follows:
ID
TYPE
NAME
PARENT
CHILD
NEXT
TLEVEL
TLOCK
STATUS
INCLUDE
LINK
Thank you in advance!
ag

for the tree table use the table of type TVIEW2.
and the tlevel can be max 2 chars long.
to build the tree in BSP side, its enough if you pass the following fields.
status
childid
parentid
text
treeid
Regards
Raja

Display Structure Hierarchy (Root node appears below)

Similar Messages

Maybe you are looking for