Temporal Hierarchy Join

Hi all,
Can any one explain me the concept of
Use Temporal Hierarchy Join
Use this to indicate whether the "Temporal Hierarchy Join" feature is to be used for this characteristic with time-dependent hierarchies With an good example?

Hi Sunil,
Have a read through these and any questions then let me no.
http://help.sap.com/saphelp_nw70/helpdata/EN/80/1a6702e07211d2acb80000e829fbfe/frameset.htm
http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3414800)ID0649628450DB21019087468887407824End?blog=/pub/wlg/3113
http://help.sap.com/saphelp_nw04s/helpdata/en/03/eca042bde0c611e10000000a1550b0/content.htm
I have implemented it once in a HR scenario.
Cheers,
Nick.

Similar Messages

Temporal hierarchy join - validity (0TCTVINTV)

Hello experts,
today it is a hierachy display problem in a report:
We present a time dependent hierarchy structure with a temporal join. This is to have the postings in the correct periods of the hierarchy. A characteristic of this hierarchy is the validity period. This validity period is default displayed in the report. This cannot be suppressed in the query designer. Is there a way to suppress this?
Can you please help us with a sloution?
Thanks in advance.

Hi,
Were you able to solve this issue? I noticed that once you activate the temporal hierarchy join option in the orgunit the system automatically creates a new characteristics called 0orgunit1 and the validity 0TCTVINTV in this characteristic is 1 in the order of F4 column. The problem is that you cannot put 0orgunit1 into change mode and therefore it is not possible to change this value to 0. But were you somehow able to solve this issue?
Kind regards
Sara

Temporal Hierarchy Join activation error

Dear ALL,
I have activate the Hierarchy for 0CUST_SALES with CHECK the Radiobutton Time u2013Dependent Hierarchy Structure AND CHECK use Temporal Hierarchy Join.
I have generated also 0CUST_SALE1 for this CHECK.
When I use the Data Transfert Processes for import data to 0CUST_SALES(ATTR), I have the run time error for
SAPSQL_INVALID_FIELDNAME
Exception              CX_SY_DYNAMIC_OSQL_SEMANTICS .
The cause for this problem is the check use Temporal Hierarchy Join .
And the error Is in the include program u201CLRRSIF02u201D (procedure "VALUE_TO_SID_CONVERT_ASO") when execute this statement:
   SELECT SINGLE sid FROM (i_sidtab)
            INTO <l_s_valsid>-sid
            WHERE sidrange = <l_sidrange>
              AND nodename = <l_nodename>
              AND datefrom = <l_datefrom>.
   IF sy-subrc NE 0.
     <l_s_valsid>-sid = rrsi_c_sid-not_exist.
   ENDIF.
ENDLOOP.
The (I_sidtab) is the table u201C/BI0/KCUST_SALESu201D, this table donu2019t have datefrom.
Is there a procedure for implementing Temporal Hierarchy in existing IO 0CUST_SALES ?
My SAP BI 7.0 has support packages 17.
Thancks.
Roberta

Try to apply the following OSS Note:
[OSS Note 1135854 - Follow-up note for Note 1132195|https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1135854]
This OSS Note does make corrections modifications to the LRRSIF02 INCLIUDE for procedure VALUE_TO_SID_CONVERT_ASO. as the name suggests, this OSS Note will most likely require that [OSS Note 1132195 - Reducing the read accesses to RSDCHATHJ|https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1132195] be applied first.

Hierarchy structure with temporal hierarchy join

Hi guys,
For characteristic Cost Element, Im using a time dependant hierarchy structure with temporal hierarchy join. In the query, Im selecting select hierarchy and From data, derivation.
If the hierarchy is created in SAP BI or if the hierarchy is imported from Excel, query is working properly.
If the hierarchy is imported from SAP ECC, the query giving me an error:
ABEND BRAIN (336): Hierarchy "xx" from characteristic 0COSTELMNT can be used here
Someone can tell me if its normal or if there is a way in order to correct this problem.
Thanks in advance,
Rubé

Hi guys,
For characteristic Cost Element, Im using a time dependant hierarchy structure with temporal hierarchy join. In the query, Im selecting select hierarchy and From data, derivation.
If the hierarchy is created in SAP BI or if the hierarchy is imported from Excel, query is working properly.
If the hierarchy is imported from SAP ECC, the query giving me an error:
ABEND BRAIN (336): Hierarchy "xx" from characteristic 0COSTELMNT can be used here
Someone can tell me if its normal or if there is a way in order to correct this problem.
Thanks in advance,
Rubé

Problems with temporal hierarchy join in BI7.0

Hello,
I am using the new feature temporal hierarchy join which enables viewing historical data over a time-dependent hierarchy.
Now this works fine as long as the hierarchy is being used in rows or columns. However if I use a hierarchy node as a selection in a structure element, the temporal hierarchy join does not work properly.
Does anyone have an idea if this should be supported?
Thanks in andvance,
Patrick

Hi Jorge,
we have BI Patch 15. I tried to find out which notes were implemented to solve the Problem.
I'm not sure which note was the leading note, but following notes were implemented:
0001061525
0001055725
0001051170
0001042353
0001041760
0001040649
0001039979
0001038008
0001036536
0001029689
0001024554
0001009908
0001002662
0001010516
Since then there have been further notes concerning different problem with the temporal hierarchy join.
I hope these will help to solve the initial problem.
Regards,
Patrick

Temporal Join Hierarchies

Hi,
I am currently working on BW HR reporting and in that context temporal join of hierarchies seems relevant for reporting organizational assignment.
Three questions:
1. I can see that temporal join of hierarchies must be enabled on infoobject level, e.g. on 0ORGUNIT. Will it afterwards be necessary to enable it on hierachy or query level? We do not want to get in a situation where just enabling temporal join of hierarchies on infoobject level affects existing hierarchies or reports based on this infoobject.
2. To what degree will performance be affected?
3. Will temporal join of hierarchies work in both BW 3.5 and BI 7 reporting environments? (We have done a technical upgrade to BI7 but still using BW 3.5 queries / web templates)
Appreciate any input on this!
thanks,
Ørnulf Andresen

Dear Ørnulf,
1. Besides enabling it on InfoObject level, you also have to specify settings in the query designer (in the properties of the query).
2. Performance will be affected, because the hierarchy could be larger than with a single key date. If necessary you can also increase the hierarchy buffer (notes exist).
3. For using temporal hierarchy join, you must make the settings in the Query Designer 7.0. But the query can be used in 3.x templates
Kind regards,
Luc Boodts

Temporal Join

Hi gurus,
Can anyone explain me in detail about the temporal join in the hierarchy.
thx in advance.

Hi........
Use of Temporal Join :
The temporal join of time-dependent hierarchies allows you to view the leaves within a hierarchy under two (or more) nodes, depending on the validity period (attribute of the characteristic value).
To use this function you have to select the indicator for the "Use temporal hierarchy join" option. You make this setting in InfoObject maintenance on the "Hierarchy" tab page.
http://help.sap.com/saphelp_nw04s/helpdata/en/11/723c3b35703079e10000000a114084/content.htm
Check these links :
http://help.sap.com/saphelp_erp2004/helpdata/en/11/723c3b35703079e10000000a114084/content.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/03/eca042bde0c611e10000000a1550b0/frameset.htm
Hope this helps you.........
Thanks == Points as per SDN..........;)
Regards,
Debjani..........
Edited by: Debjani Mukherjee on Oct 1, 2008 12:43 PM
Edited by: Debjani Mukherjee on Oct 1, 2008 12:44 PM

Generated authorizations on 0ORGUNIT - Time-dep.hier.struct&Temp.hier. join

Hello gurus,
We use generated hierarchy authorization for 0ORGUNIT with Time dependent heirarchy structure & Temporal hierarchy join.
Authorization objects (RSR_*) seems to generate well, however they don't work - query ends with EYE 007 message.
If I make a copy of generated authorization object and split it into two objects - one with very the same 0ORGUNIT limitation and the rest of original auth. object, it suddenly works!
So I don't know what's wrong whether the generation of authorization or evaluation process.
We use EHP1 with 05 support package.
BR
Ondrej

Ondrej,
Please refer to the below post, it is helpful.
Re: BI HR Structural Authorizations
Also, refer to the below document. It is old but provides very useful steps to be followed.
[http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/business-intelligence/a-c/bw_hr%20authorization%20-%20asap%20for%20bw%20accelerator]
Update your findings.
-Mann

Error while actvating Transformation

Gurus,
I've changed a DSO, i.e., added new InfoObjects . All the fields are mapped properly.
When I'm actvating transformation - its giving me error messages
- Error while activating transformation - RSTRAN510
- Error when writing routines - RSAA561
- Error when activating Transformation 0KC0IK6EYKKG22LW9MN80OV6H9RUZWNR - RSO404
I tried the following:
1. Tried actvating the Transformation after deleting data from DSO.
2. Tried logging off /nrsal and performed Actvation.
To Update:
1. There is no start routine and end routine written for this DSO.
Can anybody help me in fixing this problem.
Regards,
Yaseen

Hi,
InfoObjects: Deleting temporal hierarchy join in target syst, or due to deleting routines or even you can get this msg when you had not assigened the Units.
Go though the below SAP Notes and link for your reference...
[/message/1410802#1410802 [original link is broken];
apply the SAP Notes
SAP Note Number: 1100975
SAP Note Number: 979487
if you had resoved the issue...do let me know the approach...
regards,
NR

ABAP Run time error "UNCAUGHT_EXCEPTION" "CX_RSR_PROPAGATE_X"

Hi Gurus,
*This error occured after loading the Hierarchy & while saving the Hierarchy.*
Short text
    An exception occurred that was not caught.
What    happened?
    The exception 'CX_RSR_PROPAGATE_X' was raised, but it was not caught anywhere
     along
    the call hierarchy.
Since exceptions represent error situations and this error was not
    adequately responded to, the running ABAP program
     'CL_RRHI_INCL_CREATOR==========CP' has to be
    terminated.
Error analysis
    An exception occurred which is explained in detail below.
    The exception, which is assigned to class 'CX_RSR_PROPAGATE_X', was not caught
     and
therefore caused a runtime error.
    The reason for the exception is:
    An error occurred when getting data from the processor.
The occurrence of the exception is closely related to the occurrence of
    a previous exception "CX_RRHI_INCLTAB_LOCKED", which was raised in the program
     "CL_RRHI_INCL_CREATOR==========CP",
    specifically in line 33 of the (include) program
     "CL_RRHI_INCL_CREATOR==========CM00W".
    The cause of the exception was:
An exception has occurred
Plz advice.
Regards,
Shree.

Hi,
Refer to the Note:
Note 1130023 - Temp hierarchy join:CX_RSR_PROPAGATE_X, CL_RRHI_INCL_CREATOR
Symptom
You select the indicator "Temporal hierarchy join" for an InfoObject. You try to activate the InfoObject. This may result in the termination: UNCAUGHT_EXCEPTION, CX_RSR_PROPAGATE_X. The termination occurs at position: CL_RRHI_INCL_CREATOR, SAVEHIER. The main program is: RSDG_IOBJ_ACTIVATE.
Alternatively, the system may issue an error message during activation, which indicates a conflict with the maximum name length that is allowed.
Other terms
CL_RRHI_INCL_CREATOR, CX_RSR_PROPAGATE_X, temporal hierarchy join, rsd1, InfoObject
Reason and Prerequisites
This problem is caused by a program error.
Solution
SAP NetWeaver 7.1 BI
           Import Support Package 05 for SAP NetWeaver 7.1 BI (BI Patch 06 or SAPKW71006) into your BI system. The Support Package is available when Note 1126007 "SAPBINews BI 7.1 Support Package 6", which describes this Support Package in more detail, is released for customers.
SAP NetWeaver 7.0 BI
           Import Support Package 17 for SAP NetWeaver 7.0 BI (BI Patch 17 or SAPKW70017) into your BI system. The Support Package is available when Note 1106569 "SAPBINews BI 7.0 Support Package 17", which describes this Support Package in more detail, is released for customers.
In urgent cases, you can implement the correction instructions as an advance correction.
You must first read Note 875986, which provides information about transaction SNOTE.
To provide information in advance, the notes mentioned above may already be available before the Support Package is released. In this case, the short text of the note still contains the words "Preliminary version".
Hope this hleps
regards
KP

Time dependent Hirarchy Structure

Hi,
I need to create Hirarchy, i did not create before,
Please some one explaine me how to create     Time dependent Hirarchy Structure in CostCenter InfoObject.
Please, please help me.
Thanks

HI
Find the below link
http://help.sap.com/saphelp_nw2004s/helpdata/EN/0e/fd4e3c97f6bb3ee10000000a114084/frameset.htm
Time-Dependent Hierarchies
Use
In a hierarchy that is not time dependent, the characteristic values are always the same.
If you want to create views of a hierarchy that are valid for a specific time period, you need to create the entire hierarchy as time dependent.
If you want to model relationships that change time-dependently, you need to create the hierarchy structure time-dependently.
Functions
In InfoObject maintenance, you can set whether and in which ways a hierarchy is time dependent. You can choose from the following:
·         whether the hierarchy is not time dependent (Hierarchy Not Time-Dependent). This is set by default.
·         whether the entire hierarchy is time dependent (Entire Hierarchy Time-Dependent).
·         whether individual node relationships are time dependent (Hierarchy Structure Time-Dependent)
·         whether a temporal hierarchy join is used with time-dependent hierarchy structures (Use Temporal Hierarchy Join)
Entire Hierarchy is Time-Dependent
You can either load time-dependent hierarchies (see Loading Time-Dependent Hierarchies) or create them in the BI system (see Creating a Hierarchy). When you create a time-dependent hierarchy, you have to enter a validity interval (valid to and valid from fields).
If an entire hierarchy is time dependent, the system creates hierarchy versions that are valid for separate intervals. The system automatically uses the current valid version in this case. The hierarchy valid in each case can be uniquely identified by its technical name and the From-To Date.
In the InfoObject tree of the Data Warehousing Workbench, all time-dependent hierarchies under the associated InfoObject are displayed with the corresponding To Date, for example Time-Dependent Hierarchy 05/31/2000.
In reporting, the system returns the valid hierarchy when a query is executed using the query key date.
Within a restructuring company areas, you can create time-dependent versions of a hierarchy for the Main Area InfoObject. This enables you to compare the restructuring over different time periods in a query.
Time-dependent hierarchy 01/01/1999 - 05/31/1999
Time-Dependent Hierarchy 06/01/1999 - 12/31/1999
Main Area NORTH
Main Area NORTH
Area 1
Area 2
Area 2
Main Area SOUTH
Main Area SOUTH
Area 1
Area 3
Area 3
Area 4
Area 4
In reporting, you can work in the individual columns of the report structure with fixed date values. You may want to do this to compare Main Area North in the Time-Dependent Hierarchy 05/31/2000 with Main Area North in the Time-Dependent Hierarchy 06/01/2000 (simulation).
Time-Dependent Hierarchy Structures
You can either load time-dependent hierarchies (see Loading Time-Dependent Hierarchies) or create them in the BI system (see Creating a Hierarchy).
In hierarchy maintenance, you can determine a valid time interval for each hierarchy node (Valid to and Valid from fields).
In reporting, a hierarchy with time-dependent hierarchy structures is created either for the current key date or for the key date defined for the query. In addition, you can evaluate a hierarchy historically using the temporal hierarchy join.
You can assign an employee to different cost centers at different times within the context of a restructuring.
In the context menu of a hierarchy, choose Display Hierarchy to access the hierarchy display: Each node and leaf has been given a date symbol. Hierarchy nodes that are assigned to different places in the hierarchy structure, depending on the time, are displayed more than once. By double clicking on a hierarchy node, you can display the associated validity period for the node relation.
In the following example, you can double click on the Jones leaf to see that the worker Jones was assigned to region USA between 01/01/1999 and 05/31/1999 and Puerto Rico from 06/01/1999 to 12/31/1999.
In order to use a hierarchy with a time-dependent hierarchy structure in reporting, you require the following settings in the BEx Query Designer:
                            a.      If you want to evaluate a hierarchy with a time-dependent hierarchy structure for a fixed key date, enter the key date in query definition.
                            b.      If you want to evaluate a hierarchy with a time-dependent hierarchy structure historically, for a key date that is to be derived from the data, choose the temporal hierarchy join option and specify the derivation type for the key date.
For a more detailed description of the functions and differences between the two evaluation views, see Time-Dependent Hierarchy Structures in the Query.
In maintenance of the key date derivation type (RSTHJTMAINT) determine the rule you want to use to determine the key date from the data. In this way you determine the time characteristic and way in which the key date is to be derived.
       1.      First determine the time characteristic.
If you choose a Basic Time Characteristic as a time characteristic (for example, 0CALDAY, 0CALMONTH, 0FISCPER), you can use a key date derivation type of this kind for all InfoProviders that contain exactly one time characteristic that references the selected basic time characteristic. If there are several time characteristics in an InfoProvider that reference the basic time characteristic, you have to either determine the time characteristic more specifically or select a particular time characteristic from a particular InfoSet (Time Characteristic from InfoSet).
       2.      Determine how you want the key date to be derived from the time characteristic.
The following derivation types are available:
¡        First day of the period
¡        Last day of the period
¡        Delay by number of days (you specify this in the Delay by Days field). In this case, the key date is calculated from the first day in the period plus the number of days specified minus 1. If the key date does not fall within the period, the last day of the period is used.
Key date derivation type with (basic characteristic = 0CALMONTH, derivation type = u201Cfirst day of periodu201C):
·         For January 2005 the key date is calculated as 1/1/2005.
·         For February 2005 the key date is calculated as 2/1/2005.
Key date derivation with (basic characteristic = 0FISCPER, derivation type = u201Cdelay by number of daysu201C and u201Ddelay u201C = 29):
·         For K4/01.2005 the key date is calculated as 1/29/2005.
·         For K4/02.2005 the key date is calculated as 2/28/2005.
·         For K4/03.2005 the key date is calculated as 3/29/2005.
Note that the way in which you determine the key date derivation type affects performance. The number of data records that the OLAP processor reads corresponds to the level of detail on which the time characteristic and the leaf level lie. For this reason, choose the time characteristic as approximately as possible in order to keep the hierarchy small.
A small hierarchy has 100 leaves. For a period of 12 months, the OLAP Processor reads 1200 data records at month level. At day level, it reads 36500 data records.
Regards,
kumar reddy.k
Edited by: kumar reddy on Nov 18, 2008 10:50 AM

Parent Child Hierarchy Issue in OBIEE 11g

Hi All,
I am in OBIEE 11G v6. I have a sales fact table where the grain is one sale. So I have one row for every sale done.
Now I have a ragged employee hierarchy like this with David at the root node.
David >>Richard>>Sean
David >>James
Also, I have a role dimension which gives me what role each employee has performed on a sale. Only one employee can be associated with one sale. This is the way Roles have been asssigned
David = Manager
Richard = Off1
Sean = Off2
James = Off2
Both Sean and James can have same Roles. Now I have created a parent child hierarchy for my employee dimension and the closure table. Defined the member key, ancestor key relationship in the parent child setting etc.
Now in the report when I pull the parent child hierarchy and the sales_amount in the report, it comes out perfect with all the ragged hierarchy resolved. But the issue comes when I try to limit the report on Role = Off2. It gives me an error saying " The layout of this view combined with the data, selection , drills resulted in no data. Undo drill and view prompt values". Basically what i want is to be able to select any role type and then my hierarchy should be adjusted to show me that data. Like when I select Off2, I want to see David at the Top level and Sean and James under him because they are both Off 2 and David is their manager.
Is that possbile? Also, am I getting this error because when I select Off2 though it gets Sean and James but since David is not Off2, I don't get the data?
I hope I was able to explain the issue, any help on this would be greatly appreciated.
Thanks
Ronny

So basically this means that if I build a parent child hierarchy on table A having the stucture like
--David (Manager)
-----James (Off1)
--------Bill (Off2)
and in my sales fact table for let's say today, I have only rows for Bill (Off2) because he is the only officer who did the sales today. Now when I will join my fact table to parent child hierarchy table A I will NOT get any data ? because there is no James who is the parent of Bill. So obiee need to have parent pulled off in the data (ANCESTOR) to be able to roll up the child.(IS_LEAF = 1)
I testes this and if my data only contains only rows for Bill (or I limit on ROLE = Off2) then it won't show the hierarchy. The query which OBIEE fires is to look for either ANCESTOR_KEY = NULL OR (DISTANCE = 1 AND ANCESTOR KEY IN (Bill). Therefore it doesn't I am wondering then what is the use of builiding the parent child hierarchy when we need to pull in all the ancestors (like in this case James for bill and David for james) because in real scenarios there can be cases wherein we would want to filter the data based on other dimensions to which the parent child hierarchy joins ?

Parent Child Hierarchy in OBIEE 11G

Hi All,
I am working on the parent child hierarchy in OBIEE 11g Source ESSBASE ..followed some of the blogs.
http://www.rittmanmead.com/2010/07/obiee-11gr1-enhancements-to-essbase-support/
I followed the following steps.
1.Imported the Cubes from ESSBASE.
2.Selected Accounts Hirearchy and changed the Hierarchy type to Value.
3.Dragged the subject area to BMM and to Presentation.
4.Now when i checked the Account Hierarchy from in the dashboard its not drilling down.
If i change the Hierarchy type to Unbalanced ...then the Account hiearchy is working fine.
Is there is any settings or process i have to follow..inorder to implement the Value based Hierarchy in OBIEE 11G source ESSBASE.
Thanks

So basically this means that if I build a parent child hierarchy on table A having the stucture like
--David (Manager)
-----James (Off1)
--------Bill (Off2)
and in my sales fact table for let's say today, I have only rows for Bill (Off2) because he is the only officer who did the sales today. Now when I will join my fact table to parent child hierarchy table A I will NOT get any data ? because there is no James who is the parent of Bill. So obiee need to have parent pulled off in the data (ANCESTOR) to be able to roll up the child.(IS_LEAF = 1)
I testes this and if my data only contains only rows for Bill (or I limit on ROLE = Off2) then it won't show the hierarchy. The query which OBIEE fires is to look for either ANCESTOR_KEY = NULL OR (DISTANCE = 1 AND ANCESTOR KEY IN (Bill). Therefore it doesn't I am wondering then what is the use of builiding the parent child hierarchy when we need to pull in all the ancestors (like in this case James for bill and David for james) because in real scenarios there can be cases wherein we would want to filter the data based on other dimensions to which the parent child hierarchy joins ?

BI deployment from OWB 10.2 (Paris)

Hi all,
I'm curious what success or lack thereof you have had in deploying dimensions and cubes relationally to Discoverer with OWB 10.2.
Do you deploy item folders for dimensions and cubes seperately?
Do you create item folders for every level of your dimensions?
Do you create "complex" item folders instead having the dimensions and cubes prejoined?
I'm working on our BI deployment and would love to know some of your experiences with either method. Also, are you able to fully manage your EULs with OWB or do you have to use Discoverer Administrator post-deployment?
Thanks in Advance,
Mike

Hi Mike.
Do you create item folders for every level of your dimensions?You must create item folders for all information you want to show to end-euser or you need to add to a calculation, hierarchy, join, etc. It depends on how you have imported the folder in discoverer. Make sure the item you want to add to a folder is not already there.
Do you create "complex" item folders instead having the dimensions and cubes prejoined?Read the best practices document/thread. You'll see that using db views might be an alternative.
I never tried this using OWB 10g R2. In previous releases you'd have to create collections, export/import it to discoverer and that was the most you could do using OWB.
As far as I've read the documentation, the "Defining Business Intelligence Objects" chapter in OWB users guide, it seems like there's a lot stuff you can do in OWB.
However you'll see the need to edit the Business Areas using Discoverer Adm Edition. Read this thread, you'll see there's plenty of stuff you won't be able to do using OWB (like editing security/privileges, for instance):
Discoverer Adm. Best Practices
Also, read the following document:
http://www.oracle.com/technology/products/discoverer/pdf/Discoverer_10_1_2_BestPractices.pdf
You'll find answers for most of your questions.
Regards,
Marcos

SAPKW70016 bugs with reference characteristics and attributes

Hi, experts!
I have very big problem.
When we've imported SAP BW SP 16 somthing went wrong as of reference characteristic and attributes.
1) If InfoSet contains reference characteristic, it can't be activated. (Error message RSO404)
2) If transformation rule is "read master data" and source characteristic contain compounded characteristic wiht same attribute as target field, and componded characteristic is above lexicographical then source characteristic. When you save this transformation this source field is removed from transformation rules? transformation can't be activated!!!
3) When you use in compounded characteristics which are reference characteristic and you want to use this source characteristic in rule "read master data" you'll get dump.
Now about reason and trials to resolve this problems.
2) The reason is incorrect sorting and reading internal tables with characters in source fields in transformation with attribute target field. Problem is resolved with using rule "ABAP", FM "RSAU_READ_MASTER_DATA".
3) and 1) The reason is program look for name REFERENCE character in table in field BASE characteristics names. Problem was resolved only fo happen 3) with disable "better" functionality "lookup_master_data" (note 1092539).
Problem 1) is still open...
What can I do?
Thanks for all replies!
P.S. Notes 1116379, 1112742, 1125321 have been implemented.
Best regards,
Antoshkin Vitaly.

Hi, did you try to implement this following notes ?
1158243     InfoSet in MultiProvider: Error message R7I 135
1157410     InfoObject as InfoProvider: Follow-on note for Note 1063194
1152136     Error during master data reading (ERROR_IN_MD_BUFFERING)
1147263     Temporal hier. join characteristic, compounding, attributes
1119777     THJ characteristic for referenced characteristic is missing
1118497     Incorrect where-used list for referencing characteristics
It´s have important corrections for SAPKW70016 version.
I hope that this notes can be helpful.
Best regards,
Walter Oliveira.

Temporal Hierarchy Join

Similar Messages

Maybe you are looking for