FI_GL_4 - No records in delta

I am using datasources FI_GL_4 and FI_AP_4 for delta loads from 3 R3 instances. I set my process chain to run at 15 minutes after midnight and got no records. I changed to time to 1:00am and again got no records.
Is there a 'waiting period' after which records are available to the delta?

Hi,
Let me know whether the table BWOM_SETTINGS and one of parameter BWFITIMBOR maintained in this table can clarify your doubt. For further information on this parameter see the following link.
http://help.sap.com/saphelp_bw33/helpdata/en/af/16533bbb15b762e10000000a114084/frameset.htm
This site says that Changing the default value for BWFITIMBOR is not recommended.
With rgds,
Anil Kuamr Sharma .P
Assign points, if it really helps you.

Similar Messages

Number of records in Delta Queue in table level.

Hi All,
I want to know the number of records in Delta Queue for a particular database in Table level. Right now in Production, i dont have access to TCODE RSA7. I just trying to check the Table TRFCQOUT but i am unable to see the exact count of records specific to data source. Can you please provide any other table to see the data and the count of records in delta queue specific to each data source.
Thanks.

Hi Jalina,
Check the follwing tables:
-ARFCDATA
-TRFCQOUT
-ARFCSTATE
In case you can't find what you need in the above tables. You can always ask a temporary access to RSA7 transcation to your basis team or ask them to give you the required information from RSA7 themseleves (of course provide to them a step by step procedure) .
Hope it helps.
Amine

Writing to FI-GL records to Delta Queue using a Function Module

Has anyone of you tried to write FI-GL transactions to delta queue using BTE by configuring a function module. I am trying to achieve it for a datasource based on a view on FAGLFLEXA table (GL Line Items). For some reason I am not able to see records in Delta Queue. I am doing this to achieve RDA functionality. If you have done it please sends me step sequence and the name of FM.
Your help would be highly appreciable.
Regards,
Ram

Hello Ram,
See this SAP Network Blog: [Generic Extraction via Function Module|/people/siegfried.szameitat/blog/2005/09/29/generic-extraction-via-function-module]
Have a look at these docs,
[How to Create Generic Data Sources which use the Delta Queue (NW7.0)|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/10b68b99-022e-2a10-999d-c4dc9ec24a59]
[How to Create Generic DataSources Which Use the Delta Queue (NW2004)|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d3219af2-0c01-0010-71ac-dbb4356cf4bf]
[How to Create Generic Delta|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33]
Thanks
Chandran

Full upload misses records while delta brings them

Hi experts,
I'm using 2LIS_12_VCHDR extractor and with delta exctractions everything is worknig correct. The problem comes when I want to make a full upload. It is not taking the last records (while delta took them). It is not bringing records into BW since the exact day I reloaded the 12 LIS tables.
If I create a sales order, and this order is delivered, my delta infopackage brings it into BW, but my full infopackage is not bringing it.
Any clues?
Points will be given,
Thanks

My scenario is the next one for 2LIS_12_VCHDR:
- Full upload on Nov 13th (6 months ago) and it takes 170103 records.
- I make another full upload today and I obtain 107103 records (the same as 6 months ago, and there are a lot more).
- I make an init request > I create a delivery in ECC> I make a delta upload an it takes it.
- Then I make a full upload and it is not taking it. I still have 170103 records.
Do I have to reiniciate the 2LIS_12 in ECC (OLI8BW)?
In the other hand I have the 2LIS_12_VAITM working with delta every day. How it will affect to this extractor if I reiniciate all the 2LIS_12? I'm going to miss data? I'm going to duplicate data?
Thanks

Is there any solution to Delete Single Record in Delta Queue 2LIS_08TRFKZ

Hi,
Is there any solution to Delete the Single Record in Delta Queue at R/3 -(RSA7) for Datasoure 2LIS_08TRFKZ
A wrong posting has been posted at R/3, its has been deleted once they came to know its wrong at R/3.
Now the Problem is wrong data has come into Delta Queue RSA7.
We are unable to extract the data in BW. Its not even coming till PSA also so that we can delete at PSA itself that particular record.
Is there any solution to delete the Single Record in Delta Queue at R/3 -RSA
Thanks & Regards
Ashfaq

>
Ashfaq Shaik wrote:
>
> Record 166 :Contents <000000000.00000000 from field ZZVOLUME cannot be converted in type DEC RSAR 197
Sorry I didnot see this error before.
I guess you didnot try error handling hence you get this error BW side.Try error handling first.
If this doesn't work then you can go with above method.

Delta package not fetching all records from Delta queue in r/3

Hello,
I have loaded Goods Movement Data using 2LIS_03_BF datasource into my BI system.
The Delta has been initialized and everyday the delta is being moved from r/3.
I observed that when I execute my delta package not all delta records are fetched into PSA from r/3.
For Ex: Before starting my delta package I checked in SMQ1 of my R/3 system and see that there are around 1000 records.On executing the delta package I see that the record count is reduced from 1000 to 400 in SMQ1.On executing the delta package again I get the remaining 400 records into my PSA.
Shouldn't the delta package get all records from the queue on single execution??
Is there some setting to define the nr of records to be loaded?
I'm confused with this behaviour.Please help me understand this behaviour.
Thank You.

Hello,
First thing: the data is not transferred from the SMQ1 queue, rather the data is transfered to BW from the RSA7 Delta queue. You need to check the number of records present in the RSA7 queue.
Since SMQ1 is involved, i think you are using the unserialized V3 update method. In this method, when data is first written to the application tables, it is first transferred to the SMQ1 update queue,then via a job to the LBWQ extractor queue and then to the RSA7 delta queue. So the number of entries that you see in the SMQ1 queue are not the number of entries that have to be transferred to BW but rather the records that are waiting to be transferred to the extractor queue in LBWQ. Similarly, in LBWQ, the number of entries displayed here are not the no of entries that are going to be transferred to BW, they are the no of entries that will be transferred to the delta queue RSA7 when the next v3 update job runs.
If you want to check the number of records that will be transferred to BW, select the datasource in rsa7 and then click on the display data entries button.
Hope this helps.
Regards.

RSA7 shows zero records for delta upload of 2LIS_03_BF Datasource

Dear Professionals,
I am having constant issues with inventory management DataSource (2LIS_03_BF). I scheduled delta upload in r3 production using LBWE, keeping in mind that in LBWE there is no options for posting dates, ETC... In RSA3, there are records, but when i check RSA7, it is showing 0 records. What could be the problem. Do i need to do anything/activation anywhere in LBWE or RSA7 to see the records. Please advise.

Hi,
Normally there should be a collective run which transfers data from the application-specific queues to the BW delta queue (RSA7), just like this workflow:
MCEX03 queue==> RMBWV03 (Collective run job) ==> RSA7-Delta queue => BW
It is necessary to schedule the job control regularly - see point 3 of SAP Note 505700.
Check also these SAP Notes:
869628     Constant WAITUPDA in SMQ1 and performance optimization
728687     Delta queued: No data in RSA7
527481     tRFC or qRFC calls are not processed
739863    Repairing data in BW
Rgds,
Colum

How can we get changed records in delta in case of numeric pointer

Deall All,
Thanks to all of you gurus i have been able to Get delta update for my query.
There is one last issue how can i include changes records in my delta update when i am using numeric pointer for data selection.
or
It can only be doen by time stamp.
can you explain me details of using time stamp.
Thanks & regards,
Gaurav Sood

Dear Gaurav,
Here we have three options for delta updation:
Time Stamp:   If we want to update change in the records with respect to the time interval then this option is selected.
Calend. Day:   If we want to update change in the records with respect to day to day basis then this option is selected.
Numeric Pointer: If we want to update in case of record which is completely new with respect to Field name then we use this option.
And we have got some settings like:
Safety Interval upper limit:
This field is used by Data Sources that determine their delta generically using a repetitively-increasing field in the extract structure.
The field contains the discrepancy between the current maximum when the delta or delta init extraction took place and the data that has actually been read.
Leaving the value blank increases the risk that the system could not extract records arising during extraction.
Example: A time stamp is used to determine the delta. The time stamp that was last read is 12:00:00. The next delta extraction begins at 12:30:00. In this case, the selection interval is 12:00:00 to 12:30:00. At the end of extraction, the pointer is set to 12:30:00.
A record - for example, a document- is created at 12:25 but not saved until 12:35. It is not contained in the extracted data but, because of its time stamp, is not extracted the next time either.
For this reason, the safety margin between read and transferred data must always be larger than the maximum length of time that it takes to create a record for this DataSource (with a time stamp delta), or it must display an interval that is sufficiently large (for determining delta using a serial number).
Safety Interval Lower Limit
This field contains the value taken from the highest value of the previous delta extraction to determine the lowest value of the time stamp for the next delta extraction.
For example: A time stamp is used to determine a delta. The extracted data is master data: The system only transfers after-images that overwrite the status in the BW. Therefore, a record can be extracted into the BW for such data without any problems.
Taking this into account, the current time stamp can always be used as the upper limit when extracting: The lower limit of the next extraction is not seamlessly joined to the upper limit of the last extraction. Instead, its value is the same as this upper limit minus a safety margin. This safety margin needs to be big enough to contain all values in the extraction which already had a time stamp when the last extraction was carried out but which were not read. Not surprisingly, records can be transferred twice. However, for the reasons above, this is unavoidable.
Data Source Is Real-Time Enabled
The 'real time enabled' indicator determines whether a delta-enabled Data Source can be used as a supplier of data for a real-time daemon.
And there are two options provided like
1)     New Status for changed records:
If you select this option each record to be loaded delivers the new status for the key figures          and characteristics. DataSources with this delta type can write to ODS objects or master data tables.
2)     Additive Delta:
The key figures for extracted data are added up in BW. Data Sources with this delta type can supply data to ODS objects and Info Cubes.
Hope this helps u..
Best Regards,
VVenkat..

No records in delta queue for 0CRM_SALES_ACT_1 & 0CRM_COMPLAINTS_I

Hi all,
we are linking a SAP CRM system 4.0 (patch level 10) with BW 7.0. We have initialized the delta extraction and everything was fine. Data was extracted and we can see the delta queue in RSA7 but no records are added. Users are creating new activities and nothing appears in the delta queue. We have other extractors delta capable which are working fine.
The main difference is that these two extractors have been enhanced using the Badi CRM_BWA_MFLOW. When we check the extractor using transaction RSA6, records include the information we add in the Badi.
We think the problem is in CRM because, it does not collect any delta data (queue is always empty). BW is capable to extract when initilitialization. We have tried the early delta initialization and the simple delta initialization.
Any help will be appreciated.
Thank you in advance.
As an extension: we can't see the extractors in the qRFC monitor (trans. SMQ1). We can see there the ones which are working...

Hi again,
we finally solved the problem. The thing was that no BDOCS with type BUS_TRANS_MSG were not being generated when creating or modifying CRM activities. Theses datasources need the BDOCS to work. Transaction SMW3_00 had the flag "Do Not Send" set. We unmarked it and everything seems to work now.

No records in delta extractor after change

We have a generic delta extractor that is based on ztable filled by a scheduled load program.
Last week I changed some records and then ran the transaction to fill the table and the program correctly filled the table and the extractor had the delta data.
I then extracted a delta init to an ODS in BW where I had to manually change the QM status of the load from yellow to green and got the status messages that the timestamp had changed from 0 to xxxxxx
Now after this init delta load, I went into R/3 again and changed the records.
Ran the transaction to fill the ztable but no records come up in there.
Also the extractor has no delta records.
In VBAP I see the changed items but in 2lis_11_vaitm, no delta records.
Any thoughts?
Edited by: CC on Jul 1, 2008 12:33 AM

Hi,
We have a generic delta extractor that is based on ztable filled by a scheduled load program.
Now after this init delta load, I went into R/3 again and changed the records.
Ran the transaction to fill the ztable but no records come up in there.
Also the extractor has no delta records.
If I understand correctly, the load program did not add any records to 'ztable'.
If that is the case the extractor running off 'ztable' would not deliver any delta records as there is nothing to deliver.
If my understanding is right you should revisit the load program of 'ztable' to see why it is not filling 'ztable' table as you expect.
BR/
Mathew.

Duplicate records in delta load?????pls help!!!! will assign points

Hi all,
I am extracting payroll data with datasource 0hr_py_1 for 0py_c02 cube.
I ran full load with selection crieteria in infopackage -01.2007 to 02.2007, extracted 20,000 records and then
i ran init of delta without data transfer, extracted 0 records as expected.
then ran delta with selection crieteria in infopackage -02.2007 to 01.2010, extracted 4500 where the FEB month records are extracted again.
what could be the reason for duplicate records to occur in the delta load?
i have seen the same records in full load with selection crieteria 01.2007 to 02.2007 as well as in selection crieteria 02.2007 to 01.2010. What and how it is possible?
Actually the datasource 0hr_py_1 datasource is not supporting delta. apart from this what other reasons are there for occuring duplicate records? plss help!!!!!!!!!!!!!!
Will assign points.

ur selection criteria -
01.2007 to 02.2007 as well as in selection crieteria 02.2007 to 01.2010
both of ur selection includes the month- .02.2007
might b all selections come under .02.2007
hav u checkd tht?
Regards,
Naveen Natarajan

No records - FM Delta queue

Hi,
I did setup all steps for 0PU_IS_PS_44 data extraction from R/3. In doing so I did Initialized Delta process, logged to R/3 RSA7 transaction code to check the queue. At the time of Init I got 300 records. Today I created new Info package to extract the Delta records.
Here my problem is I could not see any Delta extraction to BW. In R/3 I could not see any records in the queue but where as in the RSA3 (Extract checker) the number of records are 324 meaning (324-300) 24 records were created from I did the Init and expected that records to appear in Delta Queue and also while Delta extraction to BW.
Appreciate if one could help me any steps I am missing out or any suggestions to see additional records to extract via Delta.
Thanks in advance.
Best Regards,
Murphy.

Hi Bhanu,
Thanks for your response at both places.
I got resolved the FM data source delta extraction. Adam responded to my post stating the IMG setting required for the activating Delta Queue.
I have the same issues with CO and FI data sources. Even the GL Account master data data source does not show the new/changed records/documents at Delta queue.
Appreciate if you could help me in resolving the problem.
Thanks.
Murphy.

How to see deleted records in delta extraction from view

Hi folks,
i am currently reflecting about delta extraction from a view:
The view contains a date field (change date) which is used to identify new or changed records.
So the delta extraction of new and changed records works without problems.
But what is happening with records that are deleted in the source system?
My current understanding is that deleted records will not be shown in the view. Therefore the deletion is not visible in the extraction.
- Is there a workaround for this problem?
- How is deletion of records normaly handled in generic extractors?
- Is it impossible to extract a deletion when using views?
any suggestions and help will be appretiated...
bye

Hello Florian,
Generally records will not be deleted (until if you physically delete it from table) but will have a status deleted.
So it doesn't matter whether you use view or tables the deleted records will be extracted through the view to update the BW data targets.
Thanks
Chandran

Zero records in delta update

Dear All,
In HR :Time management (Time and Labour )(cube) 0PT_C01 two data sources are there and one is 0HR_PT_1 , during delta load it does not get any recors and it will show zero records at cube level and in r/3 rsa3 ir shows new records.Please suggest how to solve this issue.
Regards
Albaik

Hi,
This is because you havent run the init load till now.
We have to run a init load before running delta(one time process).
now as you have selected init with datatransfer, you got all the records transferred.
from next time, no need to run init and you can proceed with delta.
Cheers,
Srinath.

Zero records in Delta Queue for Non-LO Datasource

Hi,
I have a process chain which loads data daily and last loaded on 5th of this month which is a delta load to DSO, and then I have triggered process chain on 10th and now the process chain got successful but delta is returning zero records. I have gone through the Delta queue monitor, in that the data source is showing 0. what could be the reason for this? The data source is a Generic data source built on View and it is not a LO data source and delta is on timestamp.
Thanks,
Karan.

Hi lokesh.
Repair Full delta option it wont distub existing deltas.....
repair full delta put full update indicate request as repair request.
Via the Scheduler menu we can indicate a request with full-update mode as Repair Full Request. This request can be updated into every data target even if the data target already contains data from an initialization run or delta for this Data Source/ source system combination, and has overlapping selection criteria.

FI_GL_4 - No records in delta

Similar Messages

Maybe you are looking for