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.

Similar Messages

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

"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 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..........

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 Error in the Data Extraction

Hi BI Guru`s,
The issue is with the extractor 2LIS_13_VDKON (Pricing conditions), The regular delta till 22.07.2010 has run successfully, But on 23.07.2010 the delta got failed with the error message " Data Package 58 : arrived in BW ; Processing : Processing not yet finished, entry 70 still missi" for one of the Datapacket. We have repeated the load even though we got the same error message, Since the client is retailer we will be having the delta records of 200 million ( approx. 23369612) in a day. Since because of this error we could't load any of the delta from that day onwards.
Need Help on this:
1. How to get the old delta
2. How to re-initialize the process for delta. (Pls keep it in mind the volume of the records).
Thanks in Advance,
Venkat

Hi,
Here we need decrease the datapacket size as well as prallel proceesing .
than we need to load the historical data through dalta repetition
hope..helpful for you!
Regards!
Malli.

BI Load issue in the transformation/DTP after SP 17

Hello,
After SP 17 applied in our BI system, we are having load issue in one particular transformation/DTP.
See below the errors:
u2022 Messages for 101 data records saved; request is red acc. to
configuration
u2022 Thee is no active nametab in the system, although an active ABAP/4
Dictionary object was expected. Reactivate the ABAP/4 Dictionary object.
Also I have activated the DSO, transformation and DTP. Also I went to SE14 and try to adjust my DSO, SE11 and activate the table but still having the issue.
Can someone advise me on how to resolve this issue?
Thanks a lot.
Cesar

Hi,
Do the following: In BI, run transaction SE38 >> RSDG_CUBE_ACTIVATE to recreate the Metadata information
for the Info-provider.
Then execute another program via SE38: RSDD_RSTMPLWIDTP_GEN_ALL
See Note 1161940 and 1152453 for more details.
Regards,

Errors occurred during the extraction - Generic datasource

Hi,
We had created a Generic datasource based on Infoset. While executing RSA3 for that datasource, 'Errors occurred during the extraction' message is getting displayed.
In the Error log, it says, "Field catalog does not agree with the fields of the functional area".
Please let us know on how to resolve this error asap.
Thanks in advance!!!!

hi haripriya,
just go to RSO2.
Enter the name of your datsource.
then Click on Delete.
Then Again Recreate your data source with correct structure and definition.
then activate it and replicate it in BW.
hope this will help u.
thanks

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 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

Delta load not picking the changes to Custom Fields in 0CRM_QUOTA_ORDER_I

We have enhanced the structure of CRM datasource 0CRM_QUOTA_ORDER_I for some additional fields that are held on the quotation. These are being successfully extracted when the quotation is being created. We have been running with this exctract for some time but we have been made aware that the additional fields on the append structure are not being updated when the quotation is being changed. Therefore delta changes are not being picked up making the reports incorrect.
The user exit we are using to extract the information is EXIT_SAPLRSAP_001
Does anyone know how we can enable this change so that delta changes are picked up by the extractor.
Many thanks
Gareth
Edited by: Gareth Aspinall on Jan 14, 2010 2:04 PM

Hi Gareth,
Can you please check that the custom fields were added as described in question 4 in the SAP note
692195? If yes and there is still a problem please check that the SAP note 1319891 has been applied
in your system, it is a pilot note so you will need to raise a message with SAP to get added to the pilot
note.
Best Regards,
Des Gallagher.

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

Delta loading of generic data source.

Hi,
please tell me the procedure for How to load Delta data For generic data source?

Hi
You can use the following procedue
Enabling Delta Load
Use
You must first configure and modify the DataSource to be used for delta loading in CAF and SAP BW integration and define delta-relevant attribute fields.
Prerequisites
You have launched the Maintain Generic DataSources tool of SAP BW.
Procedure
1. Configuring Generic DataSources
     1.      In the DataSource pane, choose next to the Transaction data field to select the DataSource to use for CAF and SAP BW integration and choose Change.
     2.      In the Change DataSource maintenance screen:
           a.      Set Applic. Component to BW.
            b.      Choose Save.
    3.      In the Create Object Directory Entry dialog box:
            a.      Choose Local Object to see the DataSource information.
             b.      Choose Save to return to the Change DataSource maintenance screen.
4.      Choose Generic Delta. In the Generic Delta dialog box:
            a.      Browse Field Nm. to select the delta-relevant field.
           b.      Mark the Time stamp radio button.
            c.      Mark New Status for Changed Records.
5.      In the Selection of field determining delta dialog box, select the following delta-relevant fields:
○       For the entity service DataSource, select the field corresponding to LASTCHANGEDAT.
○       For the application service DataSource, select the field corresponding to delta-relevant field specified by BW extractor method developer.
6.      In the DataSource: Customer version Edit screen, save all data.
2. Activating DataSources
       1.      Launch the SAP BW Administrator Workbench and go to Modeling.
      2.      Open the list of InfoSources and select the DataSource assignment you want.
      3.      With the secondary mouse button, choose Replicate DataSources.
      4.      Select the same object from step 3 and choose Change Transfer Rules with the secondary mouse button.
      5.      In the InfoSource Change screen, choose with the quick info text Activate.
Initializing Delta Load
Prerequisites
You have configured the DataSource for the delta loading process. For more information, see Enabling Delta Load.
Procedure
1. Starting Delta Initialization
     1.      Launch the SAP BW Administrator Workbench and go to Modeling.
     2.      From the Modeling pane, click InfoSource to populate the InfoSource pane and select the InfoPackage you created for the InfoSource in, for example, Example of Data Extraction.
      3.      From the Update tab page, activate the Initialize Delta Process indicator.
      4.      To define parameters to be used for the delta load process, go to the Data Selection tab page and define relevant parameters.
      5.      In the Schedule tab page, choose Start to begin delta initialization.
If you defined parameters to be used in delta load (step 4 above), use PSA in the modeling component of Administrator Workbench to view the request results.
     6.      To check when delta initialization is finished, go to the Maintain InfoPackage screen of the Monitor u2013 Administrator Workbench and press F6.
2. Monitoring Delta Initialization
     1.      Launch the BW Delta Queue Maintenance and select the DataSource in question.
     2.      Use the secondary mouse button to see the current pointer value in Generic Delta Current Status.
     3.      You can delete the delta initialization (if you want, and subsequently create a new delta initialization) in Scheduler (Maintain InfoPackage) by choosing the delta request from Initialization Options For Source System and choosing Remove.
In this screen, you can also check the status of the delta initialization request.
To see the content and results of the delta initialization request, go to PSA in the modeling component of Administrator Workbench to view the request results.
3. Running Delta Load
You can run the delta load process only after delta initialization has been completed.
     1.      Open the InfoPackage and in the Update tab page activate the Delta Update indicator.
      2.      Go to the Schedule tab page and choose Start.
*Enabling Delta Load *
Use
You must first configure and modify the DataSource to be used for delta loading in CAF and SAP BW integration and define delta-relevant attribute fields.
Prerequisites
You have launched the Maintain Generic DataSources tool of SAP BW.
Procedure
1. Configuring Generic DataSources
      1.      In the DataSource pane, choose next to the Transaction data field to select the DataSource to use for CAF and SAP BW integration and choose Change.
     2.      In the Change DataSource maintenance screen:
        a.      Set Applic. Component to BW.
        b.      Choose Save.
    3.      In the Create Object Directory Entry dialog box:
           a.      Choose Local Object to see the DataSource information.
            b.      Choose Save to return to the Change DataSource maintenance screen.
   4.      Choose Generic Delta. In the Generic Delta dialog box:
       a.      Browse Field Nm. to select the delta-relevant field.
       b.      Mark the Time stamp radio button.
       c.      Mark New Status for Changed Records.
5.      In the Selection of field determining delta dialog box, select the following delta-relevant fields:
○       For the entity service DataSource, select the field corresponding to LASTCHANGEDAT.
○       For the application service DataSource, select the field corresponding to delta-relevant field specified by BW extractor method developer.
   6.      In the DataSource: Customer version Edit screen, save all data.
2. Activating DataSources
   1.      Launch the SAP BW Administrator Workbench and go to Modeling.
   2.      Open the list of InfoSources and select the DataSource assignment you want.
3.      With the secondary mouse button, choose Replicate DataSources.
    4.      Select the same object from step 3 and choose Change Transfer Rules with the secondary mouse button.
5.      In the InfoSource Change screen, choose with the quick info text Activate.
Hope this helps
Regards
Shilpa

IDoc delta loads using the program RBDMIDOC

Hi ALL,
We are doing some delta loads for ALE-IDOC using the program RBDMIDOC and we are using the message type HRMD_A.Under this message type we have configured two diff distribution models with different infotype data.
So when we execute the program we have only one input parameter that takes the message type.based on our setup will the program send the delta loads for both the distribution models since they are using the same message type which we do not want.
How do we restrict the program to send the delta loads only for the intended distribution models even though they are using the same message type.
Thanks
Bala Duvvuri

Hi Bala,
Assuming that based on IDoc content there is some way to determine which system should be the recipient, you could do the following (requires ABAP development as indicated by Mylène):
Define a new filter object type if required via BD95.
Assign new or existing filter object to E1PLOGI segment field FILTER1 or FILTER2 via BD59
Create BAdI implementation for HRALE00OUTBOUND_IDOC and implement method FILTER_VALUES_SET to set values for FILTER1 or FILTER2
Even without the BAdI implementation you'd see the new filter value appearing in your distribution model for message type HRMD_A. However, you need the ABAP logic for filling the fields with actual values that you can utilize.
Cheers, harald

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

Delta load Issue in the R3 generic datasource

Similar Messages

Maybe you are looking for