Mechanism to bring back delta records

Hi,
We have got all delta datasources, during last month-end, we found some delta records are missing. What could be the best approach to bring back those missed records. but those records are huge.
What is the best solution? Is Re-initialization with out data transfer? or full load for those dates by undeleting the current requests after those dates?
Thanks in Advance,
Suman

Hi ,
You can delete the setup table and re-fill it , then If you know the document numbers of those records or creation date , etc , you can give those in the selection and load the repair full load for those missed records.
If the V3 job is active then it will fill the delta queue with the recent data , so that the previous delta cannot be pulled.
regards,
karthik.

Similar Messages

Bring Back the Records From R/3 To BW

Hi Friends
We have a Generic data source and define ERDAT as Delta Field of type Calender day.after data coming to BW,we delete some records by using routine.we bring back these records from R/3 to BW.
For Example : 01.03.2006 and 02.03.2006 records are available but 03.03.2006 to 03.28.2006 records are not available in bw. how do we bring back these records from
R/3 to BW.
(Delta Queue contains:-Date on which the record was created is 03.03.2006)
Thanks in advance,
Sam

Hi,
There is no other way you can give selections on for the same, and you need to create another InfoPackage and then choose the required dates through the selections within the same.
And you are not making any changes at the InfoPackage Level? And there is no relevancy whatsoever for the Delta Mechanism.
You got to pull records from R/3 with the specific Dates you got to make selections in InfoPackage in BW.
Hope it helps,
Pradip Parmar

Petition: Bring back FM recordi

Probably fruitless, but let's try and make our views heard and see if we can create a hot thread!?(Even if you don't use this feature please sign if you agree with the principle that new firmwares should not remove paid-for features that are not in themselves illegal.)?To sign the petition, please just reply to this message.

Yep. I am currently looking for a wonderful mp3 wi-fi enabled device that can also be used to record conferences that, for the benefit of hard-of-hearing attendees, are broadcast on private FM channels. I thought I had found the perfect solution in Creative Labs!! But I guess I'll keep looking, unless they bring back FM recording before I purchase something else. Creative Labs, you've lost another potential customer!! And being a programmer and web developer who's fairly well off, I would certainly have advocated your products to all of my clients... but not with them crippled the way they currently are!

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

No.of transferred records do not match with delta records in RSA7

Hi,
The full update was failing since a number of days in 0vendor because of error in the source system. So I did an initialize with data transfer and corrected the PSA data and updated it using scheduler in the infoobject. In this case the number of transferred records was 24300 and added records was 0.Next I executed the delta infopackage and was expecting 0 records,since there were 0 records in rsa7. But I got 16000 records.Can you explain me why this happened?
Regards,
Shalaka

Hi Shalaka,
In which version of SAP you are working?
You might want to have a look at the table BDCP2 which is a different table that handles the delta mechanism for the change pointers.
You can reset the processing status using the program RSA1BDCP ex with following entries.
Now, coming to your issue - to verify the initial loads I am listing some basic checks(step by step).
You can give it a try in Dev/QAS if you have any restrictions in Prod.
1. Check and verify if the RSA7 delta queue is present.
2. In BW system, delete the INITIALIZATION request from infopackage - This should delete the delta queue from RSA7 in ECC system. (I am not 100% sure about this so try this once)
3. Re-initialize the datasource from BW system and note the no. of incoming records in BW. This should match with LFA1 entries.
4. Check the delta queue in RSA7 - There should be a new delta queue created
5. Start the Delta load - The should not be any records coming in to BW
6. Check the entries in table BDCP2 and its process indicator.
7. Create a new vendor from XK01 and check the entry again in BDCP2 table.
8. Run the delta again in BW and this time delta should have the newly created vendor.
Also be aware that since its a master data datasource and deals with change pointers you will not see any entries in RSA7.
A possible reason I could think of you getting 16000 records in delta is because you might have initialize the datasource is past and then started the FULL loads. So the deltas actually started accumulated in BDCP2 with processing status as BLANK and then when you triggered delta again back now all the historical deltas are processed.
This apply with BDCPV too if you are on older version of SAP.
Did you tried running delta's multiple times - you should not face any delta records when the processing status of change pointers is set to 'Processed' i.e. 'X'.
PS: You can find the message type for 0VENDOR_ATTR in ROOSGEN table. This will be useful in looking at table BDCP2.
Please let me know if there are any questions.
Thanks
Amit

Regarding Delta Record

Hi,
Is the delta record is capture for any field changes (Including KF, CHAR) for a particular sales/Delivery/Billing document or on changes of specific fields for sales/Delivery/Billing document.
If delta capture for specific fields change then where (Tables) these fields are maintained and how to find out this.
Points asssured....
Thanks,
Debasish

I meant a ZFIELD added in VBRP (billing docs items) for instance... If you use a standard SD exit to populate this field, the change will be captured by the delta mechanism just before the system COMMITS the transaction (this particular billing document change)...
Adding a ZFIELD in your extract structure will not suffice: suppose that you are adding a ZFIELD in your billing items extract structure; let's assume that your enhancement is populating this field with a simple lookup to VBRK (the header of a billing document).
In few words you want to capture a change in you billdoc head and extract it with your billitm DSource.
This won't work: if a user change the header of a billdoc, only 2LIS_13_VDHDR will capture a delta. 2LIS_13_VDITM won't get any delta record since no item has been changed... Note that enabling this feature would considerably "complexify" the extraction in oddition to bring way much more records... indeed a before image reversal and an after image of the record (before and after COMMIT) would have to be extracted in order to avoid double records in BW....
The above stuff should better be done in BW itself by staging your data with DSOs or even with modelling...
hope this shed light...
Olivier.

Please bring back an option to Add Scroll Arrows!?

Mac OS X v10.7 Lion - has removed scrollbars and changed the direction of scrolling to better align with iphones, ipads, etc. Thankfully, there are options to go back to behavior similar to classic scrolling behavior, with one important exception. Unfortunately, scroll arrows are now completely gone. OUCH !
Through preferences one can make scrollbars be presented. Behavior can be based on the type of device being used, or scrollbars can be displayed all the time. I choose to display scrollbars all the time.
Through preferences one can make the scrolling direction go back to what one expects if one used Mac OS X versions prior to 10.7 Lion. When I'm scrolling content on my MacBook Pro, I'm either using devices that are not "embedded" in the display (the trackpad or the mouse). When others do scrolling say on an iPad, where the scrolling is directly on the screen, I get it that the direction is different. But don't change up and down so it will match a phone or tablet when I'm on a device where I'm doing indirect manipulation of window content.
To the core complaint... Scroll Arrows are Gone: I cannot get scroll arrows any more. Take a look at Mail or Safari. This is especially needed in Mail. I get lots of mail. I want to be able to scroll up and down by pages (yes there is another preference for this) using the scroll region. I can do that. But I also want to be able to scroll the window (say preview window, or mail message content window) by one line at a time. However, there is no option that I can find. Maybe I want to see the whole paragraph at the same time. Maybe I want to see a code fragment of 5-10 lines all at one time.
Some might say we should just use the up and down keys on the keyboard. I would like to do that. However, with Mail, Apple still has not provided the ability to move from message to message in the preview pane without MARKING THE MESSAGE AS READ ! Most email messages (like this one :-) are too long at least for quick browsing. When I use the up/down arrow to go from message 42 to message 49, then 42 thru 49 are marked as read, even though I can do this in a second or so with seven down-arrow presses. Certainly I can't read 7 real-life emails in a second. See below for a post two years ago requesting this feature which many Mail programs have, but which has never been added to Mac's Mail app:
    https://discussions.apple.com/thread/1988930?start=15&tstart=0
    Marking "Read" When Viewing in Preview Pane
    ...Similar discussions occurred on 10.4, 10.5, and 10.6. Here we are on 10.7, but this request has been ignored...
Please bring back some method for turning on scroll arrows again! And yes, give the option for controlling whether they're stacked at bottom of scroll region, or for using the more common model of up arrow at top of region and down arrow at bottom.
Sadly, this is also a core behavior of Mac OS X 10.7. I have Chrome installed. It does not allow scroll arrows either.
So, Apple... Accept that you went too far. Bring back options to turn on scroll arrows.
...and go back and review that mail preview behavior too, while you're at it.
Thanks,
Alan Carwile

Alan,
while the two finger scrolling is a sometime substitute for scroll arrows it is completely inadequate as a full time solution. It is useless in programs like excel that can have multiple split screens and only scrolls in one at at time and there is no reliable way that doesn't affect other operations to tell the program what screen you want to scroll in. With scroll arrows I got arrows for each window when I split the screen. It is typical of apple's (and steve jobs) hubris that they would eliminate these. It's fine if you think it is more sleek efficient use of the screen not to have scroll bars, but why recognize the need for scroll bars and allow us to turn them on and not scroll arrows?.
Forgetting the split screen problem, on the large databases I have with 10s of thousands of records anything other than scroll arrows is unpredictable because the scrolling speed is dictated by the size of the database and the sideways scrolling with the track pad is clumsy.
The lack of compatability in Lion whether with programs or user interface speaks poorly of Apple and it is the first time in a long time I've thought I might be headed back to the dark side.
And I think they do this on purpose, to make people bend to their paradigm -- see Job's refusal for the longest time to let keyboards connect to the iphone.
And, I know I'm not speaking to apple here, I'm speaking to Apple users. Apple doesn't seem to care or think it can do any wrong and has had that attitude for a long time.
brian

Problem in getting Generic Delta records to BW

Hi BW Gurus,
I have got one issues with which I have been struggling a lot for several days . i.e
I am extracting data from R/3 using Generic Extractor (View) from CATSCO and CATSDB. At the time of delta, I tried using Personal No with Time Stamp giving Upper limit as 1800 seconds. I executed Infopackage in BW immediately. But it didn't work out. So plz guide me how I can get Delta Records to BW. Or should I do any necessary factors apart from these in Generic Delta Screen (RSO2).
It is very urgent.
I will be thankful for solving this issue.

Hey I am "Intros" again,,
I am sorry man for giving the wrong T-code mistakenly in my last reply..
To solve the proble...the whole process is same what I told u before..
But... you got to go to T-Code : BD87 , then execute the IDocs manually to bring them in to BW
identify your IDocs which are missing in Monitor screen, then goto BD87 and select those IDocs and click execute... )you can search the IDoc's based on selection conditions)
I hope this will help u...
cheers man..
---Intros

Which field changes will bring the delta into BW

Hi,
On which field changes the delta will bring data into SAP BW. let us say if you bring the data from 2LIS_13_VDITM, any key figure changes in VF02 will bring the data? Only few characterstic changes it will bring the delta data. What and all those characterstics for delta identifies?
Let us say I have added few fields in this extractor from custom table, If I would like to bring the delta for the field changes which lies in custom table, Can I do it by creating custom Business Transaction Events?
advance thank you very much.

Hi SHarsha,
delta update implemented using the characteristic 0RECORDMODE, it describes records to be updated or added.
Alex

Capture Delta records in Fixed Assets Subledger

Hi,
I am creating an extract from ECC 6.0(flat file). After the initial load I will have to capture the delta records, how can I do that?
My file will bring the Fixed asset Balance Sheet accounts at WBS level.(the asset number do not appear in the file).

ADI provides support for the Creation of Assets and performing a Physical Inventory of your assets. This functionality is also provided by the Fixed Assets team using the Web ADI framework in 11.5.10. I'm not aware of the Fixed Assets team providing any other Integration support with Excel.

Re Delta records

Hi All,
We are loading data ecc to bw system (datasource to cube) and by mistake last two request(2days) got deleted even in PSA data is not available,
So can any one help me out to get last few days delta records,
Is any process/tcode to recover delta request...
Regards,
Stanzal

Hi Lucy
Check this below thread.
Re: Job is runnning after failed job in PSA
..and its not possible to give exact suggestion until and unless we know DataSource name.
Delta mechanism varies with DataSource
Regards
Anindya

Delta Records

Hi All,
We have a delta load, by mistakenly we have deleted the delta request and we have delete the backupdata also(PSA request)There are apporximatly 12000 records.
Is there any way to get back these delta records......i know the only way to do full load.
but still i want to know is there any way at r/3 side to know daily wise delta records....
This DS belogs to HR application.
please suggest.

Hi,
Dont you have the request in the reconstruction tab of the cube?YOu will if you are using 3.X flow.
If yes then reconstruct it...
or else follow Sreekanth's advice.
You will see the request in RSMO under deleted requests.
Regards,
Mansi
Edited by: mansi dandavate on May 20, 2009 11:55 AM

TUTORIAL: Disable Auto Save, Versions and bring back Save As

1. Quit the app(s) you want to configure.
2. Launch Terminal.
3. Paste the command below in the Terminal window, then replace 'name of app' with the name of whatever app you want to configure (e.g. 'textedit'), before hitting Enter:
defaults write -app 'name of app' ApplePersistence -bool no
Alternatively, you can configure all apps at once with the following command:
defaults write -g ApplePersistence -bool no
I don't recommend doing this, though, because, for some reason, it slows down the login process considerably.
For TextEdit only, you also need to run another command, as a workaround for errors that prevents it from functioning correctly:
defaults write -app textedit AutosavingDelay -int 0
4. Relaunch the app(s).
5. Enjoy you considerably less infuriating Mac!
If you don't see any changes, a relogin will in most cases do the trick (if not, the app probably uses a non-standard saving mechanism).
Please note: Although this brings back Save As in most apps, this is sadly not the case with Preview and iWork.
To undo any of the above commands, run:
defaults delete -app 'name of app' ApplePersistence
defaults delete -g ApplePersistence
defaults delete -app textedit AutosavingDelay
P.S. If you want to remove data already stored by Versions, you need to delete the hidden .DocumentRevisions-V100 folder in the root directory of your disk(s).

Why?
Because the "Ask to keep changes when closing documents" setting doesn't actually turn off Auto Save and can cause loss of data.
Because the Save As "feature" in Mountain Lion, isn't actually the traditional Save As that OS X had prior to Lion, but a useless, mock version that is likely to cause data loss.
Because Apple still refuses to offer any way of disabling Versions.
Or, in other words:
http://www.idownloadblog.com/2012/07/31/phil-schiller-re-iterates-apple-doesnt-a sk-consumers-what-they-want/

Configuring AAA New-Model brings back old config.

We are assuming responsibility for a set of network gear from a vendor that developed an app for us. They had all the gear authenticate against their radius server. My task today is to remove that config, and point to our ACS servers using tacacs. I thought this would be an easy copy and paste, but when I put in our standard aaa new-model config, it appears like their config involving radius parameters, comes back into play. I have ended up being unable to access these devices, getting 'Authorization Failed' after putting in my user credentials and password. Any suggestions on this would be a big help!

This has occurred on various platforms, but one example is the 2821 router with c2800nm-ipbasek9-mz.124-22.T1.bin.
Here is an example of what is happening:
Beginning Config:
testsw#sh run | inc radius
aaa authentication login default group radius enable
aaa authentication enable default group radius enable
aaa authorization exec default group radius none
aaa accounting exec default start-stop group radius
aaa accounting network default start-stop group radius
aaa accounting network system start-stop group radius
aaa accounting connection default start-stop group radius
aaa accounting system default start-stop group radius
ip radius source-interface Vlan99
radius-server host 10.57.132.21 auth-port 1812 acct-port 1813
radius-server source-ports 1645-1646
radius-server timeout 1
radius-server key 7 0716376F6B0A0A200F2A2F5420240E171A39170A3E03355352
When I issue 'no aaa new-model', the radius server configs disappear:
testsw(config)#no aaa new-model
testsw(config)#
testsw(config)#do sh run | inc radius
ip radius source-interface Vlan99
testsw(config)#
When I re-apply just the 'aaa new-model' command:
testsw(config)#do sh run | begin aaa new-model
aaa new-model
aaa authentication login default group radius enable
aaa authentication enable default group radius enable
aaa authorization exec default group radius none
aaa accounting send stop-record authentication failure
aaa accounting session-duration ntp-adjusted
aaa accounting exec default start-stop group radius
aaa accounting network default start-stop group radius
aaa accounting network system start-stop group radius
aaa accounting connection default start-stop group radius
aaa accounting system default start-stop group radius
aaa session-id common
testsw(config)#do sh run | inc radius
ip radius source-interface Vlan99
radius-server host 10.57.132.21 auth-port 1812 acct-port 1813
radius-server source-ports 1645-1646
radius-server timeout 1
radius-server key 7 0716376F6B0A0A200F2A2F5420240E171A39170A3E03355352
So, just putting back the aaa new-model command, by itself, brings back all the former aaa new-model commands, and the radius server commands. We run tacacs to a pair of ACS servers for all our other stuff, so maybe this behaviour is unique to radius...not really sure. Anyway, the process of changing has hosed up three devices requiring a reload, and one that I dorked up bad enough to have to rebuild the device config!

How SAP determines Delta records?

Dear Experts,
I have a standard extractor 2LIS_02_ITM. It works like this.
1. when a sales order is saved, a customized program creates a new PO and updates a field in the PO using direct update, the abap 'update' command.
2. in BI, this record created is loaded as delta.
3. We notice that sometimes this when delta loaded, this field is blank and sometimes its not.
A. We suspect the delta did not capture program-created PO if this field value is populated as blank by the program.
B. If the program-created PO is opened and edited by user and then saved, SAP would generate a Delta record?
If this delta is created and BI reloads delta, this delta would be loaded into BI and the report would show the field value.
So, I need to check with experts here if using customized program to create a PO and update a field in it at the same time, would this be captured by the Delta mechanism?
Normally, if manually created, the PO would, i assume, be captured in the delta queue. But what about using program?
Please advise how delta is or can be affected by programs and how exactly is delta determined in this case. This standard extractor is set to use delta, i think using numeric field.
So, I am not sure if its due to R/3 or BW. For BW, its a direct mapping of the updated field. So, I do not think there is an issue on BW side.
regards
Pascal

Dear Debjani,
On your reply to point 2 about the timing of LIS V3 update run, I like to seek clarification how the timing could cause the problem given that many delta records have successfully been loaded with existing way where a collection run is scheduled to run every around 15 minutes and is able to capture the delta except in some cases which is the problem? How can the field value change be missed due to this? On your point 3 reply, the PO is created by program and it can be created by user.
I still require some clarification . Hope you can kindly bear with me.
1. For most of the delta records loaded into BI from R/3, there is no problem with the data. The program-created PO records can be loaded. But for some cases, even when this field is populated by program or EDI, after auto-creation of the PO. This delta is loaded into BI with this field being blank.
2. This suggests to me, for most cases of the auto-PO creation, the BI Delta mechanism in R/3 is able to handle PO created by automated program in R/3.
3. So, seems to me, regardless of how the PO is created : user created / by program / by EDI, the delta mechanism seems to work. So, I like to learn more how exactly can TIMING difference (asynchronous) between the creation of PO records and the LIS V3 update delta queue creation batch job have resulted in the field update from not being extracted into the delta queue ?
Solutions (i think):
1. Is it possible to Change the current delta queue update extraction method from periodic (every x minutes) V3 update batch run to the Direct / Unserialised V3 update extraction method as mentioned by Arvind earlier? Would this mean every time PO is created by any means, even by program or field updated by EDI, the delta queue is immediately created to capture the change? This sounds like a solution?
2. Have the auto-PO creation program Trigger an R/3 event to run the V3 update whenever it has completed an update or PO creation to generate the delta queue. Would this load the r/3 too much if run frequently? Or since frequent run would mean also less delta queue created which means shorter run time?
Dear Sven,
would it be good idea to use the program for ME22N to update the particular field After the PO is auto-created by the ME21N program? Would this mean, using these programs will assure that delta is captured?
Best regards
Pascal
Edited by: Pascal Gabin on May 11, 2011 9:24 AM

Mechanism to bring back delta records

Similar Messages

Maybe you are looking for