just make sure if the text is maintained for it ie just chek if the text infoobject is loaded or not. In order to make sure first check if there is check mark in the infoobject for text if its there then add the required fields like short description long description and language key to the infosouce and in the infoobject there is an option of short text medium text and long text check them and make an update rule between the infosource and text infoobject and load it
Not really sure what you are calling as Junk Records.
If it is time dependent master data system will generate records ( extra record for say each cost center ) with <b>From</b> like 01011000 to <b>To date</b> a day before the Actual <b>From date</b> for the same say cost center in ECC.
Please give us a sample so we can better analyze .
There will always be a valid interval between 19000101 and 99991231 in BI .
It means if you load a record from r/3 with a validity of 20060101 to 99991231 you will find 2 records.
1st for 19000101 to 20051231 <b>without attributes</b> and a 2nd for 20060101 to 99991231 <b>with attributes</b>.
Now you change the validity range from 99991231 to 20061231 and load this changed record. In BW you will have 3 records now. 1st, as already described. 2nd for 20060101 to 20061231 with attributes and a 3rd with 20070101 to 99991231 with attributes too.
The only way to avoid this, is to enhance the extractor or the update rules and create a record for 20070101 to 99991231 <b>without attributes</b> in the datapackage.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.