Validity period merging issue for time dependent master data

Hello All,
I am trying to load the data from DSO ZDSO1 to Master data object ZCASE1. Attribute "ZATR1" of ZCASE1 is the time dependent attribute of ZCASE1.
ZDSO1 contains "Changed On" field which defines the "Valid From" period for attribute "ZATR1" of case ZCASE1.
For eg.
ZDSO1 contains below records for Case 'C1':
Case ID     Changed On ZATR1
C1              01.01.2014     01
C1              02.01.2014     01
C1              02.15.2014     07
C1              02.17.2014     07
My transformation from ZDSO1 to infoobject ZCASE1 contains below mapping:
Case ID - Direct Mapping - ZCASE1 object
Constant value '12/31/'9999' - VALID TO field
Changed on - Direct Mapping - DATE FROM field
ZATR1 - Direct Mappint - ZATR1 object
After loading the data from ZDSO1 to ZCASE1 below results are obtained:
Case ID     VALID FROM VALID TO   ZATR1
C1             01.01.1000    12.31.2013 BLANK
C1             01.01.2014    01.31.2014 01
C1             02.01.2014    02.14.2014 01
C1             02.15.2014    12.31.9999 07
Time-Dependency is define correctly however my concern is why second and third records were not merged together. Instead of having four records, I should have ideally received THREE records. As shown above, third and fourth record (value 07) from ZDSO1 are merged into SINGLE record in infoobject ZCASE1.
For the subsequent data, it again does the same thing.
For eg. If I receive below Delta record from ZDSO1:
C1   03.01.2014 07
I get FIVE records in infoobject ZATR1 as shown below:
Case ID     VALID FROM VALID TO   ZATR1
C1             01.01.1000    12.31.2013 BLANK
C1             01.01.2014    01.31.2014 01
C1             02.01.2014    02.14.2014 01
C1             02.15.2014    02.28.2014 07
C1             03.01.2014    12.31.9999 07
In my understanding, BW system should have merged this Delta record with the last record present in infoobject because both the records have same ZATR1 value.
I would really appreciate your help/suggestions to understand/resolve this issue.
Thank You,
Nilima

Hey Arun,
While there wasn't any other time-dependent attribute apart from ZATR1, there is another time-independent attribute ZATR2 of ZCASE1 whose value was changed and hence somehow system was not able to merge the validity range.
Thank You.
Nilima

Similar Messages

0CALDAY for time dependent master data lookup unknown when migrated to 7.0

I am in the process of migrating a number of InfoProviders from the 3.x Business Content to the new methodology for BI 2004s.
When I try to create a transformation from the Update Rules for 0PA_C01, all of the rules that use a master data lookup into 0EMPLOYEE give me the error such as "Rule 41 (target field: 0PERSON group: Standard Group): Time char. 0CALDAY in rule unknown".
How do I fix the transformation rule that is generated from the update rule for these time-dependent master data attributes?

Hi Mark,
look at http://www.service.sap.com/. I guess you need to implement some corrections or newer supp-packages.
kind regards
Siggi
PS: take a look: https://websmp104.sap-ag.de/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=941525&_NLANG=EN
Message was edited by:
Siegfried Szameitat

Combining records for time dependent master data

Good Day,
We have a characteristic with turned on time dependency for master data.
Bringing in data from the source generated a number of entries for the master data.
Here is an example:
Line 1: [Date 1] - [Date 2]
Line 2: [Date 2] - [Date 3]
Line n: [Date x] - [Date y]
Any thoughts on how we can converge/aggregate Line 1 through Line n for the history, so that we have
Line 1: [Date 1] - [Date y]...
and then, going forward we can, use time dependency for any changes to master data that might come up.
Thank You for your input,
Dmitriy

Hi Dmitriy,
As far as I know, it is not possible, unless you delete the master data and reload.
I don't think you will be able to delete the master data at this stage, because it will not possible to delete the master data without deleting the transaction data.
Thanks,
Krishnan

Bex Report for time dependent master data

Hi Gurus,
I hav created a report based on a mutliprovider having 1 DSO and 2 CUBEs with has a common characteristics 0SALEEMPLY which is timedependent master data
it has following records
Validfrom===== To======== SE == Division
05.05.2006 ===14.10.2007 == 709== 32
15.10.2007 ===19.10.2007 == 709== 33
20.10.2007 === 31.12.9999 ==709 ==34
In report wen i fetch the data month wise it shud show the division(time dependent) according to its validity in master data
But in my report it shows division 34 in all the months
what is wrong here and do i need to hav any restriction at query level ?

Hello Experts,
please update

What is time dependent master data?

Can anybody explain me in detail with an example for time dependent master data?
Thanks in advance.
Sharat.

hi,
the master data value changes with respect to some time characteristics.
say- Salesregion is a char that have sales rep as master data(attribute)
saleregion date from date to              sales rep
sr001        20/10/2007 20/12/2007          Ram
sr002        21/12/2007 12/05/2008          Ram
in the above example Ram is in two sales region in different dates.
these type of attributes were time dependent.
usually time period will be defined in the data range of 01/01/1000 to 31/12/9999.
Ramesh

Data not uploading in Time dependent Master data Infoobject

Hello All,
I have a master data infoobject for HR entity and have to load data from PSA to that info object.
The HR entity infoobject already have sone data like below:
HR Entity
Version
Date from
Date To
x
A
01.07.2013
31.12.9999
x
A
19.04.2013
30.06.2013
x
A
01.09.2012
18.04.2013
x
A
01.01.2012
31.08.2012
x
A
01.01.1000
31.12.2011
Now the data in PSA is as follows:
HR Entity
Start Date
End Date
X
01.01.2012
18.12.2013
Once I loaded this data to the infoobject, i can not see this value which is the latest value of this HR entity.
Can somebody please explain how the data gets loaded in the time dependent master data infoobject and why this entry is not getting loaded in the info object.
Regards
RK

Hi,
did you activate master data after your load?
You can check also version 'M' records and see if your record is there.
The load went green?
The problem is, that your entry overlaps all exisitng time intervals, which can't be deleted or merged as there may be dependent transactional data. You have first to delete the transactional data for this entity.
Then you can delete the time-dependent data and reoload it from your PSA.
BW will build then correct time intervals.
The easiest is to change the time interval in PSA, see example below:
At the moment the time interval is not accepted. But you can add time intervalls before 31.12.2011 and after 01.07.2013, Then system will create remaiing time intervals, e.g. your new record is:
HR Entity
Start Date
End Date
X
01.08.2013
18.12.2013
Result will be:
HR Entity
Version
Date from
Date To
x
A
19.12.2013
31.12.9999
x
A
01.08.2013
18.12.2013
x
A
01.07.2013
31.07.2013
Regards, Jürgen

Changing time dependent master data records

Hello All,
I have a time dependent master data infoobject that has 39 million entries.
Now we decided that we no longer need it time dependent.
Hence we want to maintain constant value ( 01.01.1000 to 31.12.9999) going forward.(as changing the object's time dependency will have huge impact)
But for the historical data, we want to fix this and maintain only one record per value which will be the last record.
Can you please provide inputs on how this can be achieved as i tried various combinations of load( load to a copy object taking only last record, changing its valid to to 01.01.1000 and loading back) and its not working.
e.g the value XXX has following entries currently:
Object
Valid To
Valid From
XXX
15.06.2007
01.01.1000
XXX
19.09.2007
16.06.2007
XXX
28.01.2008
20.09.2007
XXX
30.03.2009
29.01.2008
XXX
31.03.2009
31.03.2009
XXX
15.04.2009
01.04.2009
XXX
31.12.9999
16.04.2009
we need to get to the below format:
Object
Valid To
Valid From
XXX
31.12.9999
01.01.1000

Hi Dhanya,
The approach u did (load to a copy object taking only last record, changing its valid to to 01.01.1000 and loading back) will not work on Master data because it is not a DSO, with the Proper keys in place, to overwrite all the previously existing data records. This approach will only work if the infoobject is not time dependent and in that case the question u posed will not arise at all .
SOLUTION:
One thing is Inevitable as Prashanth has prescribed, u have to delete the transaction data first at all the places, where and all it was used.
Then just delete the entire master data from the info object and just do a FULL DTP load from the underlying datasource putting a FILTER like "VALID_TO = 31.12.9999" so that only the last record of a particular Value will be loaded. (No need to do a full load from the source because even in the source it might had been the same old Values and might not have been revamped.)
Even for further delta's, it will be safer to maintain this filter at the DTP level if u r not sure of the constant value maintenance at the source.
Thanks & Regards
Sasidhar

Composite Provider with Time dependent master data

Hi ,
we have a infoset and due to some performance issues we are creating a composite provider to replace Info set and that Info set is having Time dependent master data objects and DSO.. But when I was creating composite provider I do not see two time dependent objects (Valid from and Valid to ) in composite provider. Composite provider does not have them/ is it a limitation? Appreciate if provide a input on this.. [We are in BW on HANA 7.4 with SP 7 environment]

Hi Manohar Karunakaram
I remember that there was the following limitation with Composite provider in terms of time dependent masterdata but it was a little old limitation.(some time in 2013)
If temporal joins are required where the result set is depending on time-dependent master data, InfoSets have to be used since CompositeProviders can't provide that functionality.
I am not sure whether it was solved in the latest release and dont remember an OSS where this was addressed.
BR
Prabhith

How InfoSpoke reads time dependent master data ?

Hello Experts !!
How InfoSpoke reads the time dependent master data ?
What key date it reffers to ?
Can you please explain, I want to use this concept in writing master data lookup for time dependent attributes of 0MATERIAL.
Thank a lot !

You can either specify the time period in the filtering area of infospoke or you can implement a transformation BAdI -OPENHUB_TRANSFORM to manipulate the data whichever way that suites your requirement. All time dependent infobjects have datefrom and dateto fields which you can use to choose your data range accordingly.
Hope this helped you.

Problem with Time dependent master data

Dear All,
I have 0PERSON master data infoobject. It is getting records extracted from backend R3 and from a different datasource called 'Peoplesoft'. It has a field 'Date of Birth'. Point of concern here is - whether a particular employee is present in Peoplesoft or in R3, his date of birth is constant. Unfortunately someone hs made 'Date of Birth' as a time dependent attribute of the InfoObject 0PERSON.
We extract data from Peoplesoft from 01.01.1900 to 31.07.2005. From 01.08.2005 onwards, data is getting extracted from R3.There are some employees which are present in Peoplesoft but they are not in R3.
Problem is occuring when the user is reporting on a relevant Infocube containing this 0PERSON infoobject. He does not see the value for this 'Date of Birth' field for certain employees. The reason for this is that the 'Date of Birth' field is blank in the interval 01.08.2005 - 31.12.9999 as this employee was absent in R3 and hence no record/s got extracted.
To view this value in the report - Please suggest me a possible remedy. I thought to write a routine but I dont think it is advisable to change a time dependent master data.
Thanks,
Srinivas

Hi,
There are two ways of solving your issue.
- Remove the time dependent check box for 0person, delete the transactional data, load the master data again and reload the transactional data.
- Write a program to extend the 'Date to' value to 31.12.9999 for all employees.
Ravi

Reorganization of time dependent master data

I am using reorganization of time dependent master data and it does not merge overlapped period as suggested by SAP. Any suggestions please.
http://help.sap.com/saphelp_nw04s/helpdata/en/c7/b05e3cc3a1a62ce10000000a114084/frameset.htm
Best Regards
Vikash

Hi,
you have used the processvariante "reorganization of time dependent master data" in a process chain and it doesn't work?
I don't think so.
1. it works perfekt. so, you can reduce the data in the master data table.
2. you don't have overlapping periods - you have one-after-another time intervals.
=> Please check the attributs again. I think there is a change in one attribut.
Sven

Time-dependent master data in the cube and query

Hello,
I have a time-dep. masterdata infoobject with two time-dep attributes (one of them is KF). If i add this infoobject into the cube, what time period SID will be considered during the load? I assume it only matters during load, if i add the KF to the query it gets its value based on the SID in the cube.. right?
Thanks,
vamsi.

If its Time Dependent Master Data object when you run your Master Data if that time any changes to the Master Data that value will be overwrite to the old value you will get the new value. When you run the Query execution the Infocube Master Data infoobject will having the SID that time it will to there it will be displayed at that moved what is the value you have in the Master Data table.
This is what my experience.
Thanks,
Rajendra.A

Modify code to pull the time dependent master data

I fully under stand the suggestion below for the requirement to add the time dependent attribute comp code
thanks fo rthe help but please tell me if there is a way i can modify the abap code and make the user enter the value for the date on which he want to pull th emaster data for company code or keydate to and from and pull the master data, so how will i proceede should i create the variable on 0doc_date and how to modify the code. please help . i have opened another question with same desc as above to assign points
thanks
soniya
The literal within <..> is supposed to be replaced by the actual field name (as I didn't know the fields). In this case, I am changing your code for costcenter/company-code.
data : wa like /bi0/qcostcenter.
select single * from /bi0/qcostcenter into wa
where costcenter = comm_structure-costcenter
and objvers = 'A'
and datefrom le comm_structure-<keydatefield>
and dateto ge comm_structure-<keydatefield>.
if sy-subrc = 0.
result = wa-comp_code.
endif.
abort = 0.
You can use this code for update rule of company_code. You have to replace '<keydatefield>' with a field name that contains the date on which the company is to be derived. If there is a date in your comm_structure (eg aedat) which you can use, you can specify that field in place of this literal (instead of comm_structure-<keydatefld> use comm_structure-aedat). If you have no such field, and you wish to use current date for getting the company code from time-dependent master data, you can use sy-datum (ie replace comm_strucutre-<keydatefld> with sy-datum).
And it should work.
The 'master data attribute' option is one of the options when you create update rule (one of the radio button options).

That the code is doing anyway.
If your txn data in the cube doesn't have a date, how does it know it is Feb data, or, it is March data?
If it has a date or month field, you should modify and use this code to update the company based on that date instead of system date.
Other than that minor variation, it is already doing what you look for.

Time Dependency Master Data Load

Hi:
This is my first time to work on time dependency master data. I need help!
I first deleted master data and cleaned up the PSA for material sales.
Then I have turned on the feature of time dependent on the info object for material sales. Save it and activated the object.
Then i have problems by loading the master sales attribute data in PSA. The error is: on every record of material, it has "invalid 'to' date '00/00/0000'" and "invalid 'from' data '00/00/0000'".
Is every process i did wrong? What is the process to work on time dependent master data? and loading the data?
Thank you!!

Hi,
After turning on the time dependence...you get an extra field in the key of the master data table Q table date to and a new field date from as a new field.
These two fields needs to be mapped to date to and date from R/3 source as well.
If there is no source field for these two then you need to make sure to get the values for these fields.
Just check if you are getting any field like that from R/3...right now i think you have left the mappings for these fields as blank.
Thanks
Ajeet

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

Validity period merging issue for time dependent master data

Similar Messages

Maybe you are looking for