Time Dependant MD (Characteristic ) repaired in RSRV

Guru's,
I have checked the characteristic info object in RSRV with All combined test -->
Master Data --> Check Master Data for a Characteristic and found red for the following steps.
 1.Time Intervals in Q table for a characterstic with time dependant master data.
 2. Compare characteristic values in SID/P/and Q tables for characteristic IO
 3. SID values in X and Y table: Characteristic 'Info Object'
Now my question
what will happend when above test found Red in RSRV?
Regards,
Venkat

1 . RSDMD_CHECKPRG_TIME_INTERVALS
2 . Compare characteristic values in SID/P/and Q tables for characteristic
Description:
    The system checks whether the same characteristic values exist in th
    master data tables S (SID), P (time-independent master data), and Q
    (time-dependent master data).
    It is checked more closely to see whether the following three quanti
    of characteristics are the same:
    o   Characteristic values that occur in the SID table of the examine
        characteristic in data records with the check flag (field CHCKFL
        'X'
    o   Characteristic values that occur in the P table of the
        characteristic in data records with the object version (field
        OBJVERS) = 'A'
    o   Characteristic values that occur in the Q table of the
        characteristic in data records with the object version (field
        OBJVERS) = 'A'
Repair:
    The repair mode does not lead to an automatic repair.

Similar Messages

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

How to Display Time-Dependent Characteristic Data In Query

Hi Experts,
   I have encountered a problem. I want to use Time-Dependent Chart. And want to display different value according characteristc's valid from time. For Example,
The Characteristic 0COSTCENTER has the navigation attribute 0COMPANY, The data as:
0COSTCENTER   Valid from   Valid To       0COMPANY
BW2305              20070101   20070430     A
BW2305              20070501   99991231     B
I want the report can display as :
0COSTCENTER   Valid from   Valid To       0COMPANY AMOUNT
BW2305              20070101   20070430     A                  1000
BW2305              20070501   99991231     B                  2000
But when I set the query's key date 20070420, the report display as:
0COSTCENTER   Valid from   Valid To       0COMPANY AMOUNT
BW2305              20070101   20070430     A                  1000
BW2305              20070501   99991231     A                  2000
when I set the query's key date 20070520, the report display as:
0COSTCENTER   Valid from   Valid To       0COMPANY AMOUNT
BW2305              20070101   20070430     B                 1000
BW2305              20070501   99991231     B                  2000
Can anybody tell me how I can get report expected.
Thanks in advance.
SF

Hi,
1) Add the characterstics 0COSTCENTER ,0DATETO,DATEFROM and 0COMPANY to the cube.
2) And also add these 4 IOs to the Communication structures which has update rules with the concern cube.
3) I hope , you already have 0COSTCENTER in the Commnication structure and mapping for that infoobject at both Update rules and Transfer rules.
4) Leave to the Blank(no mapping) mappings for the IOs 0DATETO,DATEFROM and 0COMPANY in the Transfer rules.But make 1:1 mapping in the Update rules for these 2 infoobjects.
5) Write the below code in the strt routine of the Update rules:
TYPES: BEGIN OF type4.
      include structure like /BI0/QCOSTCENTER.
TYPES END OF type4.
DATA:
ITAB4 TYPE STANDARD TABLE OF TYPE4
       WITH HEADER LINE
       WITH NON-UNIQUE DEFAULT KEY INITIAL SIZE 0.
SELECT * FROM /BI0/QCOSTCENTER INTO CORRESPONDING FIELDS
OF TABLE ITAB4
WHERE OBJVERS = 'A'.
loop at DATA_PACKAGE.
     READ TABLE ITAB4 WITH KEY COSTCENTER = DATA_PACKAGE-MATERIAL
DATETO LE DATA_PACKAGE-PSTNG_DATE
DATEFROM GE DATA_PACKAGE-PSTNG_DATE.
              IF SY-SUBRC EQ 0.
                DATA_PACKAGE-DATETO = ITAB4-DATETO.
                DATA_PACKAGE-DATEFROM = ITAB4-DATEFROM.
                DATA_PACKAGE-COMP_CODE = ITAB4-COMP_CODE.
              ENDIF.
              Modify DATA_PACKAGE.
endloop.
ABORT = 0.
Here I assumed you have Posting date in the Communication structure and used to map to Fiscalperiod of the cube.
6) Do the Master data upload to Cost center and active the master data of it always before uploading the data to cube.
7) Do the uploading to cube from Sratch.
With rgds,
Anil Kumar Sharma .P
Message was edited by:
        Anil Kumar Sharma

Display Time-Dependent Characteristic in 2different date columns (HR-data)

Hello.
I want to create a specific Query on a Self-defined HR-HeadCount cube. On this Cube I have Employee-number + characteristic values per month (e.g. PayScaleArea). Month is my most granular level.
The Query I want is the following :
     04.2006     05.2006
Employee/PayScaleArea
20184     5B     6
20230     3     4
20295     6A     6B
(5B, 6, ... are PayScaleArea's e.g. 5B is Manager)
I have already filtered on the Employees who got a promotion between 04.2006 and 05.2006 (=Month.Year). And now I whish to see the PayScaleArea listed of these Employees under 2 column headers April+May .
If this was a keyfigure this would be standard but for a characteristic I can't get it to work. I've already tried working with formulas (replacement path)
The problem is that it always displays like this :
              PayScaleArea
                  3     4    5B    6    6A    6B
Employee
20184
20230
20295
(which is realy bad)
Or
Employee/CalMonth/PayScaleArea
20184     04.2006 5B
20184     05.2006 6
20230     04.2006 3
20230     05.2006 4
20295     04.2006 6A
20295     05.2006 6B
(this is correct, but not verry readable, having it in 2 columns makes it easier to compare who promoted to what)
Note: I have PayScaleArea directly in the Cube and also as time-dependent attribute on Employee => the attribute has the problem that I can only report on one key-date per query (which is specified on the header of the query) so combining multiple queries in a workbook would also be a (less desired) workaround.
Can you help me ?
Kind Regards, Carl.

Hello,
I'm affraid you do not understand my question. You mention here one of the two 'workable' solutions (the other one being 2queries on different tabs each for a different month and then combining the 2queries on a third tab)
The report layout does not look good in this txt format so I will split it up using my original example:
The Query I want has three columns :
1) Employee
e.g. :
20184
20230
20295
2) The PayScaleArea's of Month -1 (e.g. : 04.2006)
e.g. :
5B
6
6A
3) The PayScaleArea's of current Month (e.g. : 05.2006)
e.g. :
6
4
6B
If PayScaleArea would be a keyfigure then I could just put Employee in my rows and month + PayScaleArea in the columns and it would work perfect... but it is a characteristic and therefore it does not show up next to the employee in this case.
In a sense this is logically since BW does not know that there is only one characteristic value PayScaleArea per month and per employee.

How to create a time dependent characteristic

Hi,
Can someone give me steps to create time dependent characteristic? there is a tab for attributes to make them time dependent. I don't know whether we can make the characteristic as time dependent or only the attribute.
Thanks,
Sam

What makes a IO a time dependent char?
The attribute values of the IO change according to the time. meaning atleast one attribute value has to(supposed to) change during the course. So to make a IO time dependent, atleast one of ur attribute values should be time dependent.
IO - change _ attributes - 4th column - time dependent - check that box. that would generate - MasDataTab. timDep - SIDTab timeDepAttr(tables)
simple saying in real time - cost center ABC's manager is XYZ from 06/19/2007 to 06/19/2008. So the manager (attribute of costcenter) has to be time dependent.
Hope that makes it understandable. In essence the costcenter itself never changes but the attribute values do change.

Characteristic 0PROFIT_CTR: Time-dependent Master Data Table '/BI0/QPROFIT_

Hello All,
I want to release a infoObject 0PROFIT_CTR to Prod. But after releasing the TR it errors with the following messages:
Characteristic 0PROFIT_CTR: Time-dependent Master Data Table '/BI0/QPROFIT_CTR' not buffered
Characteristic 0PROFIT_CTR: Time-dependent Text Table '/BI0/TPROFIT_CTR' not buffered
I went into these tables and also have set the buffering to ON and made them Fully buffered (Checked).
But even then it gives me same error.
Please help.
Regards,
KP

Hi Harika,
You are right, you will have to use SE14 in production system, just check that whether you have authorization to use it or not. If you don't have authorization then you can check with Basis team.
You can execute SE14, then give table name and in the lower part of the screen Click on the option Save and adjust, and activate the table. Once this step is done you can re-import your request.
Make sure that you do not delete data.
Regards,
Durgesh.

Time dependent characteristic

Hi,
In our query we have time dependent characteristic "Employee last name".
Our user wants to generate query on the employee list who was changed their last names. Here different employees has been changed their last name in different times.
Please specify in detail that how to define the query.
Regards
Sunil

if its a one time query then open the master data view in se16 and download employee / from date / to date / last name
download it to excel and analyze it.
If this is not a one time query.. then you have to build a way to save this in a ODS and make a query on it.
its not possible to go across time in a regular report as the key date takes only 1 date at a time.
Award points if you find it useful.
Thanks
Sharan

Bex query-KEY date for time dependent objects

Hi
I have one infoobject called 0customer that has one time dependent attribute .called status. I would know how the system works in the following senario for the a given key date(which in bex properties).
question 1)
customer todate          fromdate    status
1            20071231     20070101     Y
1            20081231     20080101      N
1            20091231     20081101      X
can the data in the infoobject be overlapped? is the 3 rd record is valid in the above example - as months(11&12of2008) overlapping with second record? ? pls advise
question 2)
customer todate          fromdate    status
1            20071231     20070101     Y
1            20081231     20080101      N
1            20091231     20090101      X
If the keydate is 20080201 which record will it return?would it return the record that has status 'N'?
what does the keydate is compared against? is it with from date or todate or between fromdate and todate? does the query return only one customer record for a given customer when it runs in the query?
Please advise.
Thanks
Vennela

1) Normally you cannot activate the data with this constellation. If you have inconsistent master data you can repair with transaction RSRV.
2) The system returns N for key data 20080201.
Best regards
Dirk
Edited by: Dirk Herzog on Nov 19, 2008 1:16 PM

0CS_Item with time-dependent hierarchy

Dear Experts,
we are discussing pros and cons for a time-dependent item catalog (characteristic 0CS_item with time dependent hierarchy in BW) within consolidation SEM BCS 4.0. Does anybody has experiences on this topic?
I am quite sure it will be a performance issue and it means additional reporting effort (e.g. using reference period/year in the report comparing different hierarchies).
I am not sure if there are any other risks so I it would be great if anybody has some hints.
Thanks in advance,
Birgit Laux
Message was edited by: Birgit Laux

Birgit,
Some other things to consider:
- frequency of changes to item hierarchy. Could lead to a lot of item hierarchies in BW over time.
- hierarchy validity date does not seem to be displayed when running web queries and thus makes it difficult for the user to select the correct hierarchy when executing the query. Still looking for a fix for this.
- greater complexity in overall design. Is it really necessary to achieve correct financial statement presentation?
Virtual cube performance is not great but you could implement the data mart which provides typical BW query performance.
I stayed away from setting the item as time dependent for these reasons.
Brian

Imposible to set a time dependency at a transformation

Hi!
I'm in trouble with a transformation (BW 7.0). I'm trying to fill a key figure reading master data from a characteristic. The key figure is an atribute of that characteristic, and it's time dependent. But when I define the rule in the transformation I cannot select any time characteristic to set the dependency.
Thanks!
Jose

Jose,
As far as I understand you are trying to use the "Read Master Data" option with Time dependency that was available in the Update Rules.
If that's correct, here are the steps:
Eg: Assume 1. 0REGION is a time dependent attribut of 0CUSTOMER.
2. Data Src fields: KUNNR, DATE
3. Cube: 0CUSTOMER, 0CALDAY, 0REGION
Your transformation should look like:
KUNNR=0CUSTOMER
DATE=0CALDAT
For 0REGION click to create the mapping:
Choose Rule Type = "Read Master Data"
In the "Source fields of Rule":
Add the fields KUNNR & DATE using the "+" button.
In the IO Assignment column, enter 0CUSTOMER & 0CALDAY and hit Enter.
Now in the "Source Info Object" field to the rt of Rule Type, select 0Customer using F4 help. Since it is time dependent on 0CUSTOMER, the clock icon will appear. Click on the clock button and select 0CALDAY from the F4 help.
It should work. Has worked for me (Data src to ICube directly)
For ODS use the export data source.
If it still doesn't work there are 2 more options:
1. Write a small routine/formula to read the values (as Ingrid had suggested). OR
2. Use it as a Nav Attribute (if the Attribute is a Characteristic) or as a Disp Attr (if the Attribute is a Key Fig). Then use the Key date of the query to calculate time dependency.
(By default key date = Syst date; if you need custom date, use variable exit)
That's all I can think of.
Hope it helps.
- Vishno.

Restricting time dependent records on employee master data in BW

Experts,
We have a Future hire report which gets data from 0Employee. Now whenever hire date of an employee is getting assigned in case of new hire record get's created in BW.
Now, due to some reason this new hire employee is not able to join on the hire date first assigned to him and new hire date is updated in PA30 for this employee in ECC.
This would create a new record in BW with new hire date for this employee which is valid in BW from the date it moved into BW till 9999 and the previous record 'Valid To' date is changed to previous date of the "Valid From" date of newly entered record.
Now all these records has moved into Multiple Cubes also therefore we cannot delete these records from Master data until transaction data is delete.
Client HR team is saying that previous records of all such employees are not valid , so they should not appear in BW reports even if they are running this report on historical dates.
0Employee is time dependent master data. So it makes sense to have one records for any actions done for an employee in HR system.
Cleaning up a master data for all such employee would be a tedious task and need lot of effort.
Is there any way , we can restrict previous records of all such employee , so that they do not appear in BW report in case users are going to run the report previous dates.

We were doing this activity as part of weekly house keeping job. Weekly we get list of invalid PERNR records from ECC team.
While deleting particular PERNR (say 10015824) from 0EMPLOYEE, and the log (SLG1)says, SID exists in DIM table (like /BIC/D0PA_C011).
First delete that PERNR (10015824) from cube (0PA_C01)
Use Tcode RSRV --> Tests in Transaction RSRV --> All Elementary Tests --> Transaction Data --> Entries Not Used in the dimension of an InfoCube (Dbl Click)
             From the right side window, expand “Entries Not Used in the Dimension of an InfoCube” Node &
             Enter InfoCube (like 0PA_C01), click “Transfer”
             Now, click “Execute” (Toolbar)… and the results displayed in the right side window..
             Now, click “Correct error” (Toolbar)
Now, try to delete same PERNR from 0EMPLOYEE, and if the log says SID used in some other DIM table, follow the above process.
If the log says, the SID used in DSO/Cube, then goto manage (of DSO/Cube) and do the selective deletion.

Changing to time-dependent hierarchie of 0CUSTOMER

Dear Experts,
I like to change 0CUSTOMER to "entire hierarchie is time-dependent" without losing any existing hierarchy or data. Is that somehow possible? I tried changing the Radio Button, but could not activate the InfoObject;
"The Hierarchy Table /BI0/HCUSTOMER must be converted incompatibly with an activation of characteristic 0CUSTOMER (changes to the key in the table). Table /BI0/HCUSTOMER contains data. Parts of this data were lost in the conversion."
I already checked the whole forum and the SAP help, but could not find a suitable note.
Can someone plase help?
Thank you very much in advance
Martina

Hello Amit,
Try reading the help documentation for such queries. e.g. Publishing Time-Dependent XML Documents - Knowledge Management - SAP Library
Regards,
Lorcan.

How to Select in a query considering key date of time-dependent characteris

Hi, Everybody
I have a Infoobject called CONTROL. It can be tested during the year once, twice, three times,six times or can be not Tested.
The Characteristic that contain the number of test that the Control will be tested is time dependent.
For example, one control can have the charcteristic to test twice in a year. Then 31/10/2007 it can turn "not test".
I can have these records:
CONTROL   VALID INIT       VALID END     TEST
   XYZ         01/01/2007       31/01/2007       TWICE
   XYZ         01/02/2007       28/02/2007       TWICE
   XYZ         01/03/2007       31/03/2007       TWICE
   XYZ         01/04/2007       31/10/2007       TWICE
   XYZ         01/11/2007       31/12/9999       NO TEST
I have a query that I should select the number of controls different of "NO TEST" During the time selected.
For example, if I select Interval Time = 01/01/2007 to 31/10/2007, This record should be Counted, because it was to be tested during this period.
If I have selected Interval time = 01/11/2007 to 31/12/2007, it should not be selected because in this period, this control doesn´t able to be tested.
If I put filter restricting NO TEST, the query should check the time of validity, but when I do that, BW doesn´t accept that because I can´t restrict by Validate Date.
Anybody already had a problem like that?
I´d like suggestions to solve that or comments that could explain that.
Thanks a lot,
Elisabeth
Edited by: Elisabeth Umebara on Feb 2, 2008 12:21 AM

Hi, everybody.
I already solved this problem. Thanks a lot.
For this I selected the controls in a exit variable that should be selected in from table time-dependent from infoobject. This solution ran just for BWD and BWQ, because there was a lot of data in BWP.
Then I made a first query that has selected the controls. After that, in the original query I defined the substitution path relating with the first query.
Thanks again,
Elisabeth

Additional Question on Time dependant hier

Hi Gurus,
Can anyone advice on the following
Must i use characteristic node for time dependent hierarchy structure or is text node allowed?
Thanks in advance

time dependency can be found in table EQUZ
you can check these notes
167331 0EQUIPMENT master data/texts tempor. overlapping
427214 0EQUIPMENT Time dependent Master Data Attributes
856580 0EQUIPMENT master data/text temporal overlap

Time dependent hierarchy structure in SEM-BPS

I want to use a time dependent hierarchy structure in sem BPS to make combination chek and proposal in a layout.
I have manage a relation of type hierarchy (based on this hierarchy) in the characteristic relationship tab page of my planning area.
I open my layout to make entries in the future (next fiscal year) but the system doesn't propose me the datas valide for the next fiscal year in my hierarchy but the datas validate today.
There is a key date in the master data tab page of the planning area but it seems to have only effects on attributes with validity dates but not with hierarchy with time dependent hierarchy structure.
Thanks for your help.

Hi,
The key data that you enter in the planning area is only for time dependent characteristics and attributes. For the hierarchies in the characteristic relationships the current data is used.
If you still want to use a time dependent hierarchy for modeling the characteristic relationships you could use a characteristic relationship type exit. In the exit you can read the hierarchy with the proper date.
Best regards,
Gerd Schoeffl
SAPNetWeaver RIG BI EMEA

Time Dependant MD (Characteristic ) repaired in RSRV

Similar Messages

Maybe you are looking for