Delta records not updating from DSO to CUBE in BI 7

Hi Experts,
Delta records not updating from DSO to CUBE
in DSO keyfigure value showing '0' but in CUBE same record showing '-I '
I cheked in Change log table in DSO its have 5 records
ODSR_4LKIX7QHZX0VQB9IDR9MVQ65M - -1
ODSR_4LKIX7QHZX0VQB9IDR9MVQ65M -   0
ODSR_4LIF02ZV32F1M85DXHUCSH0DL -   0
ODSR_4LIF02ZV32F1M85DXHUCSH0DL -   1
ODSR_4LH8CXKUJPW2JDS0LC775N4MH -   0
but active data table have one record - 0
how to corrcct the delta load??
Regards,
Jai

Hi,
I think initially the value was 0 (ODSR_4LH8CXKUJPW2JDS0LC775N4MH - 0, new image in changelog) and this got loaded to the cube.
Then the value got changed to 1 (ODSR_4LIF02ZV32F1M85DXHUCSH0DL - 0, before image & ODSR_4LIF02ZV32F1M85DXHUCSH0DL - 1, after image). Now this record updates the cube with value 1. The cube has 2 records, one with 0 value and the other with 1.
The value got changed again to 0 (ODSR_4LKIX7QHZX0VQB9IDR9MVQ65M - (-1), before image &
ODSR_4LKIX7QHZX0VQB9IDR9MVQ65M - 0, after image). Now these records get aggregated and update the cube with (-1).
The cube has 3 records, with 0, 1 and -1 values....the effective total is 0 which is correct.
Is this not what you see in the cube? were the earlier req deleted from the cube?

Similar Messages

Data is not updating from DSO to CUBE

Hi Friends,
Can any one please Guide me.
Data is updating upto ODS but not from this lower level ODS to top of the cube from last week and displaying error as " Exception condition "DATE_INVALID" raised" .
How i can proceed to find which date field is getting wrong date or not getting date ..Can any body tell that how we can analize the possibilities in this case to find the error and solution .I need to solve this today,Can any body guide me please.
BR,
Venkat

hi
check the transformations between dso and cube, and check any inconsistence. if not then follow the link
http://www.consolut.com/en/s/sap-ides-access/d/s/doc/F-DATE_CONVERT_TO_FACTORYDATE
this may help you.

Double Records in Update from DSO to CUBE

Hi,
I have a standard flow of DataSource - DSO - InfoCube - Multi Provider
The data in DSO is correct BUT the data in INFOCUBE is DOUBLED.
Question, could this be due to mis match of Key Fields ?
I only have a subset of DSO Key Fields in my InfoCube.
Could this be the reason

Hi,
once the DSO loads the request into infocube with some records.But the DSO wont be allowed to load the same request in second time. it transfer only '0' records.please check the request in Infocube.
if that cube have the double data you can delete data in Infocube after compression based on request Id. we can go for Reverse Posting. We can reverse post the data only when we process the data through PSA.
If u reverse post the data for a compressed request, the data for the compressed request is taken from PSA multiplying with -1 for the key figure values and loaded into the data target.Now the data in the data target is available in F table with negative key figure values.then Compression of Info Cube the data moves from F table to E table and nullifies the data in Infocube for the request ID.
Note: for deleting the zero key fig values by check mark zero elimination option in collapse tab.

Info record not updated from PO , PO updated from Info record

Dear Gurus,
I want to restrict Base price in PO will be copied from Valid info record. User does not permitted to change the Base price once info record not maintained.
Kindly tell me the configuration steps to adopt the process ?
I don't want to update infor record from PO also.
I know while making PO i can untick infor record not update, but that is user specific.
Thanks in advance
With regards
SD

Dear Sidi,
Thanks . Problem solved.
When info record is maintained the price condition will get from there. for this change in condition type P001 , set "D" in manual entries column.
When info record is not maintained, then the system will try to get the price from last PO, if not present, it will throw an error u201CNet price must be greater than 0u201D and sets price condition PBXX (manual entry) to manually enter the price you want.
What you can do:
Is make the condition type P000 as automatic only (option D as below) and also same for condition type PBXX.
Regards
Soumen

Delta Records not coming from sm13 to rsa7

Hi,
We have found that for the application 02, delta records are coming in RSA7(delta queue) even if these are coming in sm13.
It appears that some protocol responsible for bringing the delta records from sm13 to rsa7 is failed.
Fact is that for the data sources related to application 02 (purchasing: LO Cockpit), we did some enhancements through LBWE.
But before transporting the relavant requests to production, we did not delete sm13 and rsa7 entries and also at the time of transpoting the requests in production, postings were made by several users and the entries for those were appearing in sm13.
Thing to notice is that whatever fields were shifted in LBWE, those changes have successfully appeared in production after transporting ( LBWE and relavant Extract Structure in Production are containing the required changes)
Now each time to load the data in BW, we have to delete and refill the set up tables and schedule full update which is taking a lot of time and not advisable.
Each time when we are running job control in LBWE, it is throwing dump in ST22 with the heading CONNE_IMPORT_WRONG_STRUCTURE.
It appears that some internal problem has occured in the structure of rsa7/sm13 for application 02.
Also it is written in the dump that:--
When attempting to import data, the structure of the complex object
"MC02M_0ITM_TAB"
was not compatible with the target object. The error occurred with
component no. 24.
Try to find out why the structure of the object is unsuitable.
There are several possible reasons:
|
--- In the ABAP Dictionary, the structure of the imported
|   object has changed. Make sure that the structure of the imported
|   object matches that of the Dictionary structure.
|
|   If the data could not be restored from another source, this data
|   must be read with the "old" structure, then converted and exported
|   back with the new structure, so that future IMPORTs always work
|   with the new structure.
|
--- A new program version is active, and it no longer matches the
    dataset. Try to solve the error by generating the program "SAPLMCEX" again
    as follows:
    In the SAP System, choose the transaction SE38. Enter the program
    name "SAPLMCEX". Then choose the "Activate" function.
Now how to make the things back on track so that delta records come in rsa7 from sm13 so that we schedule delta update in info package.
Is there any OSS Note or Standard SAP Report which we have to run for getting the solution.
If not, please suggest the solution.
Thanks in advance,
Tarun Brijwani.

Hi,
1. Check whether your Extractor will support Early Delta Inti or not..
See this link for Early Delta Initia...
http://help.sap.com/saphelp_nw04s/helpdata/en/80/1a65dce07211d2acb80000e829fbfe/frameset.htm
Minimize downtime for delta intia..
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5d51aa90-0201-0010-749e-d6b993c7a0d6
Perform this activity on Weekends,
Also see 436393 - Performance improvement for filling the setup tables
Note 753654 - How can downtime be reduced for setup table update
2. Obviously Background job.
BG jobs can be monitored thru SM37 and maintain Logs thru SM21 and can be easier for administration
Thanks

Data is not uploaded from dso to cube

Dear Experts,
In one of my process chains uploading of the data is taking place from dso to the cube through DTP.
But only data in data package 1 are transfeered .
The data gets stuck up in data package 2 and data package 3 so the request remains in yellow state only.
Please suggest.

Dear All,
As per ur issue, try to check the following,
1) Check the short dump is there are not in SM12.
2)If found then try to load manually the packet2 and 3 , (we have got an option on the right most corner to load them manually).
3) if 1 & 2 are unsuccessful, try to keep an option of PSA and load the data again.
kindly let me know if you have any issues.
Thanks and Kind Regards,
Saisandeep.

Error when loading delta update from DSO to cube

hi Experts,
I am loading a delta DTP, get dat by requests from an dso to a cube, while doing that encounter an error :
"Exception CX_RS_ERROR occurred (program: CL_RSTRAN_RUNTIME_EXE=========CP,
include: CL_RSTRAN_RUNTIME_EXE=========CM001, line: 210). "
Any pointers ?
Thanks.
Sharat.

Hi Sharat,
We are getting the following error while loading data form DSO into InofCube.
Exception CX_RS_ERROR occurred (program: CL_RSTRAN_RUNTIME_EXE=========CP, include: CL_RSTRAN_RUNTIME_EXE=========CM001, line: 231).
Message no. RS_EXCEPTION000
Please help us in resolving this.
Thanks,
Shalin

Data Not coming From DSO to Cube

Hi All,
I have data in DSO. When i run the DTP , request status is green.
Now when i go to cube and see the data the request has came but data has not transferred .....
The Request Status is green in cube but data is not cuming....
No transferred data.
How can bring data in cube..??
Regards,
Rohit

Hi,
When you loaded the DSO......after that are you loading the cube for the first time?If so .....and still data is not coming..then check if the last loaded request somehow got deleted from the DSO....
If after loading the DSO....you have already loaded the cube...and this is the second time you are loading the cube.........then obviously it will pick 0 records...........since delta DTP always picks the fresh new request..........if there is no new request in the source .......then it will pick 0 records.......
Also both the cased are not working.........then check the End routine or Start routine.if any.......
Thanks and Regards,
Debjani.......

How Delta record is created from ODS to Cube.

Hai Gurus,
I am new to BW and I have question about the delta mechanisam. Please advise...
Suppose an order of qty 50 created in R3, the Ods is loaded with 50 and the cube is loaded with 50 already. If the order changed qty changed from 50 to 40 and I bring this 40 to ods with full update. the change log is created after the activation of ODS and the -10 from the change log is updated to cube?!. Is this correct. Please correct me if I am wrong.
Cheers!!
Vijay.

you set the Delta Methos using the setting in delta maintainance screen of the Generic Extractors.
1. additve delta
2. changed records with new status
i'm not sure whether above description correct or wrong. there is a radio button for Generic Extractors to select the option.
all the best.
Regards,
Nagesh Ganisetti.

Filter in DTP load from DSO to cube by Forecast version not working ?

Hi All
Can any help on the below code I did to filter data update from DSO to Cube in DTP - to filter by next period forecast version. This code is not working it is loading data pf present forecast version also Can any one help please
data: l_idx like sy-tabix.
data: L_date type sy-datum,
      t_gjahr type t009b-bdatj,
      t_buper type t009b-poper,
      1_period(6) type c.
          read table l_t_range with key
               fieldname = 'ZFCSTVERS'.
          l_idx = sy-tabix.
   clear: t_buper, t_gjahr.
    L_date = sy-datum.
    call function 'DATE_TO_PERIOD_CONVERT'
      EXPORTING
        i_date = L_date
        i_periv = 'Z1'
      IMPORTING
        e_buper = t_buper
        e_gjahr = t_gjahr.
*---> Check if the period is 012, then increase the year by 1 and set
*period to 001.
    if t_buper = '012'.
      t_gjahr = t_gjahr + 1.
      t_buper = '001'.
    else.
*---> Increase just the period by 1.
      t_buper = t_buper + 1.
    endif.
    concatenate t_gjahr t_buper+1(2) into 1_period.
    l_t_range-fieldname = 'ZFCSTVERS'.
    l_t_range-low = 1_period.
    l_t_range-sign = 'I'.
    l_t_range-option = 'EQ'.
       append l_t_range.
          p_subrc = 0.
sk
Edited by: SK Varma Penmatsa on Jan 23, 2012 2:30 PM

Hi Praveen/Raj,
Basically PCS_PER_PACK is a KF i have in the DSO, which i use to calculate the total number of pieces which i store in a KF in the cube. The transformation rule to calculate TOTAL_PCS is a routine.
within this routine i multiply PACKS * PCS_PER_PACK to calculate the figure. I do not store PCS_PER_PACK in the cube.
is it this rule that you want me to check whether aggregation is set to SUM or overwrite? Also this rule should add up the total pcs. if I say overwrite then it might not give me the desired result?
Thing which i cannot figure out is since the transformation rules go record by record why would it add up the PCS_PER_PACK figure before calculating?
I cannot access the system at the moment. as soon as i can i will check on it and get back to you.
thanks once again for you're quick response to my need.
regards
dilanke

Delta records are not loading from DSO to info cube

My query is about delta loading from DSO to info cube. (Filter used in selection)
Delta records are not loading from DSO to Info cube. I have tried all options available in DTP but no luck.
Selected "Change log" and "Get one request only" and run the DTP, but 0 records got updated in info cube
Selected "Change log" and "Get all new data request by request", but again 0 records got updated
Selected "Change log" and "Only get the delta once", in that case all delta records loaded to info cube as it was in DSO and gave error message "Lock Table Overflow" .
When I run full load using same filter, data is loading from DSO to info cube.
Can anyone please help me on this to get delta records from DSO to info cube?
Thanks,
Shamma

Data is loading in case of full load with the same filter, so I don't think filter is an issue.
When I follow below sequence, I get lock table overflow error;
1. Full load with active table with or without archive
2. Then with the same setting if I run init, the final status remains yellow and when I change the status to green manually, it gives lock table overflow error.
When I chnage the settings of DTP to init run;
1. Select change log and get only one request, and run the init, It is successfully completed with green status
2. But when I run the same DTP for delta records, it does not load any data.
Please help me to resolve this issue.

Semantic Partitioning Delta issue while load data from DSO to Cube -BW 7.3

Hi All,
We have created the semantic partion with the help of BADI to perform Partitions. Everthing looks good,
first time i have loaded the data it is full update.
Second time i init the data load. I pulled the delta from DSO to Cube . DSO is standard where as Cube is partition with the help of semantic partition. What i can see is the records which are updated in Latest delta are shown into the report rest all are ignored by the system.
I tried compression but still it did not worked.
Can some has face this kind
Thanks

Yaseen & Soujanya,
It is very hard to guess the problem with the amount of information you have provided.
- What do you mean by cube is not being loaded? No records are extracted from DSO? Is the load completing with 0 records?
- How is data loaded from DSO to InfoCube? Full? Are you first loading to PSA or not?
- Is there data already in the InfoCube?
- Is there change log data for DSO or did someone delete all the PSA data?
Sincere there are so many reasons for the behavior you are witnessing, your best option is to approach your resident expert.
Good luck.
Sudhi Karkada
<a href="http://main.nationalmssociety.org/site/TR/Bike/TXHBikeEvents?px=5888378&pg=personal&fr_id=10222">Biking for MS Relief</a>

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

'Get All New Data Request by Request' option not working Between DSO n Cube

Hi BI's..
Could anyone please tell me why the option ' Get one Request only' and 'Get All New Data Request by Request' is not working in DTP between Standard DSO and InfoCube.
Scenario:
I have done the data load by Yearwise say FY 2000 to FY 2009 in Infopackage and load it to Write-optimised DSO (10 requests) and again load Request by request to Standard DSO and activate each request. I have selected the option in DTP's to 'Get All New Data Request by Request' and its working fine between WDSO and SDSO. But not working between Cube and SDSO. While Execute DTP its taking as a single request from SDSO to Cube.( 10 request to single request).
Regards,
Sari.

Hi,
How does your DTP setting looks like from below options ? It should be change log, assuming you are not deleting change log data.
Delta Init. Extraction from...
- Active Table (with archive)
- Active Table (without archive)
- Archive ( full extraction only)
- Change Log
Also if you want to enable deltas, please do not delete change log. That could create issue while further update from DSO.
Hope that helps.
Regards
Mr Kapadia
*Assigning points is the way to say thanks*

Problem while data processing TRANSACTION data from DSO to CUBE

Hi Guru's,
we are facing problem while data processing TRANSACTION data from DSO to CUBE. data packets processing very slowly and updating .Please help me regarding this.
Thanks and regards,
Sridhar

Hi,
I will suggest you to check a few places where you can see the status
1) SM37 job log (give BIrequest name) and it should give you the details about the request. If its active make sure that the job log is getting updated at frequent intervals.
2) SM66 get the job details (server name PID etc from SM37) and see in SM66 if the job is running or not. See if its accessing/updating some tables or is not doing anything at all.
If its running and if you are able to see it active in SM66 you can wait for some time to let it finish.
3) RSMO see what is available in details tab. It may be in update rules.
4) ST22 check if any short dump has occured.
You can also try SM50 / SM51 to see what is happening in the system level like reading/inserting tables etc.
If you feel its active and running you can verify by checking if the number of records has increased in the cube.
Thanks,
JituK

Delta records not updating from DSO to CUBE in BI 7

Similar Messages

Maybe you are looking for