Delta Load - BI Statictics 0 records

Hi All,
I have loaded Init successfully for all the infoprovider related to BI Statistics. But the delta loads are bringing 0 records then I checked in RSA7 and found no records.
Please help me how to resolve this issue.
Regards,

Hi Vikas,
I will tell you how I did the setting for the statistics -
1. Allowed all the Infoprovider for statistics collection (RSA1-Tools-Setting BI Statistics---Selected Infoprovider changed Defalt setting to X mode).
2. Init load for all Statistics cubes.
While running Delta No records are updated.

Similar Messages

Master Delta Load - Error "38 Duplicate records found"

Hi Guys,
In one of our delta uploads for a Master data we are getting error "38 Duplicate records found". I checked the PSA data but there were no duplicate records in that.
Once the data upload fails I manually update the failed packet and it goes fine.
Please any one have solution for this.

Hi
You can see the check box in the Processing tab page. Make a tick mark for the check box Ignore Duplicate Data Records indicator . When multiple data records that have the same key are transferred, the last data record in the request is updated to BI. Any other data records in the request with the same key are ignored.
Help says that:
To maintain consistency, ignoring duplicate data records is only possible if the data is updated serially. A serial update is when data is first updated into the PSA then, after it has been successfully written to the PSA, it is updated into the master data or text tables of the InfoObject.
If a DataSource transfers potentially duplicate data records or if you manually set the Ignore Duplicate Data Records indicator, the PSA Only update type is automatically selected in the scheduler.
hope it clears ur doubt, otherwise let me know.
u can see the same in my previous thread
Re: duplicate records found while loading master data(very urgent)
Regards
Kiran

Issues with Delta Loads.

Hi All,
I hope you don’t mind to provide a suggestion about the delta load of Purchase Orders.
There was a request from Procurement team and they complaint that the data is not looking right.
For example: for a given purchase order the exemption flag is displayed as ADE.
Before change:
Purchase Doc Number
Puchase Exemption flag
90002106
ADE
They want this to be displayed as:
After Change :
Purchase Doc Number
Puchase Exemption flag
90002106
So ABAPER has included the logic in ECC Functional Module to populate the Extract Structure for Data Source to display above result. But the overnight run didn’t pick up the changes to above record in BW. The loads are delta loads.
So my Question is:
· This load for the Infocube Purchase Orders is delta load. Does change to Function Module will pick up the changes to old records as well? I mean if we are doing delta load does the old records gets changed and updated in CUBE or should I delete the data from all the PSA and Infocube and run the load into CUBE to pick up the changes. Am bit worried about deleting the data from Infocube as it may have history data (because of delta load). Total records in cube are 800000 records.
· Another question does the process chain trigger the function module to load the data into Extract Structure of data source in ECC (am bit confused about this process in ECC)?
Please suggest me how can I capture those changed records?
Any help would be much appreciated. Please let me know if you need more info.
Thanks in advance
Sandeep

Hi Sandeep,
I am little confused from your post. You are using 2lis_02_SCL or the generic FM datasource?.
Also it looks like new custom field added in your client. I never saw any purchase exemption flag even though i am working in purchasing flow for last 2 years.
W.r.t purchasing , deletion flag will be there which will come from EKPO and have the values S or L ( Deleted or Blocked).
You can block or delete a PO aslong as GR was not happened. Other wise you can do it. So use the EKPO-LOEKZ for your use.
Regards,
Rajesh

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

0 records in master data delta loads.

We have activated delta on 0CUSTOMER_ATTR and verified the queue is active in RSA7. However the delta load is not fetching any records. A full load, however, does. I have deleted and reactivated the delta init multiple times with no success
The infopakage error monitoring status has the following messages
No new data since the last delta update
Diagnosis
The data request was a delta update, meaning, the data basis in the
source system has not changed since the last update.
System response
Info IDoc received with status 8.
Procedure
Check the data basis in the source system.
Thanks in advance.
D

hi ok first check what Ajay said the BD61 if it is activated in R3.
After that go to roosgen fill in the name of the DS 0custmer_attr select the line with the R3 from which you want to extract data.
Copy the message type.
Then after you have made the change (update or creation) go to table cdhdr and cdpos to get the change doc object, table name and field name.
After that go to bd 52 paste your message type and add the entry for in your case for the phone number in communication tab
chge doc ADRESSE table : ADR2 field name : TEL_NUMBER
Launch the delta it should work.
In fact when you go to bd52 you will see the fields that are entered for the fields to be taken into consideration when an update is made (they are mainly based on the chge doc obj DEBI) so if you need more fields add them in function of your needs and the info you get in cdhdr and cdpost when you do changes. You can do this only manually so take care of repeating these steps in QA and in prod.
Hope this could help you to solve your issue.
regards
Boujema

Duplcate records in the delta load

BW experts,
I am getting the following errors when doing a delta load from 2LIS_02_ITM
into OBBP_CON, 0BBP_INV, 0BBP_PO, 0SRCT_DS1, 0SR_VEGUID.
The delta loads show a green light for all the targets except 0SR_VEGUID and
the error message is
3 Duplicate record found. 2295 records used in /BIO/XSR_VEGUID
3 Duplicate record found. 2295 records used in /BIO/PSR_VEGUID
I tried to check the contents of the both /BIO/XSR_VEGUID and
/BIO/PSR_VEGUID but i get a message saying the tables are not active in the
dictionary.
However, i can view the data in the Info object OSR_VEGUID.
How can i resolve this issue ?
Any help will be appreciated.
Many Thanks

Kiran,
Welcome to SDN,
P and X tables are created only if you have 1. Time dependent Navigational Attributes ( X Table)
2. Time Independent Master Data Attributes.. ( P table)
Otherwise the tables will not be created.
Arun
What table do you see in the header when you see the data for the infoobject ? on the creen - do you see something like
/bi0/XX0SR_VEGUID where XX xould be some characters ... Ideally P table should be viewable...

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

Question for delta loading, why can not update existing record in cube

Hi, Gurus,
I load data from a flat file into one infocube with delta loading option, and in the related datasource, i chose 'additive delta' option.
However after delta initial and delta update, when I checked cube content, I found that there are 2 records with the same characteristic value (just like duplicated key), and my expectation is to sum key figure with the same characteristic. Who can help me on that?
BTW: when I check delta queue, why there is not any queue?

Hi,
In uploading of flat file , If you are able to capture the changes to the previously loaded records, Then you can follow the additve delta. So it decreases the time of uploading .Only changed or new records will be uploaded every time.
If you are not able capture the changes in flat file ,Every time you have to do full upload ,Before this delete the contents of Infocube. (Assuming there is no ODS B/W Infocube and Flat file).
With rgds,
Anil Kumar Sharma. P

About delta loading for master data attribute

Hi all,
We have a master data attribute loading failed which is a delta loading. I have to fix this problem but I have two questions:
1. how can I find the those delta requests because I need to delete all these failed requests first, am I right ? Master data is not like cube or ods that we can find the requests in Manage, for master data how can we find them ?
2. Could you please let me know the detailed procedures to perform this delta loading again ?
Thanks a lot

Hi...
1. how can I find the those delta requests because I need to delete all these failed requests first, am I right ? Master data is not like cube or ods that we can find the requests in Manage, for master data how can we find them ?
Look.....for master data.....no need to delete request from the target..........just make the status red.......and repeat the load.....But problem is that master data sometimes does'nt support Repeat delta..........if u repeat......then load will again fail with Update mode R.........in that case u hav to do re-init.......
1) delete the init flag.......(In the IP scheduler >> in the top Scheduler tab >> Initialization option for source system)
2) Init with data transfer(if failed load picks some records)..........otherwise .....init without data transfer.....if the last delta failed picking 0 records.......
3) then Delta.......
2. Could you please let me know the detailed procedures to perform this delta loading again ?
1) Make the QM status red.........to set back the init pointer.......
2) Repeat the load.....
After that.........if again load failed with Update mode R.....
1) delete the init flag.......
2) Init with data transfer(if failed load picks some records)..........otherwise init without data transfer.....
3) then Delta.......
Regards,
Debjani.....

Compare data in R/3 with data in a BW Cube after the daily delta loads

Hi Friends,
How can I compare data in R/3 with data in a BW Cube after the daily delta loads? Are there any standard procedures for checking them or matching the number of records?

Hi Sunil,
If you want to check the records daily instead of checking the data in R/3 manually ......
You can try this...
If you have staging DSO(level 1) that means whatever data is in source system load it to Staging DSO without any routines or any modifications.
Now load this DSO data to Cube or DSO(level 2) as per your requirement with routines etc.
Now Staging DSO contains Source system data.
Now the level 2 Cube or DSO contains BW data with some modifications.
Now create a Multiprovider based on level 1 and level 2 data targets.
Now create a report on which keyfigures you want to test the data.
In Multiprovider there is a field called 0infoprovider in data packet dimension.
you can drag this infoprovider to the columns and restict your keyfigures with level 1 and level 2 data targets.
In the first column you can see the level 1 DSO data ( source system data),in the 2nd column you can see the BW data.
Now create a formula which gives the diffrence b/n level 1 and level2.
that is R/3 data - BW data.
If the diffrence is zero both R/3 and BW data are same.
if the diffrence is not eqaul to zero check whether any routine is there or not.

What is the diffrence between full load and delta load in DTP

hI ,
I am trying to load the data into CUBE from another cube using DTP ..
There are 2 DTPS ..
1: DTP with full load
2: DTP with DELTA load ..
what is the diffrence betwen thse two in DTP ...
Please can somebody help me

1: DTP with full load - will update all the requests in PSA/source to the target,
2: DTP with DELTA load - will update only new requests to the datatarget
The system doesnt distinguish new records on the basis of changed records, rather by the request. Thats the reason you have datamart status to indicate if the request has been loaded to further datatargets.

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.

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.
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 ?
Check if this note helps
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

Error in delta loading from a planning cube

hi all,
I am using a delta load from one planning cube to another.When the changed records are of a magnitude of 100 then it is successful but when the records are of magnitude of 100000 then it stays yellow with no data records sent and eventually fails.the packet size is 20000.
any help is appreciated.

Hello Ajay,
Have you checked that your Request is closed in the planning cube? FM RSAPO_CLOSE_TRANS_REQUEST will do it
It is a customizing issue to tell the infopackage to end "green" when it has no data.
Transaction Spro ==> SAP Netweaver ==> SAP Business Information Warehouse ==> Automated Processes ==> Monitor Settings ==> Set Traffic Light Color. There you have to set the Traffic light on green if no data is available in the system.
Hope that helps
best regards
Yannick

Delta loading and Process chain BI

Hi experts,
Two Issues.
1)As i am loading FI data into dso through a process chain which includes Start process>Delta infopackage(which gets data upto psa)>Delta dtp-->Datastore activation.
But infopackage is picking up deltas but DTP is picking up all the previous records plus deltas.
100 records -- 1st day throught Intialization of Delta with Data Transfer
2 delta records -- 2nd day
But DTP is picking up 102 Records on the 2nd Day, which means it is also picking the old records as well.
The DSO must have just 102 records but it is having 202 records.
2) A process chain in running daily as scheduled , but I rescheduled with new scheduling options without deactivating the Process chain.
My Question is
Will the Process chain run for the OLD and the New Schedule or
Is it going to run for new schedule or old one?
or
will I face any Problem because I did not deactivate and made changes to the Change.
Please help me in this matter.
Thanks in advance.
Bhadri.

First query:
I believe that u have used FUll update type DTP is instead of the Delta DTP.. Please cross check the Update mode of the DTP once.
To resolve this issue, delete the total content of the DSO as u have Init and delta loads in PSA. And then using the Delta DTP of the Process chain, load the data. It will extract the total cotent what ever is there in PSA, and later the same DTP will act as the Delta type and will pick the data from the New request of the PSA.
Second Query:
Its always suggested to deschedule the process chain before changing the schedule timings. When ever u do this type of scheduling, just check how many number of JObs available in Schedule mode, if u can see more than one, then delete the older one and keep the new one as it is.
But I always suggest you to deschedule the process chain and reschedule PC with the new timings and then activate the same.
Thanks
Assign points if this helps

Replicating data once again to CRM after initial load fails for few records

My question (to put it simply):
We performed an initial load for customers and some records error out in CRM due to invalid data in R/3. How do we get the data into CRM after fixing the errors in R/3?
Detailed information:
This is a follow up question to the one posted here.
Can we turn off email validation during BP replication ?
We are doing an initial load of customers from R/3 to CRM, and those customers with invalid email address in R/3 error out and show up in SMW01 as having an invalid email address.
If we decide to fix the email address errors on R/3, these customers should then be replicated to CRM automatically, right? (since the deltas for customers are already active) The delta replication takes place, but, then we get this error message "Business Partner with GUID 'XXXX...' does not exist".
We ran the program ZREPAIR_CRMKUNNR provided by SAP to clear out any inconsistent data in the intermediate tables CRMKUNNR and CRM_BUT_CUSTNO, and then tried the delta load again. It still didn't seem to go through.
Any ideas how to resolve this issue?
Thanks in advance.
Max

Subramaniyan/Frederic,
We already performed an initial load of customers from R/3 to CRM. We had 30,330 records in R/3 and 30,300 of them have come over to CRM in the initial load. The remaining 30 show BDOC errors due to invalid email address.
I checked the delta load (R3AC4) and it is active for customers. Any changes I make for customers already in CRM come through successfully. When I make changes to customers with an invalid email address, the delta gets triggered and data come through to CRM, and I get the BDOC error "BP with GUID XXX... does not exist"
When I do a request load for that specific customer, it stays in "Wait" state forever in "Monitor Requests"
No, the DIMA did not help Frederic. I did follow the same steps you had mentioned in the other thread, but it just doesn't seem to run. I am going to open an OSS message with SAP for it. I'll update the other thread.
Thanks,
Max

Delta Load - BI Statictics 0 records

Similar Messages

Maybe you are looking for