Deltas not working in NW2004s

Hello All,
I am having issues while populating deltas in BI 7.0, we are extracting activity data from CRM and first populating all the deltas into ODS and then moving the data to Cubes. We defined a key figure for count which is always populated as a constant 1 at the DSO level. When we get a new transaction from CRM it gets populated with a count 1 in the Cube and when I get a change record, it has to trigger a record with negative key figure (-1) count to the cube and then add the change record with a new count 1, but its not triggering the negative record and at the same time triggering a new change record with count "0" which is really weird. Thereby throwing off all the key figure counts:
As an illustration:
Delta 1:
Transaction: 12345; Call Status: Open; Key Figure: 1
Delta 2:
Transaction: 12345; Call Status: Closed; Key Figure: 1
Ideally Data in Cube should be:
Transaction: 12345; Call Status: Open; Key Figure: 1
Transaction: 12345; Call Status: Open; Key Figure: -1
Transaction: 12345; Call Status: Closed; Key Figure: 1
But we have in cube:
Transaction: 12345; Call Status: Open; Key Figure: 1
Transaction: 12345; Call Status: Closed; Key Figure: 0
Deltas from ODS to Cube is extracted from the Change log tables. All the data movements are in delta mode. Don't know where and what we are missing or doing wrong. Any help is greatly appreciated.
Regards,
Vinay

Vinay,
It looks interesting to me. Can you please check the Changelog table and compare the entries? did you find before image entry with delta Load in Changelog? ODS should generate 2 entries with Delta record as we know. It's not generating entry with before image i guess.
I will try to put the same scenario in our system. Let us know what is the service pack you are on?
Note: I'm assuming you are working Standard DSO and In the Transformation Start or End routine youare not deleting Before Images.
Regards,
Nagesh Ganisetti.

Similar Messages

Delta not working after upgrade from 3.5 to BI7.0

Hello All,
We have recently upgraded from BW3.5 to BI7.0 and the standard delta is not working now after the upgade. The name of the Extractor is 0CRM_SALES_ACT_1.
Did anyone come across this problem before or can anyone suggest the solution.
Thanks
Madhu

Hi Madhu,
I've experienced a similar problem with this extractor. I attempted to Initialize Delta with Data Transfer to no avail. The job ran for 12+ hours and stayed in "yellow" status (0 records extracted). The following steps worked for me:
1. Initialize Delta without Data Transfer
2. Run Delta Update
3. Run Full Update and Indicate Request as Repair Request
Worked like a champ, data load finished in less than 2 minutes.
Hopefully this will help.
Regards.
Jason

Delta not working in Solution Manager

Hi Friends,
I am developing BI reports for Solution Manager. The problem is I am not able to get Delta records from SM. Delta Queue is active in RSA7, the request is Green in BI. I get all the records when I do a reinitialization. Only Delta is not working.
I heard that the Queue CSA* needs to be registered SM. But I don't how to go abt it. Can someone help me with this.

Hi,
could you pleaes tell us how did you managed to solve this issue as I am facing a similar problem..
Regards
Puneet

Delta not working for 2LIS_17_I3OPER

HI BW Experts,
Can somebody please help me to solve the following problem.
Software :BI 7.0
There is a custom built release flag in the extractor 2LIS_17_I3OPER and it can be changed by users.When ever Flag is changed(R or blank) it should generate a Delta and should be effective in BW system.
But the delta is generated randomly at moment not sure why and when i checked in RSA3 for 2LIS_17_I3OPER all the PM orders are having blank Release flags although they have R in their actual PM order.
So how can i check if Delta is working?
Anybody please help me to solve this issue?

Hi Joseph,
In LBWE check the update mode of the datasource. if it is queued delta or v3, run the job (in job control) before runing RSA3.
I don't know where you are getting the flag from. Your view is nice, but the system will do what is was programed, not what you think. If the flag doesn't generates a modification for the document, you won't get a delta. This field was added from RSA6 or have you enhaced LIS?
Regards,
Diego

Delta not working for datasource 0CRM_SRV_IBASE_TRAN

Hi All
We are facing problem with setting up delta for datasource 0CRM_SRV_IBASE_TRAN after transporting to QA system.
In QA System:
a.Initialization and Full load has worked successfully and it did fetch the
records.
b.But the newly created records are not coming through delta.
c.Moreover delta is working in Dev but not in QA environment. All the transports
have gone in successfully from Dev to QA system.
d.Only difference we found between dev & QA is: Datasource not listed in SMQ1(Outbound Queue) whereas it is listed in Dev System
We have already checked & ensure that following things are in order:
Source System Checks:
1.Init successfully in place. Entry present in RSA7.
2.SMW01 checked.
3.BWA5 & BWA7 checked.
4.GNRWB checked
5.No entry present in SMQ1 in QA system but its present in Dev system???
BW Checks:
6.Datasource replication done. Info source activated.
Would appreciate any help on this.
Thanks
Pramod

Hi Pramod,
SMQ1 will only show an entry, when there are available data for the delta queue, i.e. someone has made a change or added new data.So checking RSA7 and SMQ1 will give the same result, if RSA7 shows more than 0 entries.
The problem may be the init. What init did you do: an init with data, or an init without data, or an init with a filter. Experience with our CRM system tells me, best way to initialize any CRM data is to do a full data init (without filter) or a init without data (without filter). I wonder about the FULL load you mentioned ? When did you do it ?
Kind regards,
Jürgen

CRM Datasource-Delta not Working

Folks,
I am using CRM Standard Datasource 0CMS_RTCM_TRAN-Resale Tracking and Claims Management data..
I have enhanced this Datasource with four fields and transported to Quality system..
no problem with the new additions..Datasource is extracting properly..
but Delta update is not working..Delta Queue is not picking any records..but new transactions are getting updated in the respective source tables..
when i checked in BWA1- am getting these messages:
error message:
(121) MS_RTCM_TRAN: Table SMOXHEAD contains no BDOC name.
Warning messages:
(111) MS_RTCM_TRAN: No mapping found for extract field SLSR_ADDRESS_I..similarily for all the Datasource fields, its showing the same no mapping warning..
its working fine with Full update..but for Delta update am facing these issues..
Can you please explain what could be the reason for this and suggest a proper solution..
Thanks and Regards,
Yog

Hi,
Are there any transactions to change the BDOC name for Standard Datasources??..
In BWA1, when i tried to change these ADAPTER settings, i am getting this message:
"DataSource 0CMS_RTCM_TRAN cannot be edited with this transaction"..
i hope if i specify the BDOC name, Extraction should be happening..
so please suggest where i can perform these changes??..
Note : currently no extraction is happening because of this..
Regards,
Yoga

Delta not working for - 0CRM_SALES_ACT_1

Hi ,
Delta has stopped working for standard extractor 0CRM_SALES_ACT_1.
1] I deleted delta queue from RSA7 in R/3 to load new init, but init is not getting deleted from infopackage. Any idea ?
2] to correct this error, i want to load full repair load but which is the field in this extractor that captures delta ? (I mean 'changed date' like field. Bcoz created date field is only taking new records not changed ones.
Any suggestions to fix this delta and load missing records ?
Thanks,

HI,
1.Can you please check whether its updated to any other data target after loading the staging data target.
2.I remember we use to load with posting date.
Hope it helpsu2026

Copy function not working in nw2004s-ip

Hi,
I am using NW2004s BI-Integrated Planning. I am using the Planning Modeler tool.
I am trying to create a copy function to copy actual data from 2006 to become plan data for 2007.
There are no variables involved. I have specified the infoprovider, fiscal year/period and value type for reporting.
The copy function reads as:
FROM :
Fiscal year / period: 001.2006; InfoProvider: CO-OM-CCA: Costs and Allocations; Value Type for Reporting: Actual
TO:
Fiscal year / period: 001.2007; InfoProvider: Plan Data; Value Type for Reporting: Plan
The fiscal year/period value chosen in both cases is a V3 variant.
I get the same error message every time
" Inconsistent time characteristics: 0FISCPER,V3/001.2007 and 0FISCYEAR,V3/2006"
Ultimately I want to copy to all periods of 2006 to 2007, but to get something working would be nice!
What am I doing wrong?
Any suggestions gratefully received (and points given).

Hi Dave,
We are experiencing the same problem. We've just implemented BW-IP and we are trying to configure through the Modeler a simple copy function from 0cca_c11 to a transactional InfoCube with plan data. Also changing characteristics as: 0fiscyear, 0vtype, 0version and nothing else, both InfoCubes are selected in the filter area, and I think the Multiprovider that we've created in BW is ok. Everything seems to be so straight forward but .. .nothing is working (we had this working in the previous BW-BPS).
Can someone give us a hint of what we may be doing wrong, or a kind of checklist of the things that we have to validate so as to be sure to get this working.?
(tips about the multiprovider in bw? , tips about the filter options?, tips aobut the copy function parameters?)
Regards,
Andrea.

0FI_AR_4 Delta not working like I think it should be

I have the extractor/DataSource 0FI_AR_4 installed and I am on a 7.0 technical upgrade. I have not yet migrated anything to the new 7.0 dataflow so I am still running 3.x data flow with this extractor. My issue is that when I check RSA7 for this extractor I usually see 0 records. Yesterday I saw 3 LUWs in RSA7 for this extractor but they were not AR records - it looked more like metadata. Next I went to RSA3 and chose Update Mode u2018Du2019 and I got zero records back. I ran the Delta InfoPackage 3 times yesterday and only got data once - the other two requests I got back 0 records.
I read that since PlugIn 2002.2 that we no longer have to decouple GL from AR. Is this true? This was my first guess but we don't even have 0FI_GL_4 installed.
Somehow the data is getting into our 0FIAR_O03 DSO, but I canu2019t identify how that data is being collected. It looks like there is also a lag in the time that the data gets entered into ECC and when it finally gets extracted. Any ideas?

There are conflicting statements on help.sap.com
1: In delta mode, data requests with InfoSource 0FI_AR_4 and InfoSource 0FI_AP_4 do not provide any data if no new extraction has taken place with InfoSource 0FI_GL_4 since the last data transfer. This ensures that the data in BW for Accounts Receivable and Accounts Payable Accounting is exactly as up to date as the data for General Ledger Accounting.
2: As the strict connection of DataSources has been abolished as of PlugIn2002.2, you can now load 0FI_GL_4, 0FI_AR_4, 0FI_AP_4 and 0FI_TX_4 in any order you like. You can also use DataSources 0FI_AR_4, 0FI_AP_4 and 0FI_TX_4 separately without 0FI_GL_4. The DataSources can then be used independently of one another.
Which is true?

2LIS_02_ITM DELTA NOT WORKING

Hi,
I deleted the setup tables in LBWG, I filled up the setup tables again.I set the InfoPackage on Delta after the initial extraction. However the delta is not updating any new records. It has been updating 0 records consistantly for one week. I went ahead and deleted the setup tables in LBWG (2nd time), I filled up the setup tables again (2nd time), suddently it updated almost 30000 more records. How can I set this up so that it will update the records atomatically on a daily basis? so that i dont have to redo these steps again and again.
Thanks

LBWE -- maintain Lo **** pit
Step by step
Go to RSA6 and check the availability of the data source
if data source is not available then go to RSA5 (all business content object available here) make a copy of the required DS.
RSA6 - check the DS is available or not..
lbwe - lo customising **** pit...
select required fields - hide - inversion...
do statistical setup run
login to bi
replicate DS..
go to info package
do initalization delta (Delta Q will be generated only after a successfull delta initializtion done. when you do the same system will load historical data from setup table after loading from set up table (init delta) delta Q will be get posted with records for all changes/creation which is happening in R/3 (related to MM) through events. )
i suggest you should go for unserialized v3 (store and transffer on demand )
1. V3 Unserealized ---unsort records
Unserialized V3 -> Update Q> (V3 Coll. Run)---> Delta Q
[When a transaction happends those delta will be get posted in Update Q, in order to transfer those record from update Q to Delta Q you should do V3 collective Run, (the process of loading data from update Q to delta Q is known as V3 Collective Run) ]
2. Qued Delta [SAP recommended]--
It will not sort record or stop record while transferring to to delta q but will continue until the whole record finish. it will have the track of failure record
3. Direct Delta --->Delta Q
it will directly post records to delta Q when transaction happends
hope it will help you
binu v. rajan

Delta not working for a Z Datasource for CRM Services

Hi Experts,
I have created an exact replica of the standard CRM Service Datasource 0CRM_SRV_PROCESS_I and named it as ZCRM_SRV_PROCESS_I by adding a field and populating it using a BADI.
I have initalized this datasource from BI for delta.
Now when I create or change a service order, the delta does not get picked up.
I checked RSA7 and the ZCRM_SRV_PROCESS_I is active.
Have I missed anything?
In my hey days (about 3-4 years back) we use to set up the population (schedule) of the delta queue by V3 update using the cockpit (i think LBWQ).
In CRM are there any other ways?
Please help?
Thanks and Regards
Raj Jain

Hi Pramod,
SMQ1 will only show an entry, when there are available data for the delta queue, i.e. someone has made a change or added new data.So checking RSA7 and SMQ1 will give the same result, if RSA7 shows more than 0 entries.
The problem may be the init. What init did you do: an init with data, or an init without data, or an init with a filter. Experience with our CRM system tells me, best way to initialize any CRM data is to do a full data init (without filter) or a init without data (without filter). I wonder about the FULL load you mentioned ? When did you do it ?
Kind regards,
Jürgen

Generic delta not working with '0calday' change pointer

I have created a generic datasource based on a database view and extracted data with afull load infopackage into BI. Then, I configured the generic delta with a date field and 0calday type. Set the safety interval of 1 day as a lower limit. Saved the datasource in R/3 and Replicated and activated the datasource in BI. Done some changes to a record in R/3.
After that, I created an Init delta infopackage (with data) and extracted the data with the same number of records as extracted in the full load. Note that all these were done on the same day.
If I have done something wrong by doing it on a same day, I should get 0 records.
Why did I get the same data with a delta init package? I wonder the generic delta is configured correctly or not? Please tell me where I have gone wrong. Thanks..

Hi Shiva,
While running the delta init, you have option of without data transfer and, with data transfer.
I am sure, you used with data transfer and thats why got all those records same as full load.
U can use different options like.
1. DO the init without data transfer and then do the full load, and then run delta everyday for delta records
2. Do the init with data transfer then no need to do the full load and the subsequent delta will take care day onwards,
I guess your are good to do the delta load by tomorrow.
Thank-You.
Regards,
Vinod

FI-SL Special Ledger Extractor (Delta not working) Issues

Hi,
We are creating extractor for Special Purpose Ledger using standard SAP methodology.
Step1: Goto Transaction BW01 --> select the Summary table ---> Check for total records and line Items and then execute. This results in extrators created for totals and Line Items.
Issue 1: The Summary table eg. ZLTST has special ledgers Z1, Z2 and ZA where Z1 and Z2 are for spot balances and ZA is for Average Balances, the issue is we dont see any extractor for ZA (we do see extractors created for Z1 and Z2 both totals and line Items)
Step 2: Goto transaction BW03 ---> select the totals extractor and double click
Issue 2: When you double click the check box to Activate Delta Update for Z1 and Z2 (totals) is disabled???
If anyone has configured Special Ledger Extractors in past for release 4.7 and higher please let me know the process to set up delta

Hi Gilles,
As you are a FI-SL consultant, can you provide me peformance issues on FI-SL?
I posted a thread on New G/L and FI-SL performance
My apologizes to post that question on this thread.
Thank you
Bernard

Write optimized dso - Stand DSO loading by Delta Req by req is not working

Hi All,
We have a data flow which has 1st layer having write optimized dso and then we are loading data to Standard DSO.
We are using Delta DTP to load the data with the option "Get All New Data Request By Request", but it is not working.
Suppose if i have 2 requests which are need to update to Standard Dso from Write Optimized Dso, it is updating in single request. We are on SAP BW 701 patch level is 005.
Please suggest me ....

Hi Prasanna,
For reasons of downward compatibility, the system behaves differently for DTPs that were created before "SAP NetWeaver 7.0 Support Package Stack 13"
DTPs for which the indicator is set only get the first new request, even if there is more than one new source request at the time of processing. This restricts the way in which these DTPs can be used in process chains, because requests accumulate in the source and the target may not contain the current data. The Retrieve Until No More New Data indicator is therefore displayed for these DTPs.
I Suggest you to set this indicator and activate the DTP.
If you set the Retrieve Until No More New Data indicator and then activate the DTP, once it completes processing, a DTP request checks whether there are any further requests in the source. If the source contains more requests, a new DTP request is automatically generated and processed. Once the DTP is activated, the indicator is no longer visible in DTP maintenance.
This applies when the DTP is started by a process chain and also when you start the DTP directly from DTP maintenance.
The indicator is set by default for new DTPs that get data request by request.
If you do not select the indicator, the label for the Get All New Data Request By Request indicator changes to Get One Request Only. Once the DTP is activated, only this indicator is displayed in DTP maintenance.
Regards,
Sudheer.

Appended Key figure is not working in Delta reverse record

Dear All,
I have enhanced 2LIS_11_VASCL datasource, to pull value from condition record, called Surchage.
I have set reversal indicator for this field in my datasource. I have written code in CMOD to get this value from KONV table of that sales order.
Now when value is changed, delta record for this, automatically creates reversal record, but it shows new value of surcharge as negative, because that code is pulling value which currently exists in table.
For example for order 350089 , if surchage is $ 100 . User changes it to $200
Then I get following record.
Reversal Record - $200 (This should be instead -$100 , i.e. previous value)
New Record - $100.
Because of this my new value is not getting updated in table.
I can't use overwrite mode in ODS because some other technical reason.
How can I solve this problem?
appended Key figure is not working in Delta reverse record

LIS have before-after delta. So ODS should be in Overwrite mode. If that is not possible.. try sorting the records in Start Routine such way that the - 100 $ is above the - 200 $ records in Data Package.
but this is risky as it will affect other key figures for which things maybe fine. I guess you need take Data Package records in an internal table. And then sort this internal table. then you can read the internal table in update routine of this key figure.
OR (If you are on BI 7.0) you introduce an InfoSource in between DS and DSO with Overwrite mode for this Key Figure.

Deltas not working in NW2004s

Similar Messages

Maybe you are looking for