Second level Hierarchy Manager
I have a hierarchy like this
A has child B,C
B has child D,E,F
C has child P,Q
D has Child G,H
E has child I,J,K
F has Child L,M
G has child N,O
I need the second level manager from top most node for any child
1st level top most node in the above example is A
2nd level top most node in the above example is B and C
I will give any child as parameter.But it has to return its 2nd level manager.
For eg if my parameter is J it has to return B
if my parameter is Q it has to return C
if my parameter is N it has to return B
Thanks
Hi,
One way is to use a Yo-Yo Query , where you do two CONNECT BYs: one from the bottome up, the next from the top down, like this:
WITH ancestors AS
SELECT child
, parent
, CONNECT_BY_ISLEAF AS is_root
FROM table_x
START WITH child = 'J'
CONNECT BY child = PRIOR parent
SELECT child
FROM ancestors
WHERE LEVEL = 3 -- or 4, or whatever
START WITH is_root = 1
CONNECT BY parent = PRIOR child
;Another way is to use a single CONNECT BY, and get the desired results from SYS_CONNECT_BY_PATH and REGEXP_SUBSTR.
Similar Messages
-
Second level Manager Unable to view the leave request
Hello Experts
We are using three levels approval leave request, first level manager able to approve successfully, when second level manager approving the leave request is unable to see any contents inside the request, its showing blank.
Kindly help me on this.
Thanks
Neelima.Hi,
I have a requirement in which I have to sent Leave Workflow to three approvers. For that I maintain the approvers in a customising table. What I did is, I took a copy of the standard Leave WF and added a step in loop (to read the table maintained, through a bor method). For the last approver, he has to get the standard leave approval task and for that reason i looped my custom bor for 2 times and put the standard leave approval task outside the loop.
Now the issue is that, eventhough the first approver gets the workitem and approves that, the next approver is not getting the workitem for him. Workflow is going into an error state stating that the successor node is not found.
Please tell me whether my approach for customising leave workflow is correct. And if correct, what could be the reason for the error that I get.
Regards, -
DMS repository manager error at second level
Hello everyone
We successfully installed the DMS Business Package in our portal, set up the back-end connection to our R/3 system, and now a couple folders show up when we view the Document Explorer iView. However... when I click on a folder, I receive an error:
com.sap.mw.jco.JCO$Exception: (127) JCO_ERROR_FIELD_NOT_FOUND: Field CREATED_BY not a member of BAPI_DOC_FILES2_KEYS
I went to the DMSRM_Explorer layout set to see if the collection renderer was trying to display the CreatedBy property, but it's not. The only properties it displays are rnd:icon, rnd:displayname(contentLink)+rnd:action, contentlength, rnd:lock, dmsrm_dir:dokar, dmsrm_dir:doknr, dmsrm_dir:dokvr, and dmsrm_dir:status. I even tried removing all displayed properties except for the icon and displayname, and still received that same error at the second level.
Has anyone run into this before, or perhaps have even a hint of where I should look to troubleshoot this problem? I can't find where it's trying to display Created_By.
We're on EP6 SP14.
Thanks in advance! All help will be rewarded with points.
- FallonLocated the table BAPI_DOC_FILES2_KEYS in our R/3 system, and the field CREATED_BY is not there. However, in some of our other R/3 systems (with later service packs) the field does exist. Which R/3 service pack creates this field? The DMS Business Package documentation states that the back-end R/3 system needs to be release 4.6C or later, but this must not be the case. We're currently on 4.7... sap_basis support pack is 55, sap_appl is 12, with a date of 30.09.2003 19:37:07 for table definition.
Thank you,
Fallon -
Linked report from second level drill-down level
Hi,
I have a report with two drill-down levels, Dept Id and Job Id.
The requirement is when I am on Job Id drill level; I have to call another report when I click on any of the Job Id. This Job Id is passed to another report and the report is filtered based on that Job Id.
I created a hyperlink on Job Id drill down level successfully. But the problem is I am unable to go to the first level i.e Dept Id. Actually the hyperlink is displayed and the up arrow is not visible to go to the first level.
Is there any way where after creating a link on second level and opening the report in a new window, the drill up functionality can be maintained?
I am using Business Objects XI 3.1 version.
Thank you.hi
there is another way to drill down the report of web intelligence.for that we have to customize in the universe level create a folder in custom hierarchy and add your two objects to that folder, i.e empid. and deptid. the order of these objects should be in the way the drilling happens that means if you want to drill down from empid. to deptid. then empid. should be the first object of the folder,save and export the universe to the CMS.Then it ready to use for webi report.Build the query for the report and enable the drill option in the report.Now the report is ready for your requirement.
thanks & regards
Sreekanth K -
Tree View Second level is not displaying bind parameter
Studio Edition Version 11.1.2.2.0appears this problem is addressed in
http://dailydevfixes.blogspot.com/2011/07/setting-bind-parameters-on-hierarchy-of.html
unfortunately I must be missing something.
as a test using the hr schema
I was doing a tree view with hire date as the first level then the employee id, last name and first name as the second level.
I hard coded employee id of 187 on a bean called by a button.
the first level is updated unfortunately the second level is not (employee id 107 should not show up)
--1999-02-07
----- 187 Cabrio Anthony
----- 107 Lorentz Dianahere is my bean the first level is updated but the second level is not not quite sure what I am missing
public void ButtonClick(ActionEvent actionEvent) {
BindingContext bindingctx = BindingContext.getCurrent();
BindingContainer bindings = bindingctx.getCurrentBindingsEntry();
DCBindingContainer bindingsImpl = (DCBindingContainer) bindings;
DCIteratorBinding dciter = bindingsImpl.findIteratorBinding("ParentVO1Iterator");
ViewObject Parentvo =dciter.getViewObject();
Parentvo.setNamedWhereClauseParam("empid",187);
Parentvo.executeQuery();
AttributeDef attrDef = Parentvo.findAttributeDef("ChildVO");
ViewObject childvo = attrDef.getAccessorVO(Parentvo);
childvo.setNamedWhereClauseParam("empid",187);
childvo.executeQuery();
AdfFacesContext adfFCtx = AdfFacesContext.getCurrentInstance();
adfFCtx.addPartialTarget(treeupdate);
}here is the query for the parent view object.
select trunc(hire_date) hire_dt
from employees
where :empid is null or employee_id = :empid
group by trunc(hire_date)here is the query for the child view object
select trunc(hire_date) hire_dt, employee_id, employee_id||' '||last_name||' '||first_name nm
from employees
where :empid is null or employee_id = :empid
order by trunc(hire_date)here is the view link
<?xml version="1.0" encoding="windows-1252" ?>
<!DOCTYPE ViewLink SYSTEM "jbo_03_01.dtd">
<!---->
<ViewLink
xmlns="http://xmlns.oracle.com/bc4j"
Name="ParentToChildViewLink"
Version="11.1.2.61.83">
<Properties>
<SchemaBasedProperties>
<LABEL
ResId="model.view.link.ParentToChildViewLink_LABEL"/>
</SchemaBasedProperties>
</Properties>
<ViewLinkDefEnd
Name="ParentVO"
Cardinality="1"
Source="true"
Owner="model.view.ParentVO">
<DesignTime>
<Attr Name="_accessor" Value="true"/>
<Attr Name="_finderName" Value="ParentVO"/>
<Attr Name="_isUpdateable" Value="true"/>
</DesignTime>
<AttrArray Name="Attributes">
<Item Value="model.view.ParentVO.HireDt"/>
</AttrArray>
</ViewLinkDefEnd>
<ViewLinkDefEnd
Name="ChildVO"
Cardinality="-1"
Owner="model.view.ChildVO">
<DesignTime>
<Attr Name="_finderName" Value="ChildVO"/>
<Attr Name="_isUpdateable" Value="true"/>
</DesignTime>
<AttrArray Name="Attributes">
<Item Value="model.view.ChildVO.HireDt"/>
</AttrArray>
</ViewLinkDefEnd>
<ResourceBundle>
<PropertiesBundle
PropertiesFile="model.ModelBundle"/>
</ResourceBundle>
</ViewLink>and here is the tree
<af:tree value="#{bindings.ParentVO1.treeModel}" var="node"
selectionListener="#{bindings.ParentVO1.treeModel.makeCurrent}" rowSelection="single"
id="t1" binding="#{myBean.treeupdate}">
<f:facet name="nodeStamp">
<af:outputText value="#{node}" id="ot1"/>
</f:facet>
</af:tree>thanks I am working through that example unfortunately I ran into a problem
previously (in my real application) I was using bind parameters and my query had the following where clause.
( I did this to turn a comma separated list into an in statement)
WHERE :Bind_Batch_NM_Comma_Sep_List IS NULL
OR batch_nm IN
( SELECT REGEXP_SUBSTR (:Bind_Batch_NM_Comma_Sep_List,
'[^,]+',
1,
LEVEL)
batch_nm
FROM DUAL
CONNECT BY LEVEL <=
REGEXP_COUNT (:Bind_Batch_NM_Comma_Sep_List,
+ 1)however in the example presented you are to create view criteria and there is a panel on the right called view object where clause but I can not figure out how to type into it directly
and I find it unlikely I can recreate this where clause using the add item button.
is there a way to manually type the where clause in the view object where clause box? -
Determining second level approver for travel expense claim workflow
Hi Experts...
In Travel Expense claim workflow,we are using two level Approval.The employee has to enter his data for expense claim through ESS..Then expense claim is submitted and sent via workflow to the Travel department. Travel Dept verifies the expenses against the bill and approves the claim by selecting the next level approver and attaching the scanned copies of the bill.
I made copy from the standard workflow WS20000040.
How can i select the next level appover in first level approval step???
Is there any FM or BAPI or BADI???
Please help me ...
Thanks in Advance
Regards,
Hemalatha.Hi Hemalatha,
I have small tricky workaround to find out the second level of approver.The Standard Rule available can reused again by passing manager's Position.i.e
After first level completed , store manager position in container variable and pass it to the same task rule so the task is sent to the manager's approver .
Message me if needed more details.
**Award Points if useful -
Second level detail in master-detail via VL does not return rows
Sorry, I did not want to repost the entire thread. Please see the last entry in the following thread for my urgent question.
second level detail in master-detail-detail does not return rows
"second level detail in master-detail-detail does not return rows"
Thanks so much!
TeriAhhh ... that explains everything!
You wrote:
ListView1
-> ListRowView2 (via ListRowFkLink1)
-> ListValueView2 (via ListValueFkLink2)
That's why I thought it's a master and two details.
But it's more like:
ListView1
-> ListRowView2 (via ListRowFkLink1)
-> ListValueView2 (via ListValueFkLink2)Is that correct?
That's the explanation.
A ViewLink is basically a RowSetIterator controlling a detail RowSet. When the iterator navigates, the detail RS is refreshed.
When you create a hierarchy in the wizard, the controlling master iterator is always the default iterator! But you used a new iterator (listRowIter) to iterate over your first detail. The default iterator of that first detail didn't move, hence the RowSet of your second detail was not refreshed.
When you navigate in the tester, the tester always uses the default iterator. That's why it worked there.
Sascha -
Multi level hierarchy AdvancedDataGrid
Hey guys,
I have create a data struct as follows
{env:"Marine"
children:[
{name: "name1",
size: "size1",
children:[
{complete: "val-1",
incomplete: "val-2"}
I can display the first leve of hierarchy no problem, similar to example here (http://ticore.blogspot.com/2008/04/flex-collapsible-datagrid.html). What I would really like to do is have, the second level expand so I can display values of complete and incomplete and other under the second child, eventually instead of displaying the values under second child, I want to create pie charts and have them expand/hide as user chooses.
Does anyone have any pointers? I did google but didn't find anything that could help.
Thank you
JaysheelHey Guys,
I have figured out how I could create a chart based on data input. Only thing I need to do is have a Grid looking similar to the one here
http://ticore.blogspot.com/2008/04/flex-collapsible-datagrid.html
I just need not a way to expand each record, and display pie charts. In the case of example above, I need to have it such that I can expand each person's record and see a pie chart. I am banging my head against this one, and I have a feeling that I am overlooking something quite simple
Thank you
Jaysheel -
Steps required for second level approval Workflow
Hi,
Can any one explain me step by step procedure of how to configure 2 level approval process in SRM.I have activated the second level approval for SC.But after this what i have to do. Where can i set the value conditions in workflow?How system will decide for one level approval it has to go for a person "Y" and for 2nd level approval it has to go to Manager?
kindly help me out in this
regards
subbramanyamI think you have to activate the below workflows in the system which automatically identifies the number of levels that it should cross.
WS14000133
WS10000049
WS14000134 ---> This Sub workflow determines, is there any next approver or not?. -
Failed validation as a level hierarchy
Hi,
I have dimension called SKU in my analytic workspace with a hierarchy PRODUCTS defined as ALLPRODUCTS<--MD<--MG<--PG<--STYLE<--PRODUCT. I have used composite keys as Members to maintain uniqueness. For example the member expression for PG is CUBE_DEV.DIMSKU.MDID || CUBE_DEV.DIMSKU.MGID || CUBE_DEV.DIMSKU.PGID. I'm not using Surrogate keys. When I hit the maintain Dimension SKU, LOAD NO SYNCH succeeds but the compile step fails with error
"INI: error creating a definition manager, Generic at TxsOqConnection::generic<BuildProcess>INI: XOQ-01712: "SKU.PRODUCTS" failed validation as a level hierarchy., Generic at TxsOqStdFormCommand::execute"
I looked at the rejected records and every record has the error "(XSRWLD13) Cannot change the level of a dimension member within a single load." Can anyone help me resolving this issue ?
I'm using AWM 11.2.0.1.0 on Oracle 11g R2 server.
Thanks,
RKDavid,
I looked at the data and found out that there were NULLs in many key columns. I updated all of them to the value 'Unknown'. Also I re-implemented Composite keys because I thought Type 2 dimension would pose problem in determining uniqueness. Now there are no errors and I could successfully load data into the dimension.
Below is the latest definition
<!DOCTYPE Metadata [
<!ENTITY % BIND_VALUES PUBLIC "OLAP BIND VALUES" "OLAP METADATA">
%BIND_VALUES;
]>
<Metadata
Version="1.2"
MinimumDatabaseVersion="11.2">
<StandardDimension
Name="SKU"
ETViewName="SKU_VIEW"
ETKeyColumnName="DIM_KEY"
ETLevelColumnName="LEVEL_NAME"
ETMemberTypeColumnName="MEMBER_TYPE"
ETDimensionOrderColumnName="DIM_ORDER"
DefaultHierarchy="PRODUCTS"
ETHierarchyOrderColumnName="HIER_ORDER"
ShortValueDescriptionAttribute="SHORT_DESCRIPTION">
<Organization>
<AWPrimaryDimensionOrganization
AW="&AW_NAME;"
AddUniqueKeyPrefix="True"
MVOption="NONE"
HierarchyConsistencyRule="CONSISTENT">
<MVCreationOptions
RefreshType="COMPLETE"
RefreshOn="DEMAND"
UsingConstraintsClause="TRUSTED">
</MVCreationOptions>
<DefaultBuild>
<![CDATA[BUILD SPEC SYS_DEFAULT
LOAD,
COMPILE
)]]>
</DefaultBuild>
<AttributeOrganization
Attribute="SHORT_DESCRIPTION">
</AttributeOrganization>
</AWPrimaryDimensionOrganization>
</Organization>
<DimensionLevel
Name="MERCHDIVISION"
ETKeyColumnName="MERCHDIVISION">
<Description
Type="LongDescription"
Language="AMERICAN"
Value="MERCHDIVISION">
</Description>
<Description
Type="ShortDescription"
Language="AMERICAN"
Value="MERCHDIVISION">
</Description>
<Description
Type="Description"
Language="AMERICAN"
Value="MERCHDIVISION">
</Description>
</DimensionLevel>
<DimensionLevel
Name="MERCHGROUP"
ETKeyColumnName="MERCHGROUP">
<Description
Type="LongDescription"
Language="AMERICAN"
Value="MERCHGROUP">
</Description>
<Description
Type="ShortDescription"
Language="AMERICAN"
Value="MERCHGROUP">
</Description>
<Description
Type="Description"
Language="AMERICAN"
Value="MERCHGROUP">
</Description>
</DimensionLevel>
<DimensionLevel
Name="PRODUCTGROUP"
ETKeyColumnName="PRODUCTGROUP">
<Description
Type="LongDescription"
Language="AMERICAN"
Value="PRODUCTGROUP">
</Description>
<Description
Type="ShortDescription"
Language="AMERICAN"
Value="PRODUCTGROUP">
</Description>
<Description
Type="Description"
Language="AMERICAN"
Value="PRODUCTGROUP">
</Description>
</DimensionLevel>
<DimensionLevel
Name="STYLE"
ETKeyColumnName="STYLE">
<Description
Type="LongDescription"
Language="AMERICAN"
Value="STYLE">
</Description>
<Description
Type="ShortDescription"
Language="AMERICAN"
Value="STYLE">
</Description>
<Description
Type="Description"
Language="AMERICAN"
Value="STYLE">
</Description>
</DimensionLevel>
<DimensionLevel
Name="PRODUCT"
ETKeyColumnName="PRODUCT">
<Description
Type="LongDescription"
Language="AMERICAN"
Value="PRODUCT">
</Description>
<Description
Type="ShortDescription"
Language="AMERICAN"
Value="PRODUCT">
</Description>
<Description
Type="Description"
Language="AMERICAN"
Value="PRODUCT">
</Description>
</DimensionLevel>
<Description
Type="LongDescription"
Language="AMERICAN"
Value="sku">
</Description>
<Description
Type="ShortDescription"
Language="AMERICAN"
Value="sku">
</Description>
<Description
Type="Description"
Language="AMERICAN"
Value="sku">
</Description>
<Hierarchy>
<LevelHierarchy
Name="PRODUCTS"
IsSkipLevel="True"
IsRagged="True"
ETParentColumnName="PARENT"
ETDepthColumnName="DEPTH"
ETViewName="SKU_PRODUCTS_VIEW">
<HierarchyLevel
DimensionLevel="MERCHDIVISION">
<HierarchyLevelMap
KeyExpression="DIMSKU.MDID"
Query="DIMSKU">
<AttributeMap
Name="SHORT_DESCRIPTION"
Attribute="SHORT_DESCRIPTION"
Expression="DIMSKU.MDID">
</AttributeMap>
</HierarchyLevelMap>
</HierarchyLevel>
<HierarchyLevel
DimensionLevel="MERCHGROUP">
<HierarchyLevelMap
KeyExpression="DIMSKU.MDID || DIMSKU.MGID"
Query="DIMSKU">
<AttributeMap
Name="SHORT_DESCRIPTION"
Attribute="SHORT_DESCRIPTION"
Expression="DIMSKU.MDID || ':' || DIMSKU.MGID">
</AttributeMap>
</HierarchyLevelMap>
</HierarchyLevel>
<HierarchyLevel
DimensionLevel="PRODUCTGROUP">
<HierarchyLevelMap
KeyExpression="DIMSKU.MDID || DIMSKU.MGID || DIMSKU.PGID"
Query="DIMSKU">
<AttributeMap
Name="SHORT_DESCRIPTION"
Attribute="SHORT_DESCRIPTION"
Expression="DIMSKU.MDID || ':' || DIMSKU.MGID || ':' || DIMSKU.PGID">
</AttributeMap>
</HierarchyLevelMap>
</HierarchyLevel>
<HierarchyLevel
DimensionLevel="STYLE">
<HierarchyLevelMap
KeyExpression="DIMSKU.MDID || DIMSKU.MGID || DIMSKU.PGID || DIMSKU.STYLE"
Query="DIMSKU">
<AttributeMap
Name="SHORT_DESCRIPTION"
Attribute="SHORT_DESCRIPTION"
Expression="DIMSKU.MDID || ':' || DIMSKU.MGID || ':' || DIMSKU.PGID || ':' || DIMSKU.STYLE">
</AttributeMap>
</HierarchyLevelMap>
</HierarchyLevel>
<HierarchyLevel
DimensionLevel="PRODUCT">
<HierarchyLevelMap
KeyExpression="DIMSKU.MDID || DIMSKU.MGID || DIMSKU.PGID || DIMSKU.STYLE || DIMSKU.SKU"
Query="DIMSKU">
<AttributeMap
Name="SHORT_DESCRIPTION"
Attribute="SHORT_DESCRIPTION"
Expression="DIMSKU.MDID || ':' || DIMSKU.MGID || ':' || DIMSKU.PGID || ':' || DIMSKU.STYLE || ':' || DIMSKU.SKU">
</AttributeMap>
</HierarchyLevelMap>
</HierarchyLevel>
<Description
Type="LongDescription"
Language="AMERICAN"
Value="PRODUCTS">
</Description>
<Description
Type="ShortDescription"
Language="AMERICAN"
Value="PRODUCTS">
</Description>
<Description
Type="Description"
Language="AMERICAN"
Value="PRODUCTS">
</Description>
</LevelHierarchy>
</Hierarchy>
<Attribute>
<BaseAttribute
Name="SHORT_DESCRIPTION"
IsVisibleForAll="True"
SQLDataType="NVARCHAR2(100)"
ETAttributeColumnName="SHORT_DESCRIPTION">
<Description
Type="ShortDescription"
Language="AMERICAN"
Value="Short Description">
</Description>
<Description
Type="LongDescription"
Language="AMERICAN"
Value="Short Description">
</Description>
<Description
Type="Description"
Language="AMERICAN"
Value="Short Description">
</Description>
<Classification
Value="STAR"/>
</BaseAttribute>
</Attribute>
</StandardDimension>
</Metadata>
But I'm facing problem if I put Names in Short Description attribute. I have fields MerchGroupName, MerchDivisionName, ProductGroupName, StyleName in the database table which I would love to use for short description. When I use them, the error is
INI: error creating a definition manager, Generic at TxsOqConnection::generic<BuildProcess>INI: XOQ-01600: OLAP DML error "ORA-34034: 1 is already a value of DEMANTRADW!SKU_MERCHDIVISION_SURROGATE." while executing DML "SYS.AWXML!R11_LOAD_DIM('SKU.DIMENSION' SYS.AWXML!___R11_LONG_ARG_VALUE(SYS.AWXML!___R11_LONG_ARG_DIM 1) 'MATCH' 'YES' 'YES' 'SKU.MERCHDIVISION.LEVEL' 'SKU.MERCHGROUP.LEVEL' 'SKU.PRODUCTGROUP.LEVEL' 'SKU.STYLE.LEVEL' 'SKU.PRODUCT.LEVEL' 'SKU.SHORT_DESCRIPTION.ATTRIBUTE' 'SKU.PRODUCTS.HIERARCHY')", Generic at TxsOqStdFormCommand::executeINI: XOQ-01601: error while loading data for Cube Dimension "CUBE_DEV.SKU" into the analytic workspace, Generic at TxsOqStdFormCommand::execute -
Heading level hierarchy errors when topics are in TOC more than once
I have discovered that the hierarchy in the Heading levels in
the Printed Documentation will differ from than in my online help
table of contents hierarchy, and that the problem is due to topics
that are intentionally in the TOC more than once.
For example, in chapter 5 of a particular help system the
hierarchy should be:
Heading 1 < Chapter 5 title from top-level book>
Heading 2 <title of second level book>
Heading 3 <title of topic that appears under second-level
book>*
What I actually get is:
Heading 1 < Chapter title from top-level book>
Heading 2 <title of second level book>
Heading 4 <title of topic that appears under second-level
book>*
* This same topic appeared in an earlier chapter. In that
chapter it was really at a Heading 4 level.
Due to company styles, etc. we use a numbering system at the
headings and in the TOC, so instead of
5
5.1
5.1.1
I erroneously get
5
5.1
5.1.1.1
This type of hierarchy issue appears multiple times in this
particular document (which I inherited by the way.)
Other than restructuring the document to not reuse topics in
different places in the TOC, is there a solution or a workaround
for this problem?
What I am doing so far, is generating the Print Documentation
one chapter at a time. As long as a topic is not reused with the
same chapter, my hierarchy of heading levels is maintained;
otherwise, it is not. Then I can put the chapters back together
after fixing the few places that still have heading level problems.
This however, will be quite cumbersome as this document is
translated into nine other languages.
I am using RoboHelp X5 for Word / Word 2003 for the source
and most of the translations; RoboHelp Asian Edition, Simplified
Chinese / Word 2003 for the Chinese translation. The heading level
hierarchy error occurs in both versions.>> AF: I've commented in sections...
Without Maintain Heading Levels, RH will apply heading levels
to the books and then the topic levels will get bumped down. So a
top level book will be Heading 1 and the Headings in the topic will
get bumped down to 2, 3 and 4 etc. If then you have another book
one level down so that it gets Heading 2 applied, the same topic
but under the level two book would then get 3, 4 and 5 applied.
That is not the original problem but hopefully we are agreed
that is how things work on that.
>> Yes - that is the expected behavior. When it didn't
happen as expected, that's what led me to the discovery of the
cause of the problem (topic reuse).
Your problem was that firstly Heading 3 got bumped to Heading
4 if the same topic was inserted into the TOC twice. I assume it
was OK in the first instance, or is it that when you add it twice
it goes wrong everywhere?
>> Your assumption is correct. First occurrence is
correct. Second, third, and fourth (yes - there is one topic that
is used 4 times! ) are not correct based on TOC hierarchy.
On the numbering, nothing surprises me. If you look at my
site you will see that for RH HTML, i gave up on getting it right.
I have had many queries on this and more than a few people have
indicated they will work on the problem and get it working. I'm
still waiting. There are many posts about outline numbering
problems. Has anyone got it working satisfactorily?
>> I don't really have numbering problems. The
numbering is following the RoboHelp-generated hierarchy and the
.dot template that I apply. It's just that the RH-generated
hierarchy and its heading levels don't correspond to the "real"
hierarchy because of the reuse issue.
I have seen various Word gurus maintain that numbering has
not worked entirely satisfactorily since Word 2! Also enough posts
to convince me this is a Word issue, not a RH issue.
If you want to create a new project and knock something up
that demonstrates this problem, by all means zip it up and send it.
I'll assume it will be a small project and zip to less than 5mb. If
more, contact me first.
>> Unless you have RoboHelp X3 Asian Edition,
Simplified Chinese, there is really no need. I plan to either avoid
the reuse issue in the source, or build the print doc in sections
which is easy enough in RoboHelp X5 for the non-Chinese languages.
It is in the older Asian edition where the problems are compounded
by the omitted reuse topics. If you do have RoboHelp X3 Asian
Edition, Simplified Chinese and want to experiment, I can send you
a cut-down version of the project. Don't feel obligated though;
unless you can read Chinese (I can't) it is very tedious to work
with. -
How to load second level nodes dynamically in jTree?
Hi,
I'm new to jTree & I want to load jTree with two levels of Hierarchy dynamically.
First level nodes I loaded from the database directly.
And regarding the second level nodes, I want them to be loaded only when I expand the first level nodes(on tree expansion), instead of loading it before-hand itself.
I tried this in TreeExpansion event, but still my tree was not refreshed.
Is there anyother way to do this .....?
Thanks.
G.Hi sangar;
use method valueChanged() in ListSelectionEvent interface to notify tree selection change. -
Problem with open in new window for second level tab
Hi Friends,
I am using 2 level tabs in my application. In my second level tab when i right click and select *open in new
window* it is giving Page not found error. But for the first level tabs it is working correctly. How can i fix this so
that either i can show the page when right click the tab and select open in new window or disable the right clicking
for the second level tabs. Please help,
Thanks
JeevHi,
I don't think its exactly possible, as tabs use javascript:doSubmit('somevalue'); and you can not open javascript in a new window, as javascript usually references the current page you are on, and since you open the javascript in a new window, it doesn't know what to reference. The most helpful thread I found was : Re: Open other tab in a new window (ATD reply, third from the bottom).
Ta,
Trent
Edited by: tr3nton on Dec 3, 2009 4:19 PM; Hari beat me to linking to the correct thread, my bad. -
Issue with Skip Level Hierarchy in OBIEE 11g
Hi,
I have implemented Ragged and Skip Level Hierarchy as explained in the links below in OBIEE 11g RPD.
(checked the 'Ragged' and 'Skipped Levels' check boxes)
http://www.rittmanmead.com/2010/07/obiee-11gr1-support-for-ragged-skip-level-value-based-hierarchies/
http://docs.oracle.com/cd/E17904_01/bi.1111/e10540/dimensions.htm#BABFBBFG
When the Presentation Hierarchy is dragged in the OBI Answers, the leaf level beyond the skip (null) levels is not shown in the report.
When any level finds intermediate null values, OBIEE is failing to show the existing value of the leaf level (Most Granular Level) or any values after Skipped Levels.
For example, following is the values in database for different levels of department hierarchy.
A -> B -> C -> Null -> Null -> F
The OBIEE Presentation Hierarchy can only drill down till C, not beyond that. (does not show the leaf level value 'F').
Could you please suggest whether I am missing any step?
Thanks.Hi, My problem is that in my report it is showing me that levels as -- A -> B -> C -> Null -> Null -> F, however I want to show data as A -> B -> C -> F, i.e the null valus(columns) should be skipped. Please help.
Thanks and Regards,
Deepak -
What is the Purpose of Account Hierarchy Manager
Dear Members
Advantages of Account Hierarchy Manager.
Regards
PadarthyHi,
You question is answered in "Oracle General Ledger User Guide", Chapter 7 - The Account Hierarchy Manager.
Applications Releases 11i and 12
http://www.oracle.com/technology/documentation/applications.html
Regards,
Hussein
Maybe you are looking for
-
IPhone 5S call quality / volume issue. Please help.
Hi, Please can anyone help? I have an iPhone 5S and callers frequently complain (9 out of 10) that the volume fades in and out and my voice sometimes sounds robotic, i.e. digital interference. I always hold the iPhone in the same manner as any other
-
Updated to itunes 7 and music library appears empty
Upgraded from itunes 6 to 7. Open itunes and nothing displays from the Music Library. I changed the Prefs/Advanced/General itunes music folder to point to where my music folder is but it still doesn't display anything in that folder. When I used itun
-
Flash player file will not open
Flash player 14.0 will download a 1.0 MB file but the file will not open, using windows 8.1 with firefox
-
Unable to play External Midi Instruments in Logic Express
Hi, I have a Yamaha Keyboard which is connected to my Mac via a usb midi cable (Edirol). I have installed the driver for the midi cable and have set it up properly in the "Audio Midi Setup". However when I am using Logic Express, I just do not know w
-
Transport Order to 2 TMS Domains
Hello, I want to know how can I transport an order to 2 TMS Domains? I Think I can't do it in the STMS Transaction. But I think I can Call an External Instante, right? to one of the Domains?. Thank you in Advance.