0FI_AR_4 Delta Timestamp

Hello,
We are using 0FI_AR_4 to extract our AR line items. There seems to be a time delay of 1 DAY for us to get new/changed records. We are on SAP_APPL 603 level 0004. I went through the forum and also looked at SAP Note : 991429. This seems to be for a previous version of ECC. I looked at note details. BWOM_SETTINGFS table seems to be fine in our case. I am not sure where the problem is. Can you please suggest.?
Thanks in advance.

Hi Tibollo
My assumption is the 1 day safety delta depends on the entries maintained in BWOM_SETTINGS. If we apply OSS note 991429, these are minute-based extractors. We are maintining the same entries as the note.
I ran the process chain on 4/26/2011 5:45 PM. I did not get records created on 4/26/2011 in SAP into BI.
I ran process chain on 4/27/2011 9:35 AM. I did get records for 4/26/2011 but I did not get records created on 4/27/2011 in SAP around 8:30AM.
Please advise.
Thanks
Edited by: George Smith on Apr 27, 2011 5:56 PM

Similar Messages

0FI_AR_4 delta problem

We have recently implemented the 0FI_AR_4 extract of AR customer items into BW in conjunction with some of the Collections Management targets. This appeared to be working well and was giving the data we expected. However, after we started loading in Production, we realized that items that were being cleared after the initialization were still being reflected as Open in the BW datastore/cube. In looking at the delta updates, we see the clearing document itself but no records affecting marking the old Open items with a Cleared status/date/etc.
After reinitializing the targets, the affected data looks correct again and the items are marked as Cleared. We get Delta updates nightly but it just doesn't appear to be everything we expect. I have looked at some old notes in this area discussing 0FI_GL_4 and possible dependencies or need to decouple them. We are on SAP ECC 6.0 - 7.0SP14 and BW 7.0 SP21. Could anyone elaborate on if there would still be any need to also load 0FI_GL_4 to get 0FI_AR_4 deltas to work? Or if there is anything I should specifically look for in this area before opening up a message with OSS? For now, I was just going to have reinitialize it periodically to be safe.
Thanks in advance for any assistance you can provide on this...

Abby, we did some more research on exactly how the deltas worked with this extract in our environment. Ultimately we didn't change anything -- I think it was more in just figuring out what timeframes were being pulled so we could understand differences in balances between R3 and BW at a given point. There are other tables involved beyond just BSID and BSAD. Such as BWFI_AEDAT that holds pointers to changed records in BSID/BSAD, since those tables don't have a 'change' date in all instances to work from with deltas. There was also a table called BWOM2_TIMEST that holds delta upper limit timestamp info for each 0FI_AR_4 load and it behaves based on settings in BWOM_SETTINGS. It controlled the time periods involved in each daily load (i.e. in our case, it went from 10 pm to 10 pm), so that was also part of the reason we were 'missing' records. We didn't realize that a load running at 5 am one morning was only pulling records up to 10 pm the preceding night. Once we felt better about the completeness of the records coming into BW, we no longer pursued it.
This extract is by design a daily load. But there are some notes out there about doing additional configuration to set up 'minute based' extraction and be able to run it multiple times in a day. Fortunately we didn't have to look further into it. Also, the 'coupling' between 0FI_GL_4 and 0FI_AR_4 were no longer a requirement in our version, so apparently that was never part of the issue either.
Hope that helps you. Good luck...

0FI_AR_4-Delta Time Settings based on Numeric Pointer Time Stamps

Hi All,
For Numeric Pointersettings for 0FI_AR_4, I checked the table of DELTA settings, the time stamps are different and it says GMT IN BWOM2_SETTINGS.
So I am confused here whether for FI based on GMT timestamps or numeric pointer BAED on documents entered..
say user entered a DOCUMENT clearing ON mONDAY AFTERNOON, WE HAVE BATCH UPDATE on TUESDAY MIDNIGHT, WHEREAS the document not picked up on TUESDAY batch and so the document is still not cleared in OUR report whereas cleared in SAP..
whereas the same document CLEARED in wednesday midnight batch job...so it means there is a delay in picking up the document which is running every MIDNIGHT...
Does anyone clearly explain how its picking and why? hope it is not based on GMT TIMING...
Also I check another table, it has set the time limit of 2AM and whereas our TUESDAY batch runs before 2AM..whereas Wednesday batch runs after 2am, i am not sure whether it could be because of the above issue...

Hi Durgesh,
I checked this link..That's why raised it whether it really works based on the last part in the link based GLOBAL SETTING OF FI...
If it considers 2AM and check the same settings in my system too, it could be the reason, why my data doesn't pupulate on TUESDAY ..I AM THINKING... is my assumption right???
i am still waiting from our HQ team..will see whether that works or not..
then will let you know...

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?

0FI_AR_4 DELTA SO SLOWLY

Hi,
I use infopackege 0FI_AR_4_d to extracted the Datasourse 0FI_AR_4 Customers: Line Items with Delta. The runtime is 18h 59m 8s,but it only have 114 records. It's too slowly.
Processing is overdue.
And the maximum wait time for this request has not yet been exceeded.
the background job has not yet finished in the source system.
Current status
in the source system

Hi.....
Is there many jobs are running in the system...........check in SM37..........may be there is no free Work process..........due to which the background jobs are not getting work processes to proceed.....
Also check in ST04.........if there is any locks or deadlocks in the system..........
If you find any locks and deadlocks.......which are not changing......and seems to be permanent......then take help of the basis people...
Check short dumps in ST22...........also check System Log in........SM21........
Your Jobs are progressing.........but slowly......but still check TRFC......in SM58.......may be there is some stucked TRFC........
Keep on checking the job log in SM37........whether it is progressing or not......and if you find Sysfail in the log........it means it went to short dump.......
Hope this helps......
Regards,
Debjani......
Edited by: Debjani Mukherjee on Oct 28, 2008 5:16 AM

Delta Timestamps in ECC when upgrading BW3 to BI7

Hi,
We are about to do a technical upgrade of our BW 3.1 system to BI 7.0. BW currently contains a large volume of CO-PA Sales and HR Payroll data that are managed through Delta extractions from ECC6.
When BW has upgraded to BI, can we realistically expect that Deltas will continue without any problems.
I understand that the CO-PA time/datestamp for deltas is stored in Table TKEBWTSN and that the HR Payroll time/datestamp for deltas is stored in Table hrms_bw.
Should we backup these tables before the upgrade, so that if the first delta extracts fails, it would be possible to rerun them after updating these tables.
Are there any other precautions that we could take? Unfortunately our development BI system is not set up for Deltas from an ECC source, so we are unable to properly test.
Any suggestions or feedback on managing Deltas during and postupgrade to BI7 would be greatly appreciated.
Regards
Leanne

Hello Leanne,
See this [Best Practice for Upgrade NetWeaver 7.0BI |https://websmp110.sap-ag.de/~sapidb/011000358700000982302007E]
[SAP NetWeaver 7.0 Business Intelligence Upgrade Specifics|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/10564d5c-cf00-2a10-7b87-c94e38267742]
SAP Note 424848 P18SDLInit sels in source sys lost after upgrade 1.2-2.0 (Applies to BI 7.x)
Note 955990 - BI in SAP NetWeaver 7.0: Incompatibilities with SAP BW 3.x
Note 853507 - Release Restr.: Usage Type BI of SAP NetWeaver 2004s
Please see this link for all [BI7.0 Related upgrade info|https://websmp110.sap-ag.de/upgrade-bi]
[Thanks|http://chandranonline.blogspot.com/]
[Chandran|http://chandranonline.blogspot.com/]

0FI_AR_4 safety delta

Hi all,
We have a query on datasource: 0FI_AR_4,and every night i runs a delta load to BW. But the users are telling me that the changes they make aren't shown in the query the next day. But if they wait for 2 days the changes will show. Therefor I started to look for a setting for 0FI_AR_4 delta .
I found a document for "data extracton FI/CO" and here it says i should look in BWOM2_TIME, but here I can't find my datasource. DELTIMEST has setting : 60 ,but i dont know if this means that the delta should wait 60 hours before it should transfer to BW
Any ideas on way my delta is delayed?
Best regards
Anette

Hi there,
Please take a look to this OSS note:
485958
This will explain you that it has a safety interval ina a particular table refering just that.
By default, the data is extracted with the safety interval of 1 day. If the changes are done from 00:00 til 02:00, that safety interval will be 2 days.
Hope this helps,
Diogo.

0FI_AR_4 Arithmetic overflow while extracting delta

Hi All,
While extracting 0FI_AR_4 delta from R/3 only data packages 2-4 were recieved in BW. Data package 1 is missing and the load was terminated with an error: "Arithmetic overflow error converting numeric to data type numeric.#3621 The statement has been terminated."
Looking in RSA7 (in R/3 side) I can see all delta data waiting for Delta Repetition but can not locate any erroneous record (although I get "overflow" error when trying to sum one of the fields there. Sorting this field's values reveals nothing odd).
Any idea as how to locate the bad record(s) , and as how to fix the problem?
Thanks,
OM

Thank you Srinivas,
I've checked ST22 log but besides listing the cause of the dump (Arithmetic overflow...) it gives no details as to the specific record / value / string.
OM

Generic Delta with Timestamp Field

Dear SDN Team,
We changed one of our HR datasource from FULL to DELTA with Timestamp(TMSTMP)-Time Stamp(UTC).
Which Delta we need to take Timestamp(Local) or Timestamp(UTC)
Our Generic Datasource is based on Function Module.This data source contains HR Hours Data i.e Direct Hours & Indirect Hours.
With interval settings has
Safety Interval Upper Limit - 'Blank' .
Safety Interval Lower Limit - 1800
New status for Changed Records (Selected)
It is a HR Generic Data Source.
We are creating the records in PA30,PA40 and going to take the records from PA0000,PA0001
Delta type for this DS is "AIE" as our delta type process for our DS.
I am trying to load the INIT to Cube,but its not allowing to load,saying with 'AIE' delta type its not possible to load to cube.
I changed the delta type to 'ADD' then the safety interval limits changed to
Safety Interval Upper Limit - 1800 .
Safety Interval Lower Limit - Blank.
Additive Delta (selected)
Is it possible to load the Generic Delta Time stamp to Cube?
Please let us know what are the settings & delta type needs to be there to load the Generic Delta Timestamp to Cube.
Your suggestions are really appreciated.
Thanks and Kind Regards,
Lakshman Kumar G

Hi,
We used TMSTMP filed with Data element TZNTSTMPS with data type DEC Length 15 in Function Module & Extract Structure.
Default filed name is TIMESTAMP_UTC,Domain is TZNTSTMPS.
Generic Delta -
Filed name - TMSTMP
Timestamp (UTC) selected
With interval limits
Safety Interval Upper Limit 1800
Safety Interval Lower Limit
New Status or Changed Records selected.
Thanks and Kind Regards,
lakshman

EKBE table for Generic Delta

Hi Gurus,
Good Day to all. I just like to inquire some details for creating generic datasource with delta enabled. I have created a view table with fields from EKBE table, and created generic datasource that reads the view table I have created from EKBE, now it needs delta process with CPUDT as delta specific field name, seeing the data type of CPUDT, it is DATS with 8 length.
I would like to assure if what will be use as marker of delta, timestamp utc, timestamp local, calendar day and numeric pointer?
And if I use one of the above, what settings that needs to be use for the safety interval upper and lower limit?
Thank you for your inputs and really appreciate it.

Hi,
use the CALDAY as a generic delta pointer.
i would like to recommend as: Safety Interval for Upper Limit as 1 and Safety Interval for lower Limit as ZERO
i think your are using the DSO as a staging layer no worry about duplicates.
Thanks,
Phani.

Delta update in Info package

Hai all
what is the us of delta update in info package
I had intially loaded data from R/3 to psa using
(INFO PACKAGE->UPDATE-->Initilize delta process)
Then I had created to more records in r/3 side .
this time I scheduled using DELTA UPDATE I am getting 0 records
then what is the use of delta update
How can I get only delta records with out use of selection condition in DATA SELECTION of INFO PACKAGE
thanks
chaithanya

Hi,
You must specify "1" (day) in the lower limit of the delta maintenance.
I could not post my previous reply so here a new try :
Hi Chaithanya,
Let me explain how the generic delta mechanism with "date"-field works on the R/3 side:
When doing a delta extraction, the current date is stored in table ROOSGENDLT or ROOSGENDLM (anyway not so important).
This date will serve as a "from" date for the next delta extraction, though excluding the current value.
This in order to prevent duplicate records to be extracted during a second delta run on the same day.
Without extra settings, it will thus not be possible to extract two different delta's on date the same day.
Solution :
1. If you do not care about duplicate data (e.g. only field assignments with overwrite functionality in the transformation) goto RSO2 in change mode for your extractor and go into the generic delta maintenance screen. In the settings, enter "1" as safety interval lower limit. Like this, the delta processing mechanism will always subtract 1 day from the day stored as 'low-value'.
In your example this means that the initialisation will transfer 4 records, the delta will transfer 6 (although only 2 were added).
2. Use timestamps to determine delta (timestamp should be updated on savetime of record)
I hope this helps.
regards,
Olav

Delta loads a problem after client copy

Hi Gurus,
I did a system copy from R/3 Testing system to BW Testing system. After the system copy, the delta loads were working fine but now from yesterday the delta does not get loaded from R/3. When I try to make it red and start it again, it states the last request has not completed the delta load and it requests again. It seems RSINFO idocs need to be generated and sent to BW side but this is not getting generated and the load is still in yellow status. Finally the load also becomes red after the timeout time.
I have checked all the connections, they are working fine. There are no entries in TRFC queue and Partner profile is present and is pointing to the correct destination.
Is there any way to make the delta work again. Please advice as this is urgent and the delta loads are failing.
Thanks in advance.

hi,
I did a system copy from R/3 Testing system to BW Testing system. After the system copy, the delta loads were working fine but now from yesterday the delta does not get loaded from R/3
How were the delta working fine without reinitialization of the deltas after the system copy.
The delta timestamp information is stored in SAP base tables. The system copy not only copies the structure but also the data in those tables, the delta enteries in those tables would be of the system from which you copied. You again need to reinitialize the deltas to correct this.
regards,
Arvind.

How to set the delta for existing generic data source

Hi BW Guru's
I have a problem,actually i have a exsting generic data source"ZFRBHRCHY". Master data Object ZFRBHRCHY is getting laoded from all some R/3 Clusters on a Daily Basis. It is full load and takes 4 to 5 Hours, but number of added records(2000) are very less,while total records are more(40Lks).For avoiding this larger load time every day,i want to implement delta extraction for this.
How to implement this,(i want steps for this) .
Thanks in advance,
Regards
reddy

yeas agree with sanakar,
this field which shankar is talking about must be entry date (if u delta timestamp is date, u will also have to mention this table field name in definition of delta), this means that this field will catch last change to the record, so that it will be delta enabled based on the latest change date. This is very important becuase if u use date like posting date to the delta then back dated posting will not captured in to the delta, as delta for this back date is already been done.
Hope u understand this.

How Delta is enabled for all STD Data source?

Hi All
I have a weird qns. cropping most of the time. .For generic, naturally you set and create Funtion module to enable the DELTA..
Where as dont know how to see DELTA enable setting for TIMESTAMPS in the STANDARD Datasource...?
Can anyone help how to find for every datasource and also when we enhance the data source how do you go and change the settings or where to check the delta TIMESTAMP settings?
pls give possible step by step and clear answers to inderstand easily.

Hi ,
As per my knowledge
Delta records are directly selected from the R/3 tables using a timestamp mechanism from Timestamp table BWOM2_TIMEST.
Delta records are directly transferred to BW and no record is written to the BW delta queue.
when we have a delta dataset selected successfully, the SAP R/3 system logs two time stamps that delimit a selection interval for a DataSource in table BWOM2_TIMEST in fields AEDAT ,AETIM ,TS_LOW ,TSS_HIGH.
Table BWOM2_TIMEST serves as a document for loading history from R3. It also provides defined restart points following incorrect data requests.BWOM2_TIMEST is a standard ABAP report available in SAP.It provide the functionality of resetting of the date time of last Delta or Init Extraction from an OLTP system.
ROOSGENDLM is also a standard SAP table available within R/3 SAP systems depending on our SAP version and release level. It stores the delta pointer for each executed Data Source.For the next delta extraction, the delta pointer is therefore extracted from this table and the corresponding delta data is extracted from different DB tables.
The editing of these tables however is not recommended but they are very helpful when we loose delta because of some reason then we can just change ROOSGENDLM table to desired date and it will bring delta from that date .Very helpful in case of rollback of system .Before that we need to maintain entry fro that data source in BWOM2_TIMEST .
Hope this will be helpful .
Regards,
Jaya Tiwari

How to set delta for the generic data source(FM)

Hi Guru,s.
we have created datasource with FM with using templet RSAX_BIW_GET_DATA_SIMPLE . we want to set up delta for that funtion module.plz send me any templet for delta setup.My mail ID is [email protected]
Regards.
hari

Hi,
Use the template RSVD_BW_GET_DELTA_DATA instead.
Or a little bit of coding can be done using the field L_S_SELECT in RSAX_BIW_GET_DATA_SIMPLE to get the Delta records. If your datasource has a timestamp field which can be used for delta settings in RSO2. The last delta timestamp is captured in the field L_S_SELECT.
Use this field as one of the selection criteria in your Select statement. This worked in our case and should be helpful if ur delta field is a Timestamp field.
Hope this helps...
Cheers,
Raj

0FI_AR_4 Delta Timestamp

Similar Messages

Maybe you are looking for