Safety intervals for delta for different datasources

Hi, Please help me to find the Safety intervals for delta for different datasources in RSA7 or in table ROOSPRMSC. Like for FI_GL_10 I know it is 60 mins but where do I see this. I checked Note 380078, Please let me know this specific answer to the question asap.
Thanks
Soniya Kapoor

Hi
Go to RSA2->give your datasource name ->setting up GEN delta
It shows you whts the safety interval setting.
Hope it helps
Thanks for points assigned

Similar Messages

Not getting the data for delta for 0ASSET_ATTR_TEXT in RSA3

Hi All
In RSA3, I am not able to extract the delta for the datasource ASSET_ATTR_TEXT. But when it is on full update then i am gettign the records, when i changed to "D" it is giving me the error 'Errors occurred during the extraction' and the error messege says
"Errors occurred during the extraction
Message no. RJ012
Diagnosis
During the extraction phase an error occurred for the extractor. An exception, 'error_passed_to_mess_handler' was triggered.
System Response
A more precise description of the error can be found in the log.
Procedure
Check the function module or the call from the extractor check program
Kindly provide some inputs on the same
Regards
Abhi

hi Siggi,
I have checked Datasource in the ROOSOURCE Table for this datasource the DELTA IS - AIE. And do did the Init from the BW i got 8210 recods.Then i executed the Delta Pack. there was an error happend.
But When i loaded Delta i got the error as :
Diagnosis
         Not all the initialization requests have been completed yet for this
    DataSource, or there may be an incorrect initialization request.
System response
No delta requests can be processed whilst there is an initialization
    request that has not been completed.
Procedure                                                     Wait until the initialization request has finished, or delete the entry
    for the incorrect initialization request from the corresponding display
    in the Scheduler.
Regards
Abhi

Procedure for delta intialization of datasource 2LIS_11_VAHDR

Hello experts,
I need some help with the delta intialization for the datasrouces 2LIS_11_VAHDR and 2LIS_11_VAITM. I'm working on SAP R/3 4.7C and extracting data to BI 3.5. I'll be grateful if someone could send some links where I can find the step by step procedure.
Thanks and regards,
Sumit

Sumit
You could also go through these weblogs on LO 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/04/19/logistic-cockpit-a-new-deal-overshadowed-by-the-old-fashioned-lis
/people/sap.user72/blog/2005/02/14/logistic-cockpit--when-you-need-more--first-option-enhance-it
Thnaks
Sa

How to use EXIT_SAPLEINS_001 for delta with 2LIS_02_SCL datasource ?

Hi,
I'm facing a problem using 2LIS_02_SCL: the field MCEKET-WAMNG is not populated during delta extraction (it is populated correctly when I fill setup tables).
I have been told that I should use customer exit EXIT_SAPLEINS_001 in order to fill MCEKET-WAMNG at event ML u2013 delivery, because 2LIS_02_SCL does not takes this event into account (only MA, MB, MC and MD which can be verified in LBWE Events), this field is not passed to BW in delta.
I need help to implement this solution.
An example with ABAP code will appreciated.
M.B.

Hi,
May helpful to you
EXIT_SAPLRSAP_001 vs EXIT_SAPLEINS_001
EXIT_SAPLEINS_001
Regards,
Suman

Using different datasources and different view objects.. (ADF 11g)

In our application we have the need for using two different datasource (an old version and a new verision) - but not at the same time.
Isn't it possible to base a viewobject on top of two sub viewobjects and run time decide which sub viewobject to use?
If possible - could someone please show some code examples?
Thanks...

Hi,
no, not exactly. You can have polymorphic views, but the use case is a different. The transaction is maintained by the AM, so if you want to connect to different data sources then you have to connect to them when starting the application, For this you can configure it for dynamic JDBC connect
Frank

How to change the Safety Intervals for standard Content datasources

Go to RSA2->give your datasource name ->setting up GEN delta
It shows you whts the safety interval setting.
<b>
How to change the Safety Intervals for standard Content datasources since when I go to RSA2 edit and change options are always greyed out. let me know if there is any other transaction code or table to do this.</b>
Thanks
Soniya Kapoor

Hi Soniya,
1) try RSA6.....also RSA8 for additional info.
2) useful link:
http://help.sap.com/saphelp_nw04/helpdata/en/d0/4cc138944cfa06e10000000a11405a/content.htm
Good luck, BB

Need to help to Initialise delta for CRM datasources

Hi all,
I am currently working on CRM Extraction. I am using the datasource 0CRM_SERVICE_CONFIRM_I datasource. I have loaded the data to ODS.I am trying run Init delta without data transfer.
While running, i am getting the error message as
-> Activation of M records from DataStore object 0CRM_CNFI terminated
-> Full updates already available in DSO 0CRM_CNFI; Cannot update init./delta
Can u please provide me how to enable delta for CRM Datasources.
Thanks & regards,
Jelina.

Hi @yad1 ,
I have sent you issue to be escalated and do check your private message when a HP employee reaches out to you.
Best,
Russ
I worked for HP.

I want to make a delta for datasource of 0hr_pa_1 and 0hr_pa_0

i want to make a delta for datasource of 0hr_pa_1 and 0hr_pa_0,because our transction data are not maitain on time, so the full update which depend on the time will lost many data, could you give me some suggustion pls? thanks
allon

Hi,
Please search for the related threds in SDN, I think the following links will help you.
Re: Any other option to accomplish Delta load mechanism?
http://help.sap.com/saphelp_sem320bw/helpdata/en/29/02b43947f80c74e10000000a114084/frameset.htm
Thanks
reddy

No delta for Datasource

In RSA3, I am not able to extract the delta for the datasource 0GM_DO05. But when it is on full update then i am gettign the records, when i changed to "D" it is giving me the error 'Errors occurred during the extraction' and the error messege says
"Errors occurred during the extraction
Message no. RJ012
I have checked Datasource in the ROOSOURCE Table for this datasource the DELTA IS - ADD
It works ok in DEV and QA but my PROD is where the problem is.
Can anyone help?

Dinesh / SA
I have been doing full loads with no problems but when I try to initialise with no data transfer, thats when my problem starts.
So what I did was to go to the source system and changed the extractor checker to D or S update modes. The error occurs in RSA6. I will try to run the extraction again in debug mode an dsee if there is anything I can find.
I have given the datasource as well.
Any other ideas?
Message was edited by: jimi ogun

Need for locking system for delta initialization (BW-R3-LO)

Hello all,
Could someone please help me with the following,
Please be kind, don't get impatient for the lengthy post
1. Do we need to lock the system (or posting-free the system) to do early delta initialization or not? If yes, please explain me how that work?
2. Someone somewhere mentioned that early delta initialization is not preferable compared to normal delta initialization, even though early delta initialization is advantageous. Why is that so?
3. Imagine, while scheduling Queued Delta Init or un-serialized V3 delta Init, if I choose certain end date and time (say, 10pm, 12-31-2007) for the records, then all the records till that point would be loaded to setup tables and all the records after that point of time will be moved to extraction queue or update tables. My question is, if this is true why would we ever need to lock the system during setup tables filling?
    If you say the records after that particular time and date (10pm, 12-31-2007) will not be collected in extraction queue and update tables, why don't we do the following
             a). say, I do full load with end date and time (10pm 12-31-2007)
             b). Next, I do delta init with start date and time (10pm 12-31-2007) (this time I lock the postings)
         If we do this way, we can actually reduce the down time of the system. Is my conclusion right?
         If you say it's not practicable as some transactions' saving time differs from time stamp and some transactions' delta is even measured by pointer.......if this is the case we can use Delta offset. What do you say about this?
4. How this scenario differs to early delta initialization?
Your responses would be greatly appreciated
Thank you

Hello,
1
>
curious maven wrote:
> Do we need to lock the system (or posting-free the system) to do early delta initialization or not? If yes, please explain me how that work?
No,you don't need to lock the Source System which is the advantage of Early Delta Init.
With early delta initialization, you have the option of writing the data into the delta queue or into the delta tables for the application during the initialization request in the source system. This means that you are able to execute the initialization of the delta process (the init request), without having to stop the posting of data in the source system. The option of executing an early delta initialization is only available if the DataSource extractor called in the source system with this data request supports this.
[Business Information Warehouse 3.0 Overview Presentation|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/9a0e9990-0201-0010-629b-dc2735cb9c81]
2
>
curious maven wrote:
> 2. Someone somewhere mentioned that early delta initialization is not preferable compared to normal delta initialization, even though early delta initialization is advantageous. Why is that so?
Early delta is not supported by all the extractors. See Lo Extraction
3
>
curious maven wrote:
Imagine, while scheduling Queued Delta Init or un-serialized V3 delta Init, if I choose certain end date and time (say, 10pm, 12-31-2007) for the records, then all the records till that point would be loaded to setup tables and all the records after that point of time will be moved to extraction queue or update tables. My question is, if this is true why would we ever need to lock the system during setup tables filling?
>
>     If you say the records after that particular time and date (10pm, 12-31-2007) will not be collected in extraction queue and update tables, why don't we do the following
>
>              a). say, I do full load with end date and time (10pm 12-31-2007)
>              b). Next, I do delta init with start date and time (10pm 12-31-2007) (this time I lock the postings)
>
>          If we do this way, we can actually reduce the down time of the system. Is my conclusion right?
>
>          If you say it's not practicable as some transactions' saving time differs from time stamp and some transactions' delta is even measured by pointer.......if this is the case we can use Delta offset. What do you say about this?
This is applicable to Generic Delta where you can set the Safety Interval (Upper Limit and lower Limit) for the extractor based on ALE Pointer, or Time Stamp or Calendar day.
If you excute a extractor with early delta init, during the setup table fill, the delta records will be directly written to the delta queue. The delta management handles these functionality.
[How to Create Generic Delta|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33]
[SAP BI Generic Extraction Using a Function Module|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a0f46157-e1c4-2910-27aa-e3f4a9c8df33]
4
>
curious maven wrote:
How this scenario differs to early delta initialization?
If you do a Init without Early Delta init, then the user cannot post new documents and you have to either schedule in the weekend or request for a Source System downtime.
But if you use Early delta , then you don't need the source system down time and the user can post new records during the init, which will be written to the delta queue directly.
[How to Minimize Effects of Planned Downtime (NW7.0)|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/901c5703-f197-2910-e290-a2851d1bf3bb]
[How to Minimize Downtime for Delta Initialization (NW2004)|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/5d51aa90-0201-0010-749e-d6b993c7a0d6]
Thanks
Chandran

Delta Enabled Business Content Extractors and Safety Intervals

Is there a transaction/table from where I can check the safety intervals of Business Content extractors for example 2LIS_13_VDITM. If I created a Z copy of an extractor is there a way of changing this value? Thanks

There are two fundamentally different extractor types:
1. Que, which is updated at time of transaction
2. Delta based on incremental field on transaction
LIS extractors are type 1 and CO extractors and generic data sources are type 2.
Type 1 is more advanced as it handles the change directly. Type 1 handles complex data scenarios where type 2 is better for simple scenarios. Learn more i BW350

Delta for generic master data extractor

Hello,
Is it not possible to load deltas for a generic master data extractor?
I have created a generic extractor on R/3 table MEAN (EAN number assigned to material). I have also performed the init run which worked fine, but no deltas are being loaded.
Why is this?
Best regards,
Fredrik

hi,
its possible
how to generic delta
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33
SAFETY DELTA
check these links
oss note 368739
Symptom
For the setup of summarization levels and summarization data in the Profitability Analysis a 'Safety delta' of half an hour is used. This means, the system only includes records which exist half hour already. You want to reduce this delta in order to get more current data in reporting.
Additional key words
Summarization levels, summarization data, safety delta, time stamp
Cause and prerequisites
The reason for the duration of these safety deltas are possible differences in the clocks on different application servers. If the delta is selected too short, when updating the summarization levels/data, records may not be taken into account. In particular the Account-based Profitability Analysis depends on the sufficient length of the delta, so that update processes which take longer do not cause inconsistencies. For the Costing-based Profitability Analysis a lock is set. If not active update processes exist, it fails and the update terminates.
Solution
The attached source code correction is not part of the standard system. With this change the safety delta is set from 30 to 5 minutes. You should only implement this, if exclusively the Costing-based Profitability Analysis is active in your system. If you also use Account-based Profitability Analysis we do not recommend the change for the above-mentioned reasons.
Generic delta safty intervals
oss note 392876
safety interval
0FI_GL_4 Safety Delta
Genric delta fro table
check this thread which already discussed about this topic
Generic Extractor - Delta
Shreya

Selection Criteria in Infopackge for enhanced field of DATASOURCE in R/3

Hi All,
My client requirement is Data has to be loaded on company wise .. means the respective responsible person only carryon loading person as per his profile(Authorisation)load has to be happen...this is one requirement,
one more is (whether in this scenario can we go for Delta)
we enhanced the Datasource with new field in R/3 and when we are trying to make it selction condition in infopackage we are not getting filtering as per that ..
could u or anyone who knows through a light on this..
Thanks in advance
BRB

Hi BRB,
regarding your question about selection field I gave you an answer in one of yours previous post !
Just some considerations about your authorizations requirements.
If I right understood, you want to build a scenario in which there are different persons that, manually, have to access on the system to perform a data loading restricted to a particular company code (so, person A could load only data from company A, person B from company B and so on...)
I think you can obtain this (also with a dedicated infopackages per person), but if you want to manage a delta (your second question) just remember that you can perform different init (with different selections), but the delta channel will be only one and only one will be your delta request management..so, your previous profiling will no longer make sense...
Hope it helps.
Bye,
Roberto

Generic function module for delta - which FM ?

Hi all,
I want to create a custom generic datasource in R3 which uses a function module for delta extraction. This is straight forward for full extract (copy FM RSAX_BIW_GET_DATA_SIMPLE - I already did this and have a full extraction working to BW). However I need to extract delta - and the above function module does not have example code for that (I have seen some forum posts that it 'can' be used - but this looks like a pseudo get around where the delta field name is passed in I_T_SELECT).
FM RSVD_BW_GET_DELTA_DATA seems to be an example code of a FM which can allow delta (i.e. manually codes how to fill date/time stamp information). However when I code this and try test in RSA3 it seems to try to populate the delta selection field before calling my function module! I need it to call my function and allow the function to specifiy the date criteria.
Can anyone help with an example of how this should best be done ?
Or can it only be done in a pseudo form using 'RSAX_BIW_GET_DATA_SIMPLE' example FM.
Note: I have setup the RSO2 datasource to allow delta.
Also - I have spent several hours searching the forum - but please answer with a link if you think it does answer exactly this problem.
Thanks for any help
Martin

Hi again,
Have had a few requests for the code I used - I created a new custom function copied from 'RSAX_BIW_GET_DATA_SIMPLE'. AEDAT has been set as the delta date for this data source in transaction RSO2.
Main sample code is -
1. Code to receive selection criteria and store in internal ranges -
FUNCTION zbw_sodetail_get_detail.
""Global interface:
*"   IMPORTING
*"       VALUE(I_REQUNR) TYPE SRSC_S_IF_SIMPLE-REQUNR
*"       VALUE(I_DSOURCE) TYPE SRSC_S_IF_SIMPLE-DSOURCE
*"       VALUE(I_MAXSIZE) TYPE SRSC_S_IF_SIMPLE-MAXSIZE
*"       VALUE(I_INITFLAG) TYPE SRSC_S_IF_SIMPLE-INITFLAG
*"       VALUE(I_READ_ONLY) TYPE SRSC_S_IF_SIMPLE-READONLY
*"       TABLES
*"              I_T_SELECT TYPE SRSC_S_IF_SIMPLE-T_SELECT OPTIONAL
*"              I_T_FIELDS TYPE SRSC_S_IF_SIMPLE-T_FIELDS OPTIONAL
*"              E_T_DATA STRUCTURE ZBW_SODETAIL OPTIONAL
*--- Sales order item create date
   LOOP AT i_t_select INTO l_s_select WHERE fieldnm = 'ERDAT'.
      MOVE-CORRESPONDING l_s_select TO r_erdat.
      APPEND r_erdat.
   ENDLOOP.
*--- Sales order item change date - DELTA only - auto filled before
   this function is called.
   C (Initialise Delta) - Low = blank, High = today - safety limit
   D (Delta) - low = , High =   .       *from roosgendlm
   LOOP AT i_t_select INTO l_s_select WHERE fieldnm = 'AEDAT'.
      MOVE-CORRESPONDING l_s_select TO r_aedat.
      APPEND r_aedat.
   ENDLOOP.
2. Code to use selection criteria to get initial or delta. Note that for delta the delta date field to be used is automatically populated with the date of the last delta run (from table roosgendlm) -
   SELECT VBAK~KNUMV
          VBAPVBELN VBAPPOSNR VBAPMATNR VBAPARKTX VBAP~SPART
          VBAPWERKS VBAPERDAT VBAPAEDAT VBAPNETWR VBAP~WAERK
          VBAPABGRU VBAPZPROMISE VBAP~CUOBJ
          VBEP~EDATU
      INTO CORRESPONDING FIELDS OF TABLE ZBW_SODETAIL_ITAB
      FROM VBAK JOIN VBAP ON VBAKVBELN = VBAPVBELN
                JOIN VBEP ON VBAPVBELN = VBEPVBELN
                         AND VBAPPOSNR = VBEPPOSNR
   WHERE VBAP~VBELN IN R_VBELN        "Order number
     AND VBAP~POSNR IN R_POSNR        "Order item number
     AND VBAP~ERDAT IN R_ERDAT        "Order item date created
    AND ( VBAP~ERDAT IN R_AEDAT OR   "Created date in      Delta range
              VBAP~AEDAT IN R_AEDAT OR   "Order item change    Delta range
              VBAK~AEDAT IN R_AEDAT ).   "Order header change Delta range
Note that if the data source is called in initial or full extract mode the delta change date (aedat) will automatically be blank.
I have been using this successfully.
I hope this helps
Martin.

Error in RSA3 for Delta

Hi,
The data load for 0FI_AR_10 (payment history) delta load is fetching zero records after we did EPH4 (Golden Tax) Upgrade to the ECC 6.0 system.
When we check in RSA3 for Delta it is throwing error as -> Message no. RJ012
There is no other info. The data load looks successful in BW but with zero records.
Please suggest.
We are facing some what similar issue for 0CUSTOMER_ATTR as in the Ticket:
[0CUSTOMER data from Unicode R/3 to Non-Unocode BW Error|0CUSTOMER data from Unicode R/3 to Non-Unocode BW Error]
Thanks,
Joe

Hi
Go to RSO2 and give the data source name 0FI_AR_10 -- there you ahve extractor BWFI3D_GET_FIAR_CM_PH(functional module) ---> reset the function and module and reactivate it
mostely the problem will be solved.
incase if it is not solved the reason might be as below
These datasources have extraction type as F1 and the function module used is BWFI3D_GET_FIAR_CM_PH( Tcode: RSA2).
When we go through the code of the Function module, there is a Case statement with update mode which is written in such a way that when the update mode is full it throws one type of error and when the extraction mode is others(which includes init, delta etc) it throws another type of error.
This update mode field in the Function module will take the value when we run the Infopackage and we will get an error saying: 'Update mode when others is not supported by extraction API'(this error occurs as the update mode takes the value of c and executes 'when other' case).
In extractor checker(RSA3), the default value taken by the update mode will be F (since we are not executing any infopackage and the update mode value will be F by default).
So ultimately when that function module is executes it will throw an error no matter what type of load(delta or full) we select.The error will occur but it will be handled differently when you run in RSA3 and when you run the Infopackage.
so i would suggest you to raise a note to SAP on the same
and i will post if I find any solution going in future on the same.
Very intresting Question
pleasure answering
Santosh

Safety intervals for delta for different datasources

Similar Messages

Maybe you are looking for