Query on Time Dependent Info object

Hi ,
I am trying to create a query out of a time dependent info object.The info object is 0employee and since it is time dependent it has the date from and date to automatically in the infoobject master data. However these fields do not come up as characteristics when a create a query out of this infoobject.
Can you please let me know why or am I missing something ? I know I can get it if i use it in a cube or DSO but i want to create from this infoobject. Please help.
Thanks ,
Regards
Ashwin G

Hi
0employee_attr datasource have start and end date is mapped 1:1. target is 0employee? but when i check at 0employee attribute tab i have seen any start and end date attributes.
If you have it in attr u should be able to assign as read from master data.
Otherwise routine will be
SELECT STARTDATE from /BI0/MEMPLOYEE where employee = source_fields-employee.
for start date and
SELECT ENDDATE from /BI0/MEMPLOYEE where employee = source_fields-employee.
for enddate
Reagards,
Nagaraju.V

Similar Messages

Error in master data load in time dependent info object

hi,
while loading master data(Texts) to time dependent info object i am getting error like <b>"INFODEP1 : Data record 8 ('00000512 ') : Invalid "to" date '1-2-2004 '</b>
can anyone help where exactly is the error and how to remove it.
Thanks
Ashish

hi,
the date format should be yyyymmdd.
regards
pls assign points if helpful.

Time Dependent Info Object

Hi All,
I have an extractor that extracts data with DATEFROM and DATETO fo rthe time dependent HR employee related data for managers. But when it extracts into BI and loaded to Info Object the DATEFROM is not the same as what is extracted, it is 01/01/1000 instead of record specific.
Any idea why it is showing like it is?
Thanks,
Alex.

Beekay,
You are right. But in my case I extract only 200 records with DATEFROM and DATETO as 12/10/2006 - 12/31/9999. So I should expect my extracted 200 records and the system generated 200 records. But I have only 200 records but all the DATEFROM fields are changed with 01/01/1000. My PSA and R3 extractors are having the actual real DATEFROM.
Do you see where I have this issue?
Thanks,
Alex.

Extraction into Time dependent info object

Dear all,
In r/3 the field is time independent and want to extract the data into time dependent infoobject in bw.
what is the procedure to do it.
Regards,
BPNR.

Hi BPNR,
You have two options:
1. Make the info-object time independent and pull the data from R/3.
2. Hard code the Date to and Date from fields in the infopackage to extreme values say 01/01/1900 to 31/12/9999 and extract the data from R/3.
Hope this helps.

Which tables are hit when a query runs - time dependent objects performance

Hello all,
We are trying to see what are the effects of time dependent master data objects in query. We will have a key date as variable so user can see the data as a particular point.
I am trying to see what are all the tables hit when a query is executed and how the time dependent info objects affect performance. Basically we are trying to see is - does the query hit the P or Q or Y tables of the infoobject. Is there any tcode or program that I can use to see which tables were hit and how much time the query took to execute.
Also if the time dependent attribute is in free characteristic does it directly effect the query.
If you can share some more experience with time dependent master data objects in query and its effects on performance that will be great.
Thanks all in advance

Hello Siggi, Thanks for inputs
That is what I actually did before posting message here, the tables that are hit are /BI0/S...or /BI0/R and /BI0/T.... I never see the tables /BI0/P or /BI0/Q ... tables hit. I have a key date on variable screen at so when i put future or past date the /BI0/SDATE table is hit does it sound about right to you ?
Is the /S table hit the most because the data is being seen from the SID's that are generated.
Can you share your thoughts.
Thanks again,
Have assigned you points.

Help with a query regarding time dependent display of Plan/Actual data

Hello,
Let me try to explain what my problem is:
I have a query that shows plan and actual sales figures on a timeline. Plan and actual data is identified by 0VERSION (P01 for Plan; P00 for Actual).
0CALMONTH and Sales key figure is in rows. 0VERSION is in collums.
The output looks as follows (simplified):
CalYYYY/MM............P01....P00
2006.09......Sales........90.....100
2006.10......Sales......100.......95
2006.11......Sales........90........0
2006.12......Sales........95........0
So far so good! But users aren't satisfied with that. They want only <u>one</u> collumn with sales figures. For past months (< 2006.11) they want to see actual figures (Version P00). For current and future month (>= 2006.11) they want to see plan figures (Version P01). And this only in one single collumn.
So the output should look this way:
CalYYYY/MM..........P00/P01
2006.09......Sales......100
2006.10......Sales.... ...95
2006.11......Sales........90
2006.12......Sales........95
Is there any way/workaround to accomplish this?
Your help will be very appreciated!
Regards,
Ulrich

Hi,
For this what you can try is , have the two Restricted Key Figs the way you have right now, but Hide them. Then Create a Third Formula Key Fig, in which you can put a Boolean Logic :
(FV > 11) * Act KF +(FV<= 11)*Plan KF
Where FV is a Formula Variable which takes on the Value from Month (1 for Jan , 2 for Feb etc)
Try something on these lines.

Reporting on Time Dependent Master Date Info Provider

Dear All.
We have a info object Employee which is time dependent master data containing all the information with time dependency, when i create the query over this info object it give me the option to select the key date and it show the accurate information which is lying according to the key date.
my requirement is to show all the records in the report which are there in master data but i am not able to show more then one record cause of the key date, can you please let me know how can i show all the records for any given employee id in the query.

Hello Zeeshan,
By standard if you create query directly on time dependent info object, it would display the active records as of the report execution (if no key date has been provided). In any case you can only see one record per the info object key, not the history.
In order to fulfill this requirement, you may need to create infoset on this infoobject and select "date from" and "date to" as part of infoset fields.
Then create bex query on the infoset and drag the "date from" and "date to" also into "rows" section of the query (apart from infoobject key, time dependent attributes). This will let you see the history of changes to time-dependent attributes of the infoobject.
Cheers,
Vasu

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

Replacing DSO with InfoObject for storing time-dependent master data

Hi Gurus,
currently I am storing time-dependent contract items in a DSO. The posting items are enriched with this master data as well as some other transaction data into another consolidated DSO, which includes the time-dependency (valid from & valid to) as well for better performance. But this means that we will have a large number of records, because 1 new posting item could end up with few posting items more due to the versions of contract item.
Since there are many posting items (>50 millions yearly, daily peak 1-2 million) and the complexity with delta management, I am considering whether to use an InfoObject for storing the contract items. The number of contract items are not many, about 300,000 after migration and about 10,000 each month.
Hence, I would like to ask whether this approach is feasible? Is there a size limit for a master data InfoObject?
Thanks in advance.
Regards,
Meng

hi,
The Time dependent MD object will create the same number of records for the contract item (maybe more) as each contract item will have different record for different time frame.
this can be better explained with example.
let us say you have 1 contract item with 2 entries one valid from 2007-2008 and the other from 2008 onwards.
In DSO this will create 2 records, in time dependent MD object it would also create 2 records.
In the infopackage for the MD you would need to provide the interval (time range) for the MD.
if you provide it as 2007 till 2999 then two records will be created one with 2007-08 and other valid from 2008-999.
However as there would be other contract items which would have lower date say 2006 then this contract item would create 3 rows, 1 row for 2006-07 with blank values, 2nd for 2007-08 and 3rd for 2008-999. This way it has more number of records than the DSO.
In case of MD object you may not be able to delete data as well in future if the object is used in some other place.
There will be many pros and cons of the approach you are thinking and you would have to weigh them and decide.
regards,
Arvind.

Increasing the length of Char type Info-object ( impact )?

Hi,
We are on BW3.5 version and we have a custom defined Info-object ZP_REPORT(say )whose length is 3 now as all the three digit series will be used up in near future we have a requirement to increase the length of the characteristic.
This Info-object is used Navigation attribute of 0Material. And also this info-object is used as Navigational characteristic in few Info-cubes.
Can any one please let me know what would be the impact of increasing the length?
1)Do I need to delete the master data from this ZP_REPORT?
2)DO I need to delete the master data from 0MATERIAL?
3)Will there be any impact on Info-Cubes?
Thanks in advance.
Regards
Ajay

Hi Ajay,
It is always big challenge to change the existing info object lengh or type or anything that have gone live already..........
But if we will be very careful at the time of changing length and transport, we can do it succefully......
Lets come to your scenario... In my understanding
i) Your scenario is going to change the info object length that info object is only available for attribute. It is not at all used anywhere in the dimenstion table. So your cube will not be affected.... If problem will come your master data only will be affected.... Verify more than one time your info object is not at all used in any cubes. (Go to infoobject change mode check in where used list)
ii) Before changing the length in development, data should be available in development cube as well as master data.. Because you can verify it in development itself whether the data will be deleted or not at the time of changing the length and activate the info object.
iii) At the time of transport transport only the particular info object. Dont sent any other info objects. That might have related with any cube.
iv) For safety purpose check whether your info cube is having which type of load. Either Full load or Delta. Most of the cubes will be having delta. If it is full, then we dont have more worry on that.
v) Finally if possible, create one backup cube and back master data and load data from your existing cube to that cube. If the data will be more that 2 GB it is not a simple task to take a backup..... This is only for safty purpose......
Please let me know your status...............
Best Regards,
Vivek

Time Dependent Text

Hello, how do I set up my flat file to load time dependent text object. I encounter DTP errors when I tried the flat file with just customer key and text but not the date to and from information. is it necessary to have these fields to load? Thanks for your time. As you can tell I am just starting in SAP universe.
Suresh

Hi,
It depends upon the option which you have chosen.
In the master data/text tab in the infoobject if you have chosen short text check box then it will show short text only and mapped it to the source in tranformation.
The text for this inffobject is time dependent and values are determined by the validity periods range date to and date from.
For other infoobject you have chosen both the boxes and mapped them to the source fileds in transformation thats why it is showing both the text.
Thanks
Ajeet

Info object with time dependency

Hi Experts,
we have an info object (ZTEST) defined as time dependent with master data. ZTEST has several attributes (ATTR_1, ATTR_2).
Now I turned on one of the attribute (ATTR_1) to Navigation Attribute. The idea is to use this navigation attribute in the query, in order to avoid enhancement in the cube.
My question: could it be working? does it make sense? if yes, what should I pay attention to?
thanks for your feedback.
Sally

Hi
Of cause this will work fine.
After making infoobject available as navigational attribute, don`t forget that you have to choose
a validation date.
Therefore you can use a variable in query. (in query properties)
Otherwise, if there is no variabel, the actual date will always be choosen.
regards
Tom

Effect from build time dependent 2 attribute in info object master data

Dear all,
i creat time dependent 2 attributes in info object master data (ZCURRLUM) which use in info cube. after that i open workbook or query, it has short dump which error message
   "UNCAUGHT_EXCEPTION" "CX_RSR_X_MESSAGE"
   "CL_RSBOLAP_BICS_SERVICES======CP" or "CL_RSBOLAP_BICS_SERVICES======CM003"
   "HANDLE_UNCAUGHT_EXCEPTION"
Question: info object master data can't use more than a attribute time dependent???
i use in BI 7.0 level 14
thanks for your help
regards,
Joy

Hi Chandamita Sarmah,
I copy error code to you from line 1 to line 28
METHOD handle_uncaught_exception.
data:
    l_r_program_error TYPE REF TO cx_rsbolap_program_error.
data: lBExDebug type rs_bool.
GET PARAMETER ID 'BEXDEBUG' FIELD lBExDebug.
if lBExDebug = rs_c_true or CL_RSTT_TRACE=>GET_TRACEMODE_CURRENT_TRACE( ) = rstt0_c_tracem
Break-point for debugging, e.g. during running a trace
    break-point. "#EC NOBREAK
endif.
Subcall?
if P_RFC_CALL_DEPTH > 1.
Forward the exception
    subtract 1 from P_RFC_CALL_DEPTH.
    DATA: l_r_x TYPE REF TO cx_no_check.
    TRY.
       l_r_x ?= i_r_exception.
      CATCH cx_root.
        CLEAR l_r_x.
    ENDTRY.
    IF l_r_x IS INITIAL.
      RAISE EXCEPTION TYPE cx_rsr_propagate_x
        EXPORTING
          previous = i_r_exception.
    ELSE.
    RAISE EXCEPTION l_r_x.
    ENDIF.
endif.
All exceptions should have been caugth -> X-Message
Thanks a lot for your help
Joy

Change Info Object Master/Text data in PROD to Time dependant

Hello Experts,
I have an Info Object used in ODS and Cube. Both ODS and Cube has data in it. The Info Object has Text data.
I need to change Info Object Text data as Time dependant.
What are best way to make this change? If I make change to Info Object, how it's going to effect Cube and ODS.
Please advise.
Thanks
Padma
Padma Reddy

Bhanu,
Yes I am selectiong the check box to make IO as time dependant.
May be I am over complicationg this. Here is my understanding, correct me if I am wrong.
The IO is used in cube. It belongs to Dimension1. This dimension table is nothing but dim id's and SID's. So the Dimension table is built based on the exist SID values.
When I make change to IO, the data and SID's will change. Doesn't it cause some data inconsistancy ? And also the IO text table will have multiple rows with the same data but with different validity periods.
As I said I may be thinking too foolish or technical.
Please advise.
Thanks
Padma

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

Query on Time Dependent Info object

Similar Messages

Maybe you are looking for