Delta loading issue

Hello,
I created a specific datasource based on a standard table in which there is a "changed date" field.
I used this field to create a delta loading for BW. Unfortunately, a change has been made yesterday after the delta loading and today the delta doesn't load this entry.
Is it possible to change the current status of the relevant field in order to restart the delta from the day before yesterday or should I suppress the data and launch a new init ?
Thanks for help.
Regards,
Bertrand

The date of the previous load is stored in the table ROOSGENDLM. You can modify the date with the transaction SE16.
Regards,
Fred
Edited by: FCI on Apr 8, 2009 10:08 AM

Similar Messages

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.

Delta load issue in COPA

Hi All
We are using COPA datasources and daily delta loads will goingon from source system R/3 without any issues.
last day the delta load from source system was failed due to some basis problem( non availability of WP) and we deleted that bad request in the DSO and then repeated the failed IP in the process chain,then the delta load was succesful but 0 records has been updated.
So we are missing that delta records,I guess this is due to the time stamp set in the source system.
In which table does this timestamp exists and what is the procedure inorder to solve this issue
How do I need to solve this type of issues.
Please let us know .,
Regards
Shankar

Hi Shankar........
I think u hav'nt make the QM status red.......when a delta load will fail............always make the the QM status red before repeating the load...........it will set back the QM status.........and when u will try to repeat the load.....system will ask for a repeat delta...........and a repeat delta will pick all the failed records along with the new records(if any).......
I think u should do reinit............ie.......
1)Delete the init flag
2) Fill the set up table with selection.........did u know which values r missed........any selection criteria..like date.......
3) Then do Full repair
4) then delta....
If u don't know the selection..............then u hav to load data for a selective range.........check ur DSO.....if the Update mode is Overwritten........then no probs.........otherwise there may be duplication of records.........then u hav to do selective deleteion........
Hope this helps......
Regards,
Debjani..........

Master data delta load issue

Hi Expert,
We have recently enhanced a Master Data object with 3 fields. These fields are directly mapped from a DSO. When the delta load is done, these 3 fields are not getting the data, while a full(selective) load gets the data and the 3 fields get populated. What can be the reason for this?
Thanks,
Anupama

Hi,
Then if data already updated to info object through full load, again if you run delta dtp for the same its not fetch any records, so after full load, initiliaze the delta dtp, In DTP in exectue tab you will select processing mode as select option : No data transfer delta status in source is : fetched, aftet that you can run your regular deltas. it will work.
Regards,
satya.

Delta load Issue in the R3 generic datasource

Hi All,
We are using a generic extractor which will be extracting from the R3 system through Delta update. Yesterday, the load has taken almost thrice the amount of time when compared to the previous loads and we found that the number of creation/changed records i.e. the delta records that are need to be picked up by the extractor are also quite normal. We were not facing any issue on the load before.
The job has taken more time while fetching the records from the table "RSOORMPC". We have also checked with the basis team and they confirmed that system performance is not slow during that period. Also, there is no dump or log created in the system for this issue.
Could you please give your views on this issue why this has occurred??
For your information, the repeat delta which we had triggered has picked up only 0 records.
Your suggestions will be verymuch helpful for us as it has happened in the production environment. If you need anymore information please give me a shout.
Regards,
Yokesh Kumar.

Sateesh,
The extractor is function module based only. Load did not even entered the code which we had written. While calling a standard program itself, the load got stuck.
Regards,
Yokesh Kumar.

"Waiting time until status incorrect" - BI delta loading issue

Hi All,
We have a delta master data load, which happens daily. It runs almost for 40 minutes, there is no extraction happening for first 31-32 minutes and the thousands of records are picked in the subsequent few minutes.
After 30 minutes, the load is momentarity turning into status 'RED' and the load is picking up as usual. I could see there is a setting for the load in RSMO transaction itself, in Settings tab --> Waiting Time Until Status Incorrect. In this settings time set is 30 minutes.
Now can some help me in changing this setting time value or speed up the loading (i.e. to pick before 30 minutes). This has been happening for the past one week. Any help is highly appreciable, as this job fails unnecessarily in monitoring tool.
Regards,
Shashidhar.

Hi Shashidhar,
I had a performance issue for an infopackage loading from Generic datasource. The reason was identified as Index not being not created for the source table.
These threads may be useful for your issue.
RSC2_QOUT_CONFIRM_DATA Long Running/Delayed Delta Infopackage
n LUWs to be deleted with function module RSC2_QOUT_CONFIRM_DATA
http://www.sapfans.com/forums/viewtopic.php?f=16&t=237705
Regards,
Hari.

Delta load issue from DSO to DSO

Hi Experts,
We have a scenario where we need to load the delta from DSO to DSO. when we are running delta from DataSource to DSO it is picking some around 100 records, but when we are running delta from DSO to DSO it is picking some around 80000 records. But in previous deltas it has taken as equivalent to staging DSO only, but in today delta it has different. Could you please give some pointers, why it is happening like this.
Thanks
Konda Reddy

Hi,
There are no routines in DSO's and transformations also we have not changed, the thing is that in previous deltas it has taken same recoreds as in the staging layer. In between we have done one full load from DSO to DSO, is this makes difference in picking up the delta. And again we done delta then it has taken aroung 80000 records which includes the full load records also. could you please provide some pointers.
Regards,
Konda Reddy

Issue in the Delta load using RDA

Hi All,
I am facing an issue while trying to load delta using RDA from R/3 source system.
Following are the steps followed:
1. Created a realtime Generic Datasource with timestamp as delta specific field and replicated it to BI.
2. First I have created the Infopackage(Initialization with data transfer) and loaded upto PSA.
3. Created a standard DTP to load till DSO and activated the data.
4. Then created a realtime delta infopackage and assigned it to a Daemon.
5. Converted the standard DTP to realtime DTP and assigned the same to the Daemon.
6. Started the Daemon, giving an interval of 5 minutes.
In the first time, Initialization with data transfer is taking the records correctly. But when I run Daemon for taking delta records, its taking all the records again, i.e. both the previously uploaded historical data and the delta records).
Also after the first delta run, the request status in the Daemon monitor, for both Infopackage and DTP changes to red and Daemon stops automatically.
Can anyone please help me to solve these issues.
Thanks & Regards,
Salini.

Salini S wrote:
In the first time, Initialization with data transfer is taking the records correctly. But when I run Daemon for taking delta records, its taking all the records again, i.e. both the previously uploaded historical data and the delta records). .
If I understand you correctly you Initially did a full load. Yes? Well next you need to do intialise & after that delta.
The reason is that if you will select delta initialisation & initialisation without data transfer- it means delta queue is initialised now & next time when you will do delta load it will pick only changed records
If you will select delta initialisation & initialisation with data transfer- It means delta queue is initialised & it will pick records in the same load.
As you know your targets will receive the changed records from the delta queue.
Salini S wrote:
Also after the first delta run, the request status in the Daemon monitor, for both Infopackage and DTP changes to red and Daemon stops automatically.
I take it the infopackage has run successfully? Did you check? If it has and the error is on the DTP then i suggest the following.
At runtime, erroneous data records are written to an error stack if the error handling for the data transfer process is activated. You use the error stack to update the data to the target destination once the error is resolved.
To resolve the error, in the monitor for the data transfer process, you can navigate to the PSA maintenance by choosing Error Stack in the toolbar, and display and edit erroneous records in the
error stack.
I suggest you create an error DTP for an active data transfer process on the Update tab page (If key fields of the error stack for DataStore objects are overwrite On the Extraction tab page under Semantic Groups, define the key fields for the error stack.) The error DTP uses the full update mode to extract data from the error stack (in this case, the source of the DTP) and transfer
it to the target that you have already defined in the data transfer process. Once the data records have been successfully updated, they are deleted from the error stack. If there are any erroneous data records, they are written to the error stack again in a new error DTP request.
As I'm sure you know when a DTP request is deleted, the corresponding data records are also deleted from the error stack.
I hope the above helps you.

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

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.

Issue with delta load from R/3 to BW

Hi frnds,
There is a standarded D.S 2LIS_05_ITEM in R/3. Evereday We extraceted data from R/3 to BW based on this standard Data Source with delta load.There are two fields ZX and ZY in BW ,some times the data haven't extracted for this 2 fields in BW with the delta update.But some times this 2 fields properly extracted in to BW with the same delta update.
Why is it happen like this ? Please give some inputs on this.
Regards,
Satya.

Hello,
if its a standard field then its getting populated in correct way.
if its custom field then you need to analyze the records for which its getting populated and for one which its not.
Quite possible that some cutomization in CMOD results in this behaviour.
Also,check underlying tables to see the correct values.
Regards
Ajeet

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

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

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

No initial load of Customers, Material and delta load of Sales Orders.

Hi Experts,
I am facing a very troublesome issue. I am not able to setup the Middleware portion for initial and delta loads. I read a lot of documents and corrected a lot of things. finally, the connectivity is done with R/3 and CRM. Initial load of all objects is successful (as per Best PRactices guide). Customizing load is successful.
But after now I have these open issues for which I am unable to find any answers (am really exhausted!!):
- Customer_main load, it was succesful, but no BP's of R/3 are available.
- Material, it failed in SMW01, SMQ2, the errors are:
Mat. for Initial Download: Function table not supported
EAN xxxxxxxxxxxxxxxxxx does not correspond to the GTIN format and cannot be transferred
EAN yyyyyyyyyyyyyyyyyy does not correspond to the GTIN format and cannot be transferred
Plant xx is not assigned to a business partner
- Sales order, it shows green bdoc, but error segments says "No upload to R/3" and the order does not flow to R/3.
We had our system setup 3 years back for data transfer and Middleware. But few things changed and connectivity stopped. I did all that again now, but am not yet successful. Any inputs will be greatly appreciated.
Thanks,
-Pat

Hi Ashvin,
The error messages in SMW01 for MAterial initial load is :
     Mat. for Initial Download: Function table not supported
     EAN 123456789000562 does not correspond to the GTIN format and cannot be transferred
     EAN 900033056531434 does not correspond to the GTIN format and cannot be transferred
     Plant 21 is not assigned to a business partner
I have done the DNL_PLANT load successfully. Why then the plant error?
Some of the messages for BP:
Messages for business partner 1331:
No classification is assigned to business partner 1331
For another,
     Partner 00001872(469206A60E5F61C6E10000009F70045E): the following errors occurred
     City Atlanta does not exist in country US
     Time zone EST_NA does not exist
     You are not allowed to enter a tax jurisdiction code for country US
     Validation error occurred: Module CRM_BUPA_MAIN_VAL, BDoc type BUPA_MAIN.
Now, the time zone EST is assigned by default in R/3. Where do I change that? I do not want to change time zones as this may have other impacts. Maybe CRM I cna change this, not for sure in R/3. City check has been deactivated in R/3 and CRM, still the error.
Till these 2 are not solved, I cannot go into the Sales order loads.
Any ideas will be greatly appreciated.
Thanks,
-Pat

Delta loading issue

Similar Messages

Maybe you are looking for