Clean-up changelog in source DSO

Hello,
I was wondering if it is adviceable to clean-up change-log data in a standard DSO that is used as a source for another (target) InfoProvider.
The DTP that is used to fill the target InfoProvider uses the change-log to determine the delta between the source DSO and the target. I suppose I could delete requests in the changelog that are already loaded in the target.
However, if I need to delete the data from the target and reload it again, this data isn't available in the changelog anymore! In the old 3.x situation, I would do an init request (from the active table). This isn't possible anymore with DTP's.
Could anyone advice on how to handle these situations with DTP's?
Best regards,
Daniel

Hi,
You can clean the change log data for which the data is loaded for above data targets in BI 7.0.
If in case you need to do a full load for the above data targets, u can use the functionality of DTP as given bwllow.
First: Select Full update in DTP with "Extraction from" = active table.
Do a Full load from active table.
Second step:
For this option available in DTP is as shown bellow.
Select "Extraction" Tab.
Go to "Processing Mode"
Select 3 option: "NO data transfer and delta status in source Fetched"
This above step is (initilization without data transfer).which will help you to start the normal Deltas after full load.
Regards,
Srinivas.

Similar Messages

Missing field from source DSO in transformation to other DSO

Hi SDN,
I am facing the following problem:
I have created DSO "A" and a transformation rule to DSO "B". InfoObject 0RATE_TYPE is available in both DSOs... BUT: when I am creating the transformation rule the field from DSO "B" (on the right side) is not connected to any filed from source DSO "A" because there the field 0RATE_TYPE is not offered.
What I have tried so far:
- reactivate DSO "A"
- remove 0RATE_TYPE from DSO "A", activate DSO "A", include 0RATE_TYPE again, reactivate DSO "A"
- newly created DSO "A"
All this has not resulted in any other than the problem described before. One thing I recoginized: when doubleclicking on the DSO "A" I see the field 0RATE_TYPE, when doing a right click and selecting "Object overview" the field is also missing!
I have run out of ideas and I would like to see if any of you has had the same problem and has found any solution.
PLEASE help me!
Thank you in advance!!

Hi,
Did you try to logoff and logg on again?
(sometimes BI show things after leaving the transaction)
IS the DSO activated?
Is the field compounded to another field that is not in the DSO?
You might try a work around:
Make a routine that reads your DSO to get the field.
(If the ABAP-editor also gives an error on thing field something very strange is going on indeed)
Success,
Udo

Transformation : some fields are not visble in Source DSO

Hi
i have done mapping in transformation by connecting one Write Optimized DSO with a Standard DSo.
Both DSO have same fields. But i am seeing some of the fields are not visible in Write optimized DSO in Transformation
so those fields can not be mapped with corresponding Standard DSO fields.
let me know how those fields can be make visible in Transformation.
Regards
Atul

Hi ,
"Attribute Only" will not be visible , only method to to do this maybe something like below .
1) Look at the keys of the standard DSO , pick up the same combination and the attribute only fields from the source in the start routine of the TFM .
2) in the field level routine of the TFM (for the atrribute only fields ) , read the tables with keys and populate .
--Neha

Less source fields in transformation than in the source DSO

Hi,
I'm in a business content flow DSO 0GN_BP (consolidated BP) to fill master data attribut 0GN_VENDOR.
In the transformation source fields I only have a part of the fields in the DSO.
17 fields in DSO and only 10 in the source fields in the transformation.
<b>How can I get all the fields of the DSO as source fields in the transformation ?</b>
Regards,

I've log out log in, refresh the hierarchy etc. Nothing.
I hit the right DSO with the transformation.
The DSO is activated as well as the infoobject inside.
I've tried to reactivated it just to be sure ... but still missing fields in transformation.
I've also reactivate the DSO. Run RSRT on DTP, DSO ... all green.
I've check the structure tables of the DSO and they all got the right number of fields.
This is really weird. I'm going through a customer message.
Thanks for your help. I'll come back here if SAP found a solution.

Source Field in End Routine of DSO Transformation

Hi,
I made a transformation from source DSO to Target DSO.
There are 7 fields in source & 6 fields in target..All the 6 fields are one to one mapped from the source to Target
I need to write a simple ABAP Logic in End Routine based on the 7th source field which is not mapped.
Please let me know the piece of ABAP code or steps where i can get the value of Source table in End routine
Regards
Suresh

Hi Suresh,
Check here.........
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/e73bfc19-0e01-0010-23bc-ef0ad53f2fab
http://help.sap.com/saphelp_nw70/helpdata/en/e3/732c42be6fde2ce10000000a1550b0/frameset.htm
Regards,
Vijay.

DSO transformation problem

Hi ,
Can any one give me the some hints for the follwoing two problems..
1) I have one original DSO (NAME A) and created new DSO (NAME B) copy of the A. Both structures and fields are same.
While creating transformationsbetwen A and B, one field is missing from source DSO (A). but that field is available in DSO A and B. In transformations iam not able to see in souce DSO. Any suggessions..on this..?
2) DS in R/3 2LIS_!!_VAHDR having some fileds.all those fields are based on the table VBUK...
While extracting data or looking data in he table VBUK field AEDAT (Changed on) is empty... Even though i was created new sales document and chaned that sales document..
when it will be filled AEDAT filed in VBUK field..? which change is this..?
Thnaks
BK

Hi,
1) NO it is not 0recode mode... It is 0rate type. It is in DSO A .But in transformation it is missing to map with DSO B 0rate_type.(DSO B is copy of DSO A)
2) I did changes to the sales document(Changed the qty and saved) ,but even after that also it is empty.Same changes i can get it from other VBAP and AK tables .but i need from VBUK table AEDAT field. Is this field capturing those changes ..? or any other changes it will sve in aedat..?
Thanks
BK

Impact of Delta Records on Key Figure Summation in DSO

Hi experts,
I have a key figure with aggregation type "summation" in a DSO. I would like to know the impact of delta records on the key figure.
E.g.
source DSO
doc_id (key) | doc_pos | type | amount
4711 | 1 | A | 100 USD
4711 | 2 | B | 20 USD
target DSO
doc_id (key) | amount
4711 | 120 USD
If the first record is modified ("type" from A to C) as follows and delta-loaded to target DSO:
4711 | 1 | C | 100 USD
This will lead to incorrect amount:
target DSO
doc_id (key) | amount
4711 | 220 USD
How can I handle this situation?
Thanks in advance.
Regards,
Meng

Hi..
I believe one document number and document Item will have only one type.
Like 4711 1 should have only one type ( A / B / C).
If the above assumption is true then just remove Doc Type from Key field of source DSO.
Then From Source to Target Change Log table can handle this.
Regards
Anindya

New field added to cube, delta DTP from DSO to cube is failing

Dear all,
Scenerio in BI 7.0 is;
data source -delta IPs-> DSO -
delta DTP---> Cube.
Data load using proces chain daily.
We added new field to Cube --> transformation from DSO to cube is active, transport was successful.
Now, delta from DSO to cube is failing.
Error is: Dereferencing of the NULL reference,
Error while extracting from source <DSO name>
Inconsistent input parameter (parameter: Fieldname, value DATAPAKID)
my conclusion, system is unable to load delta due to new field. And it wants us to initialize it again ( am i right ?)
Do I have only one choice of deleting data from cube & perform init dtp again ? or any other way ?
Thanks in advance!
Regards,
Akshay Harshe

Hi Durgesh / Murli,
Thanks for quick response.
@ durgesh: we have mapped existing DSO field to a new field in cube. So yes in DTP I can see the field in filter. So I have to do re-init.
@ Murli: everything is active.
Actully there are further complications as the cube has many more sources, so wanted to avoid seletive deletion.
Regards,
Akshay

Data mart from two DSOs to one - Loosing values - Design issue

Dear BW experts,
I´m dealing with a design issue for which I would really appreciate any help and suggestions.
I will be as briefly as possible, and explain further based on the doubts , questions I received in order to make it easier go through this problem.
I have two standard DSOs (DSO #1 and #2) feeding a third DSO (DSO #3), also standard.
Each transformation DOES NOT include all fields, but only some of them.
One of the source DSO (let´s call it DSO #1) is uploaded with a datasource that allows reverse type of records (Record Mode = 'R'). Therefore some updates on DSO #1 comes with one entry with record mode 'R' and a 2nd entry with record mode = 'N' (new).
Both feeds are delta mode, and not the same entries are updated through each of them, but the entries that are updated can differ (means an specific entry (unique key values) could be update by one of the feeds, but no updates on the 2nd feed for that entry).
Issue we have: When a 'R' and 'N' entries happen in DSO #1 for any entry, that entry is also reversed and re created in the target DSO #3 (even being that not ALL fields are mapped in the transformation), and thefore we loose ALL the values that are exclusively updated through DSO #2, becoming blank.
I don´t know it we are missing something in our design, or how should we fix this issue we have.
Hope I was more or less clear with the description.
´d really appreciatted your feedback.
Thanks!!
Gustavo

Hi Gustavo
Two things I need to know.
1. Do you have any End Routine in your DSO? If yes, what is the setting under "Update behavior of End Routine Display"....Option available right side of Delete Button ater End Rouine.
2. Did you try with Full Load from DSO1 and DSO2 to DSO3? Do you face the same problem?
Regards
Anindya

Not getting data in cube from lookup DSO

Hi guys,
I have a transformation with source DSO and the target Cube. In which I have a look-up from another DSO to the cube in this transformation, end routine. But I am not getting the records I needed in the cube, which are supposed to flow from another DSO. Any ideas would be appreciated.
regards...

Hi,
When we do look-ups in end routine, we don't have active rules for the transformation.
By default transformation's "Update behaviour of end routine change" is set to
Only target fields with active rules
all target rules(independent of active rules)
So, we have to change to
All target rules (independent of active rules) in order to get the look-up data independent of active rules.
In old software, we used to make an infoobject constant,.
"Update behavior of end routine change " was not available.
check it once because it happened to me before.
Hope it works....

Issue in Data from DSO to DSO Target with different Key

Hello All,
I am having Issue in Data from DSO to DSO Target with different Key
Source DSO has Employee + Wage + Post numner as key and Target has Employee + Wage Type as key.
DSO semantic grouping works like Group By clause in sql, is my understanding right ?
Also if someone can explain this with a small example, it would be great.
Many Thanks
Krishna

Dear, as explained earlier your issue has nothing to do with semantic grouping .
Semantic grouping is only usefull when you have written a routine in the transformation for calculations and in error handling .
Please go through this blog which explains very clearly the use of semantic grouping .
http://scn.sap.com/community/data-warehousing/netweaver-bw/blog/2013/06/16/semantic-groups-in-dtp
Now coming to your above question
DSO 1
Employee WageTyp Amount
100          aa          200
200          aa          200
100          bb          400
100          cc          300
If we have semantic group as Employee . If we have Employee as key of the target DSO and update type as summation .
then target DSO will have
Emp                Amount
100                 700
200                 200
In this case Wage type will be the last record arriving from the data package . If the record 100 cc 300 is arrivng last then wage type will be cc .
2) Case 2
DSO 1
Employee WageTyp Amount
100          aa          200
200          aa          200
100          bb          400
100          aa          300
if we do Semantic grouping with Emp and Wage Type   If we have Employee and wage type as key of the target DSO and update type as summation .
then target DSO will have
Emp     Wage      Amount
100          aa          500
200          aa          200
100          bb          400
Hope this helps .

New DSO data fields are not available for transformations in the upwardflow

Hello,
There are data flow from
many source DSOs -> Target DSO -> Final DSO.
Different transformations are defined and activated with DTPs. This works fine and provides the desired results.
now new fields are added to the target DSO, final DSO and one of the source DSO.
When I now try to edit the transformations, the new fields are not part of the sources at the different stage.
The fields are available in the Data Source created out of a DSO but not directly when using a DSO as a data source.
Have anyone faced such a problem?
any solutions to this?
- I cannot delete all the other transformations as this is too much work to do and there is no time for it.
Regards
Kannan

We created ZMD_BS_MAT_OVP_LAYOUT. But the situation has not changed - the fields are not available for edit.

How to improve performance of DSO activation

Hi all,
We have created a DSO which is updated daily from another DSO. The extraction is from the Active table of the source DSO, so all records are extracted, in this case roughly 1,000,000 records. (we cannot use delta update for this particular DSO)
Because of the large number of records, the activation of the data in the target DSO is quite slow (ca 20 minutes).
My question: Is there any way that we can analize where exactly the time is lost during the activation and how we can improve the performance? Is it for example possible to deactivate the Change log?
Note that I am already familiar with RSODSO_SETTINGS, and also, we do not want to switch to write-optimized DSO.
Thank you in advance for your help.

Hi
DSO Activation can be improve by unchecking the "SIDs Generation upon Activation" check box in the DSO settings as it takes lot of time to create SIDs while activations. We can go ahead with this option only when we dont have any reports based on that DSO
Thanks & Regards
Rohit

Data load failed while loading data from one DSO to another DSO..

Hi,
On SID generation data load failed while loading data from Source DSO to Target DSO.
Following are the error which is occuuring--
Value "External Ref # 2421-0625511EXP " (HEX 450078007400650072006E0061006C0020005200650066
Error when assigning SID: Action VAL_SID_CONVERT, InfoObject 0BBP
So, i'm not getting WHY in one DSO i.e Source it got successful but in another DSO i.e. Target its got failed??
While analyzing all i check that SIDs Generation upon Activation is ckecked in source DSO but not in Target DSO..so it is reason its got failed??
Please explain..
Thanks,
Sneha

Hi,
I hope your data flow has been designed in such a way where the 1st DSO as a staging Device and all transformation rules and routine are maintained in between 1st to 2nd dso and sid generation upon activation maintained in 2nd DSO. By doing so you will be getting your data 1st DSO same as your source system data since you are not doing any transformation rules and routine etc.. which helps to avoid data load failure.
Please analyze the following
Have you loaded masterdata before transaction data ... if no please do it first
go to the property of first dso and check whether there maintained sid generation up on activation (it may not be maintained I guess)
Goto the property of 2nd Dso and check whether there maintained sid generation up on activation (It may be maintained I hope)
this may be the reason.
Also check whether there is any special char involvement in your transaction data (even lower case letter)
Regards
BVR

Deletion of requests from Write optimized DSO

Hi all,
Tried using this RSSM_DELETE_WO_DSO_REQUESTS to delete requests more than 60 days, via process chain.
But this is not removing all requests more than 60 days. Quite a few are not getting deleted and even on second run of this program, deletes one request at a time. Not sure why this behaves this way.
Any other alternative as Deletion of WDSO (Write-optimized DataStore object) Load requests and active table data without deleting it from target
This also seems to work...?
Also, how should I ensure uniformity of timelines w.r.to PSA and changelog of this DSO flow? PSA 15 days and changelog 90 days retain is fine? Want to ensure no data comes again thats deleted in WDSO

Can some one suggest pls

Clean-up changelog in source DSO

Similar Messages

Maybe you are looking for