Delta load missing

Sorry about that - Kedar
We missed some deltas because we ran them during the day and missed some transactions . I cannot really tell what transactions are missing for me to put in seleciton for the repair request.
Is there any other way ?
Thanks

Hi,
No apologies needed. Just wanted to ensure that your query got answered.
The other way is to dump the cube, delete the init, do a full pull and then reinit without data transfer.
Or you can try to do a selective full pull by giving the selection criteria if you know by date just for that one day and any other filters that you know of(you run a big risk of having duplicate data this way). Or you can try to do the same in your repair request.
Or try to run the delta again, because as Eric mentioned unless the delta was broken there shouldn't have been a cause for you to miss transactions, even if you ran the load in the morning. Any changes after that would be posted to the delta queues and should be available the nex time you run the delta, irrespective of when you ran it.
Cheers,
Kedar
Cheers,
Kedar

Similar Messages

Repair request for Delta load? Orders missing in Billing line Items

Hi
I am using BW 3.5; Some Orders are missing in BW for Billing line item reports (2LIS_13_VDITM) according to the users.
The report is based on Cube directly, ODS is not used. I planned to do a repair full request for this month's data so as to get the missing orders.
Could you please advice me on correct procedure to do that? Delta loads runs every day and todays delta is completed.
Thanks and BR
P.B

While it's usually recommended to execute setups during "quiet time", it's not required. Especially in this case. Since you're going to be restricting the setup to only extract a range of Billing Documents that are representative of the dates of data missing (or purely the identified missing documents), there is no need to wait for "quiet time" because you'll pick up the data either in your Full Repair extract or in the delta extract. Depending on how the target InfoProvider for this data is setup (cumulative v. non-cumulative), you may have to look out for duplicate data.
My recommendation would be to run your setup for only those documents that have been identified as missing. That way, you're limiting the amount of data that's required to be extracted to the setup table and then into BW, but also will remove any risk of duplicate data in your target InfoProviders.

Records are Missing when we run Delta Load( FIGL-ACCOUNT ITEMS)

Hi,
Some records are missing when we run Delta load.
We have one generic data source on FAGLFLEXA table.
We select Field nm TIMESTAMP
TIME STAMP IS LOCAL.
upper limit is Blank
Lower limit is 1000.
we run this process chain every day.
we select delta settings is New status for changed records.
Please give me any idea why records are missing when we run deltas.
Thanks
Naik

Hi Anju,
Please ensure that you are following the below steps while Initilizing the application 13:
1. All the users in source system, must be locked.
2. Ensure that SMQ1 and RSA7 are having no data for application 13. Delete the application 13 datasource entries from RSA7.
3. Delete and refill the setup tables for application 13.
4. Run a INIT with data transfer load for the required datasources of application 13.
5. The Deltas can follow from the next day.
This will ensure that your deltas are fetching correct data. Note that, delta will pick up the same conditions on which the INIT load was run.
Please let me know if you need any more information.
Regards,
Pankaj

Missing Data in 0FI_GL_4 delta loads.

Hello All,
We successfully loaded the 0FI_GL_4 related ODS upto 02/06. We turned on delta loads for the same from 03/06. The data validation team has discoved that there is missing data in 03 and 04. I plan on resetting the delta queue in R3 and reinitialize a full load until april. Here are my questions
1) Are there any specific steps i would need to follow?
2) Are their any other better alternatives then reinitializing with the full load.
Thanks in advance.
Kiran

Initialization Concept :
I will explain this with an example.
You have 5 company codes (CCs) (1000, 2000, 3000, 4000, 5000) in your R/3 source system.
But your client wants reporting in BW only for 3 Company codes (CCs) (1000, 2000, 3000).
In that case, there is no point in bringing the data for other 2 CCs.
So during Initialization, you give the inputs as,
CC = 1000, 2000, 3000 and do a Initialization (With or Without Data transfer)
So henceforth, when Delta is pulled, any changes corresponding to CCs 1000, 2000, 3000 only will be captured.
Eventhough there are changes in 4000 & 5000, they will not be captured in the Delta.
Hope I answered your Question.
Regards,
Balaji V

Missing some master data for delta load( its very urgent please)

Hi,
I am working master data for delta load,the problem is when ever changes(SO) in r/3 RECORDS for address text,City Dstrct Nm.its not getting loaded into BW.every day some delta records are coming into BW.
the data coming thru bw satging and bw.Please help what would be reson and where can i find the detail info,where is it missing.Please see below for example.
Address Number/ Addr Ln 1 Txt/ City Dstrct Nm
9025750333/ #/ #
help me its very urgent

Hi Sumanth,
check the delta queue and the V3 job is it running correctly ,
Have a look at OSS note :728687
and also see the following thread
Deltas are not available in Delta que
Delta Queues are not cleared in R/3
No data in RSA7 for 2lis_03_bf : HELP
check the data may b it is in modifide status not active.
regards,
supriya

Load Missing documents w/o disturbing delta

Hi Experts,
We miss several documents for particular reason. This cube is being loaded with delta package. Now they want the missing documents into the Infocube.We are updating data from R/3 DS(Controlling)----->Cube.
If I load missing documents with a new data package giving required selection in document number, will it disturb daily delta loading process for this cube. What is your advice.
Thanks,
Philaphi.

Hi,
If your data is missing, you may go for Repair full delta option available in infopackage. This would not disturb your deltas and bring in any missing data from R/3.
As you have mentioned that your dataload is delta load, therefore, you would not be able to change the selection conditions for your extraction as the selection condition for your delta load will have to be same as that of your Init delta load.

In infopackges Delta Load option is missing.

Hi All,
               For one infopackges initially we were using "Initialzation Delta Process " Option in update .
      Now we want to change that option into "Delta Load". I went to corrsponding infopackage,but that "Delta load" option itself is not appearing in the update tab.
What shoud i do to get that option in the infopackages.Please help me on this.
Thanks,
Prem

Hi ..
          Because of transfer structure changes i am not able to reconstruct that initial request . I am not able to do initial load also.if i delete the failed "initial delta process "request "Delt load" option will be enabled.i have to enable the Delta load option.Please help me on this.
Thanks to all.
Prem.

Delta Loads are not working: 0FI_GL_10 With enhancement : HR Data in source

Hello Friends. Thanks for your answer on theory which I know, Please help me with this situation. I read all the sdn response to my message and have below for your suggestion
QUES1: Why the 0RECORDMODE is not coming in Standard DSO and hence it is not there in Transformation in between Infosource and DSO. What do I need to include 0RECORDMODE in standard DSO. What is the correct OSS to Implement on SP 10 to solve this.
Ques2. As suggested by you If I run the Delta loads after waiting for 1 hour of Init load. say init load was done at 11 am . i will do the delta at 12:10 am to psa via Infopack and then wait for an hour to run the DTP from PSA to DSO. Delta Records come in but it also bring in the records in DSO that are not changed from about 7 hours in ECC. and make our total Balance incorrect.
Ques3: We have this Cocatenation of Keys in DSO since we exceeded the total number of 13 key in DSO.
Cocatenation#1 GL ACCT and CHRT OF ACCTS
Cocatenation#1 SEGMENT AND CONT AREA
Cocatenation#1 Version, Value Typem, Valuation view, Currency Type.
<b>
Since business want to include HR Data in Keys Like Employee Number, Emp Code, EMPSPIMCODE. Payroll ID and I can not remove these fields from Key in DSO as per the business.</b>
Also the above fields GL ACCT , CHRT OF ACCTS, SEGMENT, CONT AREA
exist in Data FIELDS OF DSO. so what are the steps to modify the design to fix this asap.
Please email me at [email protected] if you have any docs to resolve the above
Thanks
Soniya
null

Did the full load bring all records from sourcesystem to PSA?
Was this an issue with the first delta you have tested ?
Concatentaion of multiple keys into one should not be an issue here as that must have been happening in DSO and delta brings incorrect records to PSA itself.
Are you validating delta records against FAGLFLEXT inputing the timestamp value or RSA3 ..how ?
<b>Check if this note helps</b>
Note 1002272 - NewGL-DataSource 0FI_GL_10, 3FI_GL_*: Missing record.
Is delta bringing incorrect records to PSA or DTP brings incorrect records to DSO from PSA ?
May be you should revisit the logic behind for the enhancement of 0FI_GL_10.
I am facing a similar issue as well but here delta doesnot even bring a single record ( ODS has 20 keys )...will update if resolves and you do the same.
Message was edited by:
Jr Roberto

SAP Mobile Sales 2.0 delta load issue for Sales Orders

Hello,
we have used Mobile Sales 2.0 with a Windows app for a while now. Our current issue is that sales reps won't see any historical sales order data on their devices.
Background
Due customer requirements, we need to make small changes to customer master data attributes and reload all customers from ERP to CRM. Then we ran delta loads (MAS_PARTNER followed by all other objects) to DOE, in which virtually all 5000+ customer accounts were compared. The delta load ran for about 3 days (some performance bottleneck we haven't located yet).
During the delta load, data on devices was inconsistent. Accounts were missing and all transaction data disappeared. After the delta loads, all accounts and contacts are OK, save for a few. Data from activities (appointments, tasks) have reappeared, as they should. Only sales orders won't reappear. The sales orders exist in the backend and belong to active accounts and sales reps.
Settings and troubleshooting so far
We don't have any limitations for sales orders in CRM Sales Mobile configuration.
We've run delta loads for all objects in transaction SDOE_LOAD.
MAS_CUSTOMIZATION etc seem fine.
We've re-run initial load for sales orders from CRM.
In the test system, we've even reinitialized the whole CDS database on DOE and on the devices, then re-ran the loads.
Checked steps suggested in discussion
SAP CRM 2.0 initial load issue
Historical sales orders (those created before the master data reload) exist in the backend, but don't show up on the device.
If I change one of those historical sales orders in the backend, it gets sent to the device.
If I create a new sales order in the backend or on the device, it is saved and replicated just fine.
To sum it up, it seems DOE is unable to identify the sales orders relevant for replication.

First Doubt i got clarify by my self as we can go with Unwired Runtime option .
But i still have doubt in :
2. How can i Modifying the Main Menu for iOS.
i am able to customize the same for windows using files SybaseCRM.Configuration.xml file.
Same how can i do for iphone/ipad.

Issue with Delta Load in BI 7.0... Need resolution

Hi
I am having difficulty in Delta load which uses a Generic Extractor. The generic extractor is based on a view of two Tables. I use the system date to perform the delta load. If the system date increaes by a day, the load is expected to pick up the extra records. One of the tables used in the view for master data does not have the system date in it.
the data does not even come up to PSA. It keeps saying there are no records.... Is it because I loaded the data for yesterday and manually adding today's data...?
Not sure what is the cuase of delta failing....
Appreciate any suggestions to take care of the issue.
Thanks.... SMaa

Hi
The Generic DataSource supports following delta types:
1. Calender day
2. Numeric Pointer
3. Time stamp
Calday u2013 it is based on a calday, we can run delta only once per day that to at the end of the clock to minimize the missing of delta records.
Numeric pointer u2013 This type of delta is suitable only when we are extracting data from a table which supports only creation of new records / change of existing records.
It supports
Additive Delta: With delta type additive delta, the record to be loaded only returns the respective changes to key figures for key figures that can be aggregated. The extracted data is added in BI (Targets: DSO and InfoCube)
New status for changed records: With delta type new status for changed records, each of the records to be
loaded returns the new status for all key figures and characteristics. The values in BI are overwritten (Targets: DSO and Master Data)
Time stamp u2013 Using timestamp we can run delta multiple times per day but we need to use the safety lower limit and safety upper limit with minimum of 5 minutes.
As you specified, the DS is based on VIEW (of two tables, with one containing date and other does not).
Kindly check the above lines and verify, if the view (primary key) could be used to determine the Delta for your DS.
Also let us the if any standard SAP tables used in creating VIEW and if so, what is the size of the DS load every day?
Thanks.
Nazeer

2LIS_11_VAITM delta extraction missing line items

Group,
I'm having a bit of troubles with the 2LIS_11_VAITM extractor. We've been using this extractor for some time now to do daily delta loads and it seems to work fine 99% of the time, but recently we noticed a few orders here and there from the last 7 months that were missing line items. If a full repair load is done now on these orders, we are able to extract the missing line items. This seems to suggest that for some reason the R3 delta job is not processing these line items or not picking up changes to these line items when they occur. I've found a few notes that seem to apply, but wanted to know if anyone else had this problem before.
This extractor feeds into a custom ODS, but no records should be dropped since there are only straight mappings in the update rules and transfer rules and no start routines used.
Thanks for any help offered!

Hi,
I feel it would be better to check first for these records in PSA table. If the records are there in PSA but not there in ODS . Check the value for the field 0STORNO(ROCANCEL) in all those records.
IF the field ROCANCEL does not has value R or D , then you can think about REPAIR request.
For few more information on REPAIR search the forum.
With rgds,
Anil Kumar Sharma .P

Issues with 0PP_C03 delta loads

Hi,
I loaded the data from 2LIS_04_P_ARBPL & 0PP_WCCP to 0PP_C03. Initialization of the data load went fine. Did the delta loads to BI and observed that I am not getting any of the Key figure data in the cube. All the values are showing as Zero.
When I observed the in the PSA table and in the RSA3 , I observed that for every order 2 entries got created, One is with +ve values and another with u2013ve. So at the end while updating to cube its nullifying the values. Because of this reason I am not able to view the latest data which is updated as Deltas.
I am not sure what settings I missed. Could some one please help me to fix this issue.
Thanks & Regards,
Shanthi.

Thanks Francisco Milan and Shilpa for the links. Itu2019s very useful. But still I didnu2019t able to find the cause of the issue.
My data source 2LIS_04_P_ARBPL is of ABR type and the update mode for KF is Summation. In the data source level, I am getting the values with before & after image (same entries one with +ve & another with u2013ve) and as I am using the u201CSummation as my update type for KF its getting nullified.
Because of this reason I could not able to get the values in my report. Could any one pls help me on this as I am reaching the go-live date. I need to address this issue immediately. Thanks for all your inputs.
Regards,
Shanthi.

Delta load of customer from R/3 (ECC5.0) to CRM5.0

We have done an initial load of customers from ECC to CRM (R3AS). A change is done on a customer in ECC. I expect the changes to be reflected in CRM as a delta load. I do not see the changes. What am I missing?
All responses are appreciated and will be rewarded.

Hi Mani,
Here are some clues on how to proceed with processing of incomplete or failed BP deltas:
First of all you have to note that during the initial download, no delta download can occur. In particular, no delta download of customers occurs if the initial download of materials occurs at the same time. This is because the material download depends on the customer download.
During the delta download, the CRM system uses the inbound queues R3AD_CUSTOME<nnnnnnnnnn> where <nnnnnnnnnn> corresponds to the customer number in the R/3 system. If an error occurs during the download, the inbound queue for this customer is stopped. You can see the error messages in the flow trace. For the delta download, you have the option to use Transaction CRMM_BUPA_MAP for the error analysis. If you enter the customer and press Enter here, you can display the business partner number for a customer and all open BDocs (that is, those which contain errors or are being processed). To do this, you only have to click the 'Queues and BDocs during download' pushbutton. The system issues an overview of the queue and the open BDocs for this customer and in particular, you can 'look into' the BDoc. As a result, you return to the flow trace and you can display the error messages which occured as described above. During the delta download, you have the option to send the same BDoc again. This is useful if you can simply solve the problem by correcting Customizing in the CRM system. To do this, you simply click the corresponding icon in the flow trace (currently, this is the second icon from the left).
If you have to correct the error in the R/3 system, you have to delete the existing BDoc since it cannot be processed further. As a result, the inbound queue in the CRM system is released again. In this case, you are recommended to delete all existing open BDocs and to make the changes in the R/3 system.
If inconsistencies occur between the R/3 system and the CRM system, you can start a request for the customer. To do this, click the 'Get customer from the R/3 system' pushbutton. This starts a request which uses the inbound queue R3AR_CUSTOMER. Process possible errors as during an initial download.
If you still have problems and don't know how to fix, please post more specific information from the BDoc queue, such as what error message you are getting. It helps us better identify the problem.
Regards,
Rahul
PS. Please award points if it helps!
PPS. For future reference: this info was found in note 362621: Error drng data exchange customer<->business partner

Urgent: Problems in Delta load

Hi BW Gurus/Experts,
I am new to BW and My requirement is to load deltas from CRM to BW,I have initialized deltas and after some days(appx. around 3days) there was changes in the records so I have created infopackage and tried to load deltas but i cannot do that i donot know what might be the reason when i check in monitor the status of the request is yellow with 0 from 0 records eventhough there are records which i check in RSA7. I have seen some previous posts according to some gurus suggestion I have activated the transfer structure and replicated datasources and loaded deltas again but it didnot helped me.I even tried by init load without data transfer and than i have created another infopackage for delta load that too it didnot helped me. Would anyone please suggest me some of the steps and brief explaination on them I need to follow for the following queries:
1) If I need to load deltas after 4 to 5 days of Init load.
2) If I need to load deltas again after 5 to 6 days of deltas load.
When I load deltas after init or delta load after some days by init load without data transfer and loaded deltas than the status of the request is green in monitor but with 0 from 0 records. would anyone put some light on it. I appreciate it in advance.
Thanks a lot
Regards
Reddy

Hi AK,
1) As mentioned that you have activiated the transfer structure and replicated data source..I guess it should be other way ..first you have replicate the datasource and activate the transfer structure but though TS gets activate by normal ..Its good if you activate TS through the program RS_TRANSTRU_ACTIVATE_ALL ..give TS name and activate then try to load the data.
2) There are some possible reasons when IDOC get hangs such as missing free dialog process in the target system
a)IDOC hang in status 64 for tRFC with immediate( Check note:555229)
b)Request hang because IDOCS are not processed (Check note: 561880)
c)RFC resource check returns incorrect result (Check note:311930)
3)Check entries in delta queue (RSA7) see also note 380078.
4)Its also better to use Diagnosis tools delta queue monitor qRFC t.code :SMQ1 in source system see also note 444261.
I hope the above information will help you.
Thanks n Regards
Sreedhar

Delta Documents missing

Hi Experts,
I have been loading daily deltas from ERP to ODS and then to cube datasouce 2lis_13_VDITM but users found that some of the billing doc missing already deltas are upload from ODS to Cubes and we cant delete the data . the data is huge . is there any way that we can upload the missing documents .
Thanks

Hi,
Yes correct, make sure you load Full repair and not Full.
Full repair can be said as a Full with selections. But the main use or advantage of Full repair load is that it wont affect
delta loads in the system. If you load a full to a target with deltas running you again will have to initialize them for
deltas to continue. But if you do full repair it wont affect deltas.
This is normally done we when we lose some data or there is data mismatch between source system and BW.
Check the OSS Note 739863 'Repairing data in BW' for all the details.
Refer.
Repair full request
Re: Repair full request
Steps to perform repair full request
Repair bad data and subsequent data targets with
delta update
/people/aaron.wang3/blog/2007/04/11/repair-bad-data-and-subsequent-data-targets-with-delta-update
Setup tables
Setup tables hold historical data. Setup tables are based on the concept of Cluster tables means the data will be stored in a big table in database layer and it can be viewed in multiple smaller tables in application layer.
Before doing Full or Init we have to do statistical setup. When we run statistical setup tables will be filled with the data,
normally historical data, the data goes from database tables to Setup table. If you run the full or Init in BW then the data
will be extracted from the setup tables. If you run the Delta then it will fetch from the delta queue. We use setup tables
while we are doing Repair full request also. Repair full is nothing but extraction the historical data without disturbing the
delta loads.
Before running Statistical setup its good practice to delete setup tables contents to avoid data redundancy.
The reason of using Set up table is that the SAP doesn't permit the extraction structure tables to access the database tables directly like. Rather than getting the data directly from the source tables (EKPO, MARC, VBRP, VBRK), the data is stored in Set up tables, which you can use for update to BW. After that all transaction data is posted to the delta queues in the source system. After a successful full upload you can delete the setup tables.
Only after this step (initialization) any modification will be available as delta, following the schema explained before. In
OLTP (R/3) the info packages retrieve data from the setup tables (and no postings have to be in the meanwhile, otherwise there would be some data loss!), which are assigned to the extract structures.
You fill these tables using special setup transactions in OLTP (OLI*BW).
For each extract structure, one setup table with the name of the extract structure and 'SETUP' as a suffix exists.
for sales order setup tables will be like this
for header : mc11va0hdrsetup
for item level : mc11va0itmsetup
for schedule line : mc11va0sclsetup
u can view the data of setup tables in se11 or se16.
Check this blogs from Roberto for Logistics Extraction:
/people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146
/people/sap.user72/blog/2004/12/23/logistic-cockpit-delta-mechanism--episode-two-v3-update-when-some-problems-can-occur
/people/sap.user72/blog/2005/01/19/logistic-cockpit-delta-mechanism--episode-three-the-new-update-methods
/people/sap.user72/blog/2005/02/14/logistic-cockpit--when-you-need-more--first-option-enhance-it
/people/sap.user72/blog/2005/04/19/logistic-cockpit-a-new-deal-overshadowed-by-the-old-fashioned-lis
These blogs will explain what, why and when of setup tables .
Hope this helps.
Thanks,
JituK

Delta load missing

Similar Messages

Maybe you are looking for