Delta load issue from DSO to DSO

Hi Experts,
We have a scenario where we need to load the delta from DSO to DSO. when we are running delta from DataSource to DSO it is picking some around 100 records, but when we are running delta from DSO to DSO it is picking some around 80000 records. But in previous deltas it has taken as equivalent to staging DSO only, but in today delta it has different. Could you please give some pointers, why it is happening like this.
Thanks
Konda Reddy

Hi,
There are no routines in DSO's and transformations also we have not changed, the thing is that in previous deltas it has taken same recoreds as in the staging layer. In between we have done one full load from DSO to DSO, is this makes difference in picking up the delta. And again we done delta then it has taken aroung 80000 records which includes the full load records also. could you please provide some pointers.
Regards,
Konda Reddy

Similar Messages

Delta loading procedure from Write Optimized DSO to Infocube

Hi All,
We are using Write optimized DSO in our project to which I am loading data using Standard DSO 0FI_GL_12
From Write optimized DSO, we are loading delta records into Infocube, please provide your inputs to my following questionnaire:
1) I am quite interested to know how the delta records gets loaded into infocube whenever we are using 'Write optimized DSO' as we don't have any image concept in Optimized DSO
Ex: If am using Standard DSO, we have Change log table and image concept will allow to get updated value to Cube
let us assume
Active Table
111            50
111            70 (overwrite)
Change Log Table
111            -50        (X -- Before Image)
111             70    ( ' ' -- After Image) symbol for after image is 'Space'
So if we load this record to the target as a delta the above two records from change log table will get loaded to the CUBE and Cube will have 70 as the updated record
If am using 'Write Optimized',
Active Table
111            50
111            70 (overwrite)
When this record loaded to the cube, as Info Cube is always having 'Additive' feature so the total value will 50+70 =120 which is wrong?
Correct me what feature will work here to get updated value as '70' into Cube from Write Optimized DSO'
2)As the data source is delta capable and having 'ADDITIVE' delta process, only the delta records based on REQUEST ID are loaded into Info Cube with the updated key figure value?
Thanks for your inputs and much appreciated.
Regards,
Madhu

Hi Madhu,
In best practice, we use WODSO in Initial layer and then Standard DSO. Just for mass data load/staging purpose.
In best practice : Data source ----> WODSO ---> std. DSO
In your case : Data source ----> Std.DSO -----> WODSO.
In both cases if data load design is not in accurate way, then your cube will have incorrect entries.
For ex: today 9 am : 111, 50 (in active table)
Data load to cube, same day 11 am : then cube will have 111    50.
Same day, value got changed in std. DSO 1 pm :   111   70(over write function @ active table).
Same day/next day if you load data to cube, it will have 2 records one is with value 50 and other would be 70. So to avoid such scenarios we should plan load in accurate way. Else make change your DTP settings as ‘source table : change log table.
Coming to your case:
Once after the load to Std. DSO, load data to WODSO by changing the DTP settings ‘Delta Init.Extraction from’ : Change log.
Now data available @WODSO from change log table, then you load to cube In delta mode.

Long time to load data from PSA to DSO -Sequential read RSBKDATA_V

Hi ,
It is taking long time to load data from PSA to DSO. It is doing Sequential read on RSBKDATA_V and table contents no data .
we are at - SAPKW70105. It started since yesterday . There is no changes in system parameters.
Please advice.
Thanks
Nilesh

Hi Nilesh,
I guess the following SAP Note will help you in this situation.
[1476842 - Performance: read RSBKDATA only when needed|https://websmp107.sap-ag.de/sap/support/notes/1476842]
Just note that the reference to Support Packages is wrong. It is also included in SAP_BW 701 06.

Loading data from infoset to DSO

Hi,
Iam loading data from InfoSet to DSO..the transformations were fine..no errors found.
But could not activate the target DSO.
Getting error.".Error while activating transformation"
How to over come this??
Thanks
Ravi

Hi Ravi Kanth,
Please check the following links. Hope this helps.
[/message/1410802#1410802 [original link is broken];
[/message/2115621#2115621 [original link is broken];
Thanks,
Sruthi

Urgent : Error while loading data from PSA to DSO

Hi,
I am working on 7.0.
When i look for data into PSA then i have 1 date field which is containing data in proper date format. This date field is mapped with 0CALMONTH & 0CALYEAR for which i have written routine and directly assigned to 0DOC_DATE .
I have written a start routine to do some modifications in SOURCE_PACKAGE.
But When i am loading data from PSA to DSO its giving below error:
" Exception wrong_date ; see long text RSTRAN 303
Diagnosis
An exception wrong_date was raised while executing function module
RST_TOBJ_TO_DERIVED_TOBJ .
System Response
Processing the corresponding record has been terminated.
Procedure
To analyze the cause, set a break point in the program of the
transformation at the call point of function module
RST_TOBJ_TO_DERIVED_TOBJ . Simulate the data transfer process to
investigate the cause. "
I am not getting why this error is coming up
pls guide me !!

you can map the code to DOC_DATE .
The code is used to read from any date and convert that into Fiscal year/period.
Try this code.
data: l_fiscyear type t009b-bdatj.
call function 'FISCPER_FROM_CALMONTH_CALC'
exporting
id_date = COMM_STRUCTURE-doc_date
iv_periv = 'V9'
importing
ev_fiscyear = l_fiscyear.
result value of the routine
RESULT = l_fiscyear.

Error while loading data from PSA to DSO

Hi,
How to identify the erroneous records in DSO?
While loading the data from PSA to DSO through Process chains we are facing the error says:
"Value '#' (hex. '0023') of characteristic 0BBP_DELREF contains invalid characters"
"Error when assigning SID: Action VAL_SID_CONVERT InfoObject 0BBP_DELREF"
There is no error records in PSA but it seems some invalid characters exists.
Could you please help us how to find the error records in DSO and how to correct it.

Hi,
These are errors BRAIN290 & RSDRO302.
The problem here most likely is that BW doesn't recognise a character you are trying to load. Generally the character is not "#",
as BW displays all symbols it does not recognise as #. You should decode from the hex string what the actual value is. Note that hex values < 20 are not allowed in BW.
Please review Note 173241 and the document mentioned within.
This shows what characters are not allowed in BW characteristic values.
You should check if the character is allowed, and then you can solve the problem in one of the following ways:
1) add this character to the "permitted character" list in RSKC as described in the note.
2) correct the value in the source system.
3) correct the value in the PSA (to do this, you will need to delete the request from the ODS object and then you can change the disallowed character via the PSA maintenance).
4) follow Note 1075403 so that the characters HEX00 to HEX1F are not checked (this affects only characteristics that do not allow "lower case").
5) if you cannot use any of the above options, then you will need to create a routine in your transfer rules for the affected infoobject, and change the value to a character which is permitted in BW.
These are the usual ways to solve this issue.
Rgds,
Colum

Error while loading data from PSA to DSO using DTP

Hi,
I have a Unique aplha numeric identifier of type "Char" length "32" . When I am loading the data from PSA to DSO using DTP I get the following error message:
"An error occurred while executing a transformation rule:
The exact error message is
Overflow converting from ' '
The error was triggered at the following point in the program:
GP4JJHUI6HD7NYAK6MVCDY4A01V 425
System response
Processing the data record has been terminated"
Any idea how I can resolve this....
Thanks

Hi,
fist check weather any special characteristics if not
check in data source under this we have fields tab check the format of a particular field format internal/external/check u choose internal format, if any check routine once
use Semantic Groups in the DTP.
Try it
Thanku
lokeeshM
Edited by: lmedaSAP_BI on Oct 20, 2010 6:44 AM

Delta load issue in COPA

Hi All
We are using COPA datasources and daily delta loads will goingon from source system R/3 without any issues.
last day the delta load from source system was failed due to some basis problem( non availability of WP) and we deleted that bad request in the DSO and then repeated the failed IP in the process chain,then the delta load was succesful but 0 records has been updated.
So we are missing that delta records,I guess this is due to the time stamp set in the source system.
In which table does this timestamp exists and what is the procedure inorder to solve this issue
How do I need to solve this type of issues.
Please let us know .,
Regards
Shankar

Hi Shankar........
I think u hav'nt make the QM status red.......when a delta load will fail............always make the the QM status red before repeating the load...........it will set back the QM status.........and when u will try to repeat the load.....system will ask for a repeat delta...........and a repeat delta will pick all the failed records along with the new records(if any).......
I think u should do reinit............ie.......
1)Delete the init flag
2) Fill the set up table with selection.........did u know which values r missed........any selection criteria..like date.......
3) Then do Full repair
4) then delta....
If u don't know the selection..............then u hav to load data for a selective range.........check ur DSO.....if the Update mode is Overwritten........then no probs.........otherwise there may be duplication of records.........then u hav to do selective deleteion........
Hope this helps......
Regards,
Debjani..........

Master data delta load issue

Hi Expert,
We have recently enhanced a Master Data object with 3 fields. These fields are directly mapped from a DSO. When the delta load is done, these 3 fields are not getting the data, while a full(selective) load gets the data and the 3 fields get populated. What can be the reason for this?
Thanks,
Anupama

Hi,
Then if data already updated to info object through full load, again if you run delta dtp for the same its not fetch any records, so after full load, initiliaze the delta dtp, In DTP in exectue tab you will select processing mode as select option : No data transfer delta status in source is : fetched, aftet that you can run your regular deltas. it will work.
Regards,
satya.

SAP Mobile Sales 2.0 delta load issue for Sales Orders

Hello,
we have used Mobile Sales 2.0 with a Windows app for a while now. Our current issue is that sales reps won't see any historical sales order data on their devices.
Background
Due customer requirements, we need to make small changes to customer master data attributes and reload all customers from ERP to CRM. Then we ran delta loads (MAS_PARTNER followed by all other objects) to DOE, in which virtually all 5000+ customer accounts were compared. The delta load ran for about 3 days (some performance bottleneck we haven't located yet).
During the delta load, data on devices was inconsistent. Accounts were missing and all transaction data disappeared. After the delta loads, all accounts and contacts are OK, save for a few. Data from activities (appointments, tasks) have reappeared, as they should. Only sales orders won't reappear. The sales orders exist in the backend and belong to active accounts and sales reps.
Settings and troubleshooting so far
We don't have any limitations for sales orders in CRM Sales Mobile configuration.
We've run delta loads for all objects in transaction SDOE_LOAD.
MAS_CUSTOMIZATION etc seem fine.
We've re-run initial load for sales orders from CRM.
In the test system, we've even reinitialized the whole CDS database on DOE and on the devices, then re-ran the loads.
Checked steps suggested in discussion
SAP CRM 2.0 initial load issue
Historical sales orders (those created before the master data reload) exist in the backend, but don't show up on the device.
If I change one of those historical sales orders in the backend, it gets sent to the device.
If I create a new sales order in the backend or on the device, it is saved and replicated just fine.
To sum it up, it seems DOE is unable to identify the sales orders relevant for replication.

First Doubt i got clarify by my self as we can go with Unwired Runtime option .
But i still have doubt in :
2. How can i Modifying the Main Menu for iOS.
i am able to customize the same for windows using files SybaseCRM.Configuration.xml file.
Same how can i do for iphone/ipad.

Delta Load failure from ODS to Cube

Experts,
After CRM upgrade, I had to reinitilized the delta process. In this, I reloaded ODS with first init delta without data and then delta load with new data created in CRM. This worked good so far. After this when I tried to load cube with init. delta without data, no issues. But delta load from ODS to Cube doesn't work. Does anybody have any suggestions, please?
Thanks,
Nimesh
Following error observed in Status for delta load from ODS to Cube.
Error when transferring data; communication error when analyzing
Diagnosis
Data Packets or Info Packets are missing in BW, but there were - as far as can be seen - no processing errors in the source system. It is
therefore probable that an error arose in the data transfer.
With the analysis an attempt was made to read the ALE outbox of the source system, which lead to error .
It is possible that no connection exists to the source system.
Procedure
Check the TRFC overview in the source system.
Check the connection of the source system for errors and check the
authorizations and profiles of the remote user in both the BW and
source systems.
Check th ALE outbox of the source system for IDocs that have not been

Hi,
As far as i understood, you have successful deltas' loading to the ODS and you want to update entire ODS data to the Cube followed by daily delta's.
If this is the case,
Make sure that you have active update rules exist between ODS and Cube.
First goto your ODS and right click and select option 'Update ODS data in data target'.
Select Init update > IT will take you to the init info package where you select init <b>with data transfer</b> (Init with data transfer will bring all the records from ODS to Cube)
Once init is completed ,you can schedule to load delta's regularly form ODS to Cube by following the same steps.
Hope this helps
Praveen
Message was edited by:
Praveen Vujjini

Delta loading unsuccessful from cube

hi all,
I am using a delta load from one planning cube to another.When the changed records are of a magnitude of 100 then it is successful but when the records are of magnitude of 100000 then it stays yellow with no data records sent and eventually fails.the packet size is 20000.
any help is appreciated.

Hi ,
do Reintialization of delta loading.... and also check out infopackage.
Check out with this link
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/e6769d90-0201-0010-848d-ae3c7bb18f8a
Hope it helps
Reg
VArun CN

Delta loading issue

Hello,
I created a specific datasource based on a standard table in which there is a "changed date" field.
I used this field to create a delta loading for BW. Unfortunately, a change has been made yesterday after the delta loading and today the delta doesn't load this entry.
Is it possible to change the current status of the relevant field in order to restart the delta from the day before yesterday or should I suppress the data and launch a new init ?
Thanks for help.
Regards,
Bertrand

The date of the previous load is stored in the table ROOSGENDLM. You can modify the date with the transaction SE16.
Regards,
Fred
Edited by: FCI on Apr 8, 2009 10:08 AM

Data loading issue from BW Production to BW Sandbox

Hello Guys,
I am trying to load data from one info cube (Production) to another info cube (Sendbox) applying update rules for prototype model. I am not getting any error in monitoring window for Info Package. But what I see is '0 from 0 records' for long time. I have tested connection between two systems that looks O.K. There is data in Production Cube. This is first time I am loading data between two BW systems. I am not sure what could be wrong. Can some one please help me ASAP? Thanks a lot.
Export data source for that cube in production is created.
Kate

Hi Kate,
The first thing you might want to check is the status of the extractor job in your Production system. The job name will be same as the request name BI_REQU*. So, in SM37 of Production system check for the extractor job <request number> and check the status of the job. If it is running, it means that ur extraction is running still and you can wait for some more time or monitor the job closely in SM50 regarding it's progress.
If it is in cancelled state, you need to check the job log or any short dumps for the error message.
Regards,
Sree

ERROR DURING LOADING DATA FROM PSA TO DSO IN "PRUEFMBKT"

Respected all
I am trying to load data through an r/3 field( pruefmbkt, char-40length) to infoobject. the data is coming correctly to psa but when i am loading it in to dso or infocube request is turning red giving following error message--
Value '010/12.05-112.15/hold on not operate' (hex.
'3031302F31322E30352D3131322E31352F686F6C64206F6E20') of characteristic
PRU_LSIL contains invalid characters
Message no. BRAIN060
Diagnosis
    Only the following standard characters are valid in characteristic
    values by default:
    !"%&''()*,-./:;<=>?_0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ.+
    Furthermore, characteristic values that only consist of the character #
    or that begin with ! are not valid.
    You are trying to load the invalid characteristic value 1. (hexidecimal
    representation 3031302F31322E30352D3131322E31352F686F6C64206F6E20).
Procedure for System Administration
    Try to change the invalid characters to valid characters.
    If you want values that contain invalid characters to be admitted into
    the system, make the appropriate setting in BW Customizing. Refer to the
    documentation describing the requirements for special characters and the
    possible consequences.
    For more information on the problems involved with valid and invalid
    characters, click here.
kindly give me the solution how to deal with this problem.
thanks
abhay

HI Abhay,
please check if the infoobject corresponding to field PRU_LSIL in BW system has lower case checkbox enabled in the infoobject properties, as the value '010/12.05-112.15/hold on not operate' coming from R/3 has lower case alphabets.
Hope this helps.
Regards,
Umesh.

Delta load issue from DSO to DSO

Similar Messages

Maybe you are looking for