HRI Load All Competence Level Hierarchy Concurrent programm

HRMS application
11.5.10.2
windows 2003
db 10.2.0.4
How do I do the following?
Run the HRI Load All Competence Level Hierarchy concurrent program with the following parameters:
o Collect From Date: earliest reporting date required
o Collect To Date: current date (default)
o Full Refresh: Yes (default)
You should incorporate the above process into your Request Group.
I can see Concurrent : Program/define but not in submit request drop down.
Immediate Help is appreciated
Thanks.

I am able to do this.
I was registering under wrong security group.
Thanks.

Similar Messages

  • Oracl concurrent programme or a pl/sql package

    Hello all,
    I have a concurrent programme which is calling a package. How can i debug it? I mean,as the programme takes a day to run, i need to know where exactly in the package is the control...
    Any help is appreciated.
    Thanks

    there are many ways to debug a code. one is to run the code manually to check for any errors that might be thrown. second if there are no oracle error and if you are looking for logic or data error you might want to use [dbms_output.put_line()|http://www.psoug.org/reference/dbms_output.html] package to each line of code to see what might your code is returning a data. hope this helps.

  • Data loaded all level in a hierarchy and need to aggregate

    I am relatively new to Essbase and I am having problems with the aggregation of cube.
    Cube outline
    Compute_Date (dense)
         20101010 ~
         20101011 ~
         20101012 ~
    Scenario (dense)
    S1 ~
    S2 ~
    S3 ~
    S4 ~
    Portfolio (sparse)
    F1 +
    F11 +
    F111 +
    F112 +
    F113 +
    F12 +
    F121 +
    F122 +
    F13 +
    F131 +
    F132 +
    Instrument (sparse)
    I1 +
    I2 +
    I3 +
    I4 +
    I5 +
    Accounts (dense)
    AGGPNL ~
    PNL ~
    Porfolio is a ragged hierarchy
    Scenario is a flat hierrachy
    Instrument is a flat hierarchy
    PNL values are loaded for instruments at different points in the portfolio hierarchy.
    Then want to aggregate the PNL values up the portfolio hierarchy into AGGPNL, which is not working the loaded PNL values should remain unchanged.
    Have tried defining the following formula on AGGPNL, but this is not working.
    IF (@ISLEV (folio,0))
    pnl;
    ELSE
    pnl + @SUMRANGE("pnl",@RELATIVE(@CURRMBR("portfolio"),@CURGEN("portfolio")+1));
    ENDIF;
    using a calc script
    AGG (instrument);
    AGGPNL;
    Having searched for a solution I have seen that essbase does implicit sharing when a parent has a single child. This I can disable but this is not the sole cause of my issues I think.

    The children of F11 are aggregated, but the value which is already present at F11 is over wriiten and the value in F11 is ignored in the aggregation.^^^That's the way Essbase works.
    How about something like this:
    F1 +
    ===F11 +
    ======F111 +
    ======F112 +
    ======F113 +
    ======F11A +
    ===F12 +
    ======F121 +
    ======F122 +
    ===F13 +
    ======F131 +
    ======F132 +
    Value it like this:
    F111 = 1
    F112 = 2
    F113 = 3
    F11A = 4
    Then F11 = 1 + 2 + 3 + 4 = 10.
    Loading at upper levels is something I try to avoid whenever possible. The technique used above is incredibly common, practically universal as it allows the group level value to get loaded as well as detail and agg up correctly. Yes, you can load to upper level members, but you have hit upon why it isn't all that frequently done.
    NB -- What you are doing is only possible in BSO cubes. ASO cube data must be at level 0.
    Regards,
    Cameron Lackpour

  • Loading All Levels of BOM data to BW

    Hi Experts,
    I am loading all BOM data that is all levels of BOM data to BW. can anyone suggest me the steps using what should i create generic exctractor FM or view on tables (MAST,STKO,STPO) ?? please give me the detailed steps for the loading data to BW from R/3. because i want to do reporting at any level. ?
    vikrant

    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b0af489e-72b1-2b10-159d-abb8058fb88d?quicklink=index&overridelayout=true
    Just check if this helps
    Prathish

  • 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,
    RK

    David,
    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 || &apos;:&apos; || 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 || &apos;:&apos; || DIMSKU.MGID || &apos;:&apos; || 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 || &apos;:&apos; || DIMSKU.MGID || &apos;:&apos; || DIMSKU.PGID || &apos;:&apos; || 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 || &apos;:&apos; || DIMSKU.MGID || &apos;:&apos; || DIMSKU.PGID || &apos;:&apos; || DIMSKU.STYLE || &apos;:&apos; || 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

  • Data loading at different levels

    We are using Oracle 10g and AWM 10.2 tools to re-write the current Oracle Express application. We have created couple of standard cubes in AWM and it works fine. The design confusion is in one of the case. It is explained below
    We are planning to load targets into one of our AW.
    Following are the details
    Dimensions hierarchy
    1. Time Year==> quarter==> Month
    2. Point Of Sale(POS) Worldwide ==> Region ==> Country ==> Territory
    3. Origin Worldwide ==> Country ==> Territory ==> City
    4. Destination Worldwide ==> Country ==> Territory ==> City
    Measure
    rev_tgt
    The challenge is, the target are set in the warehouse at different Point Of Sale levels. i.e. For some POS the targets are set at country level, for some they are set at territory levels. e.g. For India the revenue targets are set only at country level where as for France the targets are set at all the territories of France. The requirement is to show targets at all the levels in the POS above where it is set. The bottom line is that the data is not availble at a fixed level and the dimesion levels are fixed and cannot be ragged.
    Query:
    How we can design a cube that loads data at different levels and then aggregate the same across all dimension including the higher level of POS dimension.
    Solution in the existing Oracle Express
    In the current Oracle Express, what we are doing is since we have control over the aggregate program, we have created two aggmaps one with POS and one without. We do two step aggregate for the first one we limit the POS to country level and do a rollup using the aggmap that includes POS. Then we limit POS to all and aggregate using the aggmap without POS.
    Can you please assist us on how to implement the above with the AWs.

    Hi,
    Check the below wiki link,
    http://wiki.sdn.sap.com/wiki/display/BI/Aggregates--SAPBWQueryPerformance
    Edited by: Priya.D on Apr 8, 2010 3:20 PM

  • Macmail keeps loading all messages -  help??

    im on tour w my new macbook pro.   every few cities when I get online the mail program loads all 12,000 plus messages from this year last year whenever.. and i delete and then it does it again. I have restarted of course.  any advice?? 

    Microsoft Live and Any apple programme do not talk to each other. I am using LIVE and i recently upgraded my IPhone to loose all my contacts and calanders. You MUST HAVE OUTLOOK installed on your computer. IPhone backs up all contacts and calenders to outlook only not LIVE.

  • Master Data load does not extract Hierarchy nodes in BPC Dimension ACCOUNT

    Hi Experts,
    I am performing master data load through standard DM package with Filter selection as:
    1. Chart of Accounts
    2. Hieararchy selection has 4 hierarchy names
    3. Selected Import Text nodes
    4. Selected Set Filters by Attribute OR Hierarchies
    I have run this DM package for a set of data and selections a week ago and it worked fine.
    However when i run it now, it is giving issues,
    It extracts any new GL maintained in the BI system however it does not extract any hierarchy nodes at all! (Have tested this by deleting the hierarchy nodes and tried to run the master data load)
    I am running the DM package in Update and have selection as External.
    Any sugestions for checks / has anyone encountered this issue earlier?
    Regards,
    Shweta Salpe

    Hi Guyz,
    Thanks.
    I found that the issue was with the transformation file where i was maintaining the RATETYPE.
    When i removed the mapping of RATETYPE this works fine. (Pulls the nodes of hierarchies)
    however now i do not have Ratetype populated in the system.
    my rate type mapping is:
    RATETYPE=*IF(ID(1:1)=*STR(C) then *STR(TOSKIP);ID(1:1)=*STR(H) then *STR(TOSKIP);ID)
    and in conversion file i have TOSKIP     *skip
    I have to skip the ratetypes for the hierarchy nodes and my hierarchy nodes start with C and H.
    So now that i have removed the mapping for RATETYPE can anyone suggest me a correct way to achieve this? (Note the above mapping formula was skipping all of the hierarchy nodes starting with C and H)
    Regards,
    Shweta Salpe

  • Ragged Hierarchy and Skip Level Hierarchy

    Hi all,
    I am confused with ragged and skip level hierarchy, as i read some documents related to obiee 11g.
    Will you please explain with an example the difference between ragged hierarchy and skip level hierarchy and also when to use these hierarchies?
    regards
    chandra kanth.

    Chandra Kanth,
    Hope this helps you
    http://blogs.simba.com/.a/6a00e3932f172e88340133f4d758b5970b-800wi
    Thanks,
    Saichand.v

  • The error message "No more virtual tiles can be allocated" appears when I try to use the effects in the quick editing mode in my Elements 13. The baton OK has to be pressed several times for loading all effect patterns. The error returns when selecting th

    The error message "No more virtual tiles can be allocated" appears when I try to use the effects in the quick editing mode in my Elements 13. The baton OK has to be pressed several times for loading all effect patterns. The error returns when selecting the particular pattern.
    The problem does not appear, if PH Elements 13 is executed in the administrator mode.
    The available computer resources are rather  large enough: CPU INTEL i7 4 cores,  16GB RAM, 1TB HDD + 32GB SSD, Windows 8.1.
    Please, advice how to solve this problem? Maybe, there is patch or updating available?

    Dear n_pane,
    Thank you for the quick answer. In the meantime I found other way to pass by the problem. I increased the cache level up to the maximum value 8.
    The errors reported as "No more virtual tiles can be allocated" vanish, but I still do not understand, why PSE 13 cannot work properly by the lower cache levels, having available maximum resources it needed (10443 MB RAM and 26.53GB SSD space for scratches), or cannot collaborate with the fast SSDs properly.
    I wish you all the best in the New Year 2015!

  • Loading on Aggregated Levels

    when i am loading the data from cube to PA, i see there is good change in the total qty in PA. I see the numbers are different if i load on aggregated levels ( say if i load on just 3 chars out of 10) to the load on detailed level.
    Why this should change in the totals ?
    Any idea ?
    Thanks
    venkat

    hi
    when i am loading the data from my backup cube to PA, I am loading on 3 chars (grouping condition) out of total 10 chars. I have just loaded one KF from cube to the same KF in PA. Then i see my qty in PA is much higher than whats there in the cube as totals. I am confused why i should get more data than the cube. I understand if its less, may be deletion of CVCs, etc.. But how its getting increased to ?
    What does exactly the grouping condition mean ? I understand that all records are grouped under those chars in totals and disaggregates later. But i am seeing my PA totals dont match with the Cube totals. Cube totals found to be lesser than PA totals.
    fully confused with this.
    thx
    venkat

  • ERPI: how to load only parent level metadata to Planning from EBS

    Hi, experts.
    Can we load only parent level metadata of EBS R12 to Planning using ERPI 11.1.2.2 ?
    And can we make selections on which members to load its metadata to Planning ?
    Thanks a lot.
    Eddy

    Hi,
         I m going with forecast in Step 5. But have to cross a pair of radio button in Step 3 as 'All Items' or 'Selected Items'.
         I m explaining my requirement again. I ll use the 'All Items' radio button and in the last step the recommendations are displayed for the expected child items along with the materials which are not in that specific BOM but has the demand.
         Though the other materials may have demand, it is not to be displayed in my order recommendation because I have not created the forecast for that items which I used in my MRP WIzard.
    Hope you got my problem.
    Thanks
    Karthik

  • Multiple Levels Hierarchy - Value Sets

    Hello all,
    I have a request from our client to create a four level hierarchy in E-Business Suite. I have tried creating dependent value sets but with this way I can create only two levels hierarchy since I can not make the dependent value set parent of another value set.
    Does anybody have any idea?
    Thank you in advance,
    Christina

    Hi Hiren,
    According to your description, you will not select Country, State & City at the same time, right?
    So as per my understanding, you needn't to create the hierarchy, just create three attributes Country, State and City. Then when you select one of the attributes in the PowerPivot table, the attribute can be the filter which you can see on the screenshot
    below.
    Regards,
    Charlie Liao
    TechNet Community Support

  • Poweshell script to parse a XML document to get all Leaf level nodes with Node names in CSV

    Hi Experts,
    I want to write a Powershell script to parse a XML document to get all Leaf level nodes with Node names in CSV
    <?xml version="1.0" encoding="UTF-8"?>
    <CATALOG>
       <CD>
          <TITLE>Empire Burlesque</TITLE>
          <ARTIST>Bob Dylan</ARTIST>
          <COUNTRY>USA</COUNTRY>
          <COMPANY>Columbia</COMPANY>
          <PRICE>10.90</PRICE>
          <YEAR>1985</YEAR>
       </CD>
    </CATALOG>
    Need to display this as
    CD_Tiltle, CD_ARTIST, CD_COUNTRY, CD_COMPANY, CD_PRICE, CD_YEAR
    Empire Burlesque, Bob Dylan,USA,Columbia,10.90,1985
    and so on..
    I do not want to hard code the tag names in the script.
    current example is 2 level hierarchy XML can be many level till 10 max I assume
    in that case the csv file field name will be like P1_P2_P3_NodeName as so on..
    Thanks in advance
    Prajesh

    Thankfully, I have writtenscript for ths same $node_name="";
    $node_value="";
    $reader = [system.Xml.XmlReader]::Create($xmlfile)
    while ($reader.Read())
    while ($reader.Read())
    if ($reader.IsStartElement())
    $node_name += "," + $reader.Name.ToString();
    if ($reader.Read())
    $node_value += "," + $reader.Value.Trim();
    Thanks and Regards, Prajesh Please use Marked as Answer if my post solved your problem and use Vote As Helpful if a post was useful.

  • 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.

Maybe you are looking for