Delta in Genric datasource

Hi Experts,
How to test delta for generic datasource.
will the delta goto lbwq for generic datasource or straight away rsa7?
Regards,
Anand

Hi,
For generic data source, delta will be seen in RSA7 not LBWQ.
Generic datasource to have a delta capability, your table or view should have either time or date field.
Thanks
Srikanth

Similar Messages

How to catch the delta of generic datasource created on table EBAN?

Hi Guru,
I am facing a problem about the delta of generic datasource i created on table EBAN.
when I convert a PR into PO, this PR was created several month ago, this PR will not be caught into delta package.
how to get this PR again after it was converted into a PO?
many thanks.
brgds/steve

hi,
If you have any fields(calday,timestamp,nemric pointer) in your table , using this fields any one we can enable delta.otherwise one option is there but your table is small valoum of datas.
first data load(full) r3 to bw side cube,then using open hub service download data from cube to any file (excel ,csv) then r3 side create one table using that flat file, then load download file to r3 new table using (LSMW - tcode r3 side).
now compare your genric extroction table and new table using ABAP coding , then you have any new record or changed find update new table first then BW side .
using this type we can enable delta for genric extrocation.
regards,
sundar.

Delta in custom datasource - Purchase

Hi,
I am creating a custom datasource on purchasing using EKBE and EKET tables.
can any one tell , how to capture the delta of this datasource using eg., PO number, time stamp etc.,
Thanks
Sridhar

Hi Sridhar,
In order to create a custom data source follow:
1. Create a view on both the table.
2.go to rso2
3.select transactional data source ( if data fetched is transactional ).
3 . give view name
4. click on generic delta.
5. give delta specific field :
( if yuo have chosen timestamp or calendar day then it is required that your view should have these fields.)
or else give any other field according to whic you want the delta to be generated.
6.select after images ( applies to DSO )
or select additive (applies to dso and infocube )
save ->again save
your custom data source is created.
reward points if helpful
Manish

Activation of genric datasource warning

hi all,
activation of genric datasource in rsa6 gives warning error.
and the not getting activated . my DS extracts from MARA table.
the warning "The even-numbered length of the DEC field MHDHB can lead to problems"
thank u

Hello Rakesh,
Its a bug. If you can change the lenght of the field MHDHB to an next odd number this will be solved.
See the note
Note 1118115 - Error RSMDS 024 for selection of amount field w/ even length
Note 603453 for Reference (its from IS)
Thanks
Chandran

Problem to initialize delta queue of datasource from CRM 7.0.

Hi all,
I've some problem to initialize delta queue of datasource from CRM 7.0. After initialize the Init in BW, the delta queue was created but after the user changed data, this changed didn't populated into delta queue.
I tried the steps below but without any success. Anybody know how can I correct this issue?
Suggestion 3: Please check the following.
Please Check if the services have been generated in transaction GNRWB.
If they are not active(not marked 'X' before their names) then activate
the services following the steps here.
Go to transaction GNRWB
Select BUS_TRANS_MSG
Select (on the right, the services) : BWA_DELTA3, BWA_FILL, BWA_queue
Press Generate.
Also check for the following:
1. The delta should have been initialized successfully.
2. Confirm that all Bdocs of type BUS_TRANS_MSG
are processed with success in SMW01.
3. If there are queues in SMQ1 with erroneous status then activate
these queues.
In Transaction SMQ1 if there are Queues existing with
names beginning with CRM_BWAn (n is number) then
activate these queues in the same transaction.
4.a)If required activate the datasource
Go to transaction BWA5 > select the required datasource and
activate.
4 b) The Delta may not be active ,activate the delta in BWA7 by
selecting the name of the datsource and pressing the candle icon for
'activate delta'.
5. In BW system
Go to transaction RSA1 > modeling > infosources > select the
infosource > right mouse click on the selected
infosource > choose option replicate datasource
Activate the infosource.
6. Go to the scheduler for the infosource > select delta in the
update >choose the option PSA only (in the Processing tab)

Hi Peter,
Thank you for your answer.
But we need to find out what the reason for this import error is.
Our customer will not be very pleased to see that all IDocs from CRM system cannot be found in the IDOC folder.
IDX2 import of metadata is no issue.
We were successful for standard and customer Idocs here.
Additional information:
We are already importing Idocs from a SAP ECC 6.0 system into PI in another SWCV
successfully. So this is a CRM system specific issue in our environment.
Regards
Dirk
Edited by: Meinhard Dirk on Aug 27, 2010 10:30 AM

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.

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

Getting Error while creating Genric Datasource

Hi,
I was try to create genric extracter where i was getting error
While creating view genric extracter where i am getting error "Entry A ZV_ZFRT does not exist in DD02L - check your entry".
My requirement is need to create extracter which is getting populated from three modules like SD,MM,FI/CO.From these three module i am using several tables and some of the tables don't have relation btween these tables as like foreign key and refrence key.
Which extracter i need to create as given scenario?
Does view will fullfill with my requirement or any other extracter.
Please some one can help me in this scenario.
Answer would be great appreciate.

Hi,
Rather than writing a program write a function module. Create a structure and include all the necessary fields in the structure. Then in the function module write the logic to extract the values for those fields. While creating the datasource specify the function module and structure name.
Refer this link:
/people/siegfried.szameitat/blog/2005/09/29/generic-extraction-via-function-module
Hope this helps.
PB

How to deal with delete record in generic delta of generic datasource

Hi,
Anyone can give me suggestion about the delete record in generic delta of generic data. I need extract data with a generic datasource and hope deleted record in datasource also can be "delete" in next delta extraction. I do a test with generic delta. It seem that the delete record can not be updated in ODS. but updated record can be updated in next delta extraction.
How dose BW generic delta deal with the deleted record with generic delta mechanisim? Or how can I use generic delta mechanisim to realize that BW "delete" the deleted record of source system in ODS with delta extraction?
Thanks in advance!
Billy

Delete is not supported in delta mechanism of generic delta extractor. You will need to add a workaround for that.
- Capture the deleted records somewhere (maybe enhance the txn deleting the record so the key is written to a Z table). Take these records to BW and manipulate the recordmode to affect deletion of corresponding record from ODS.
- If your generic delta is based on FM, and if the 'delete' is captured in change document tables, add the logic to check change document tables whether any records are deleted, and if yes, send those to BW with appropriate recordmode to achieve deletion.

Processing overdue error during delta extraction from datasource 0CO_OM_CCA

Hi,
I'm getting "Processing overdue error" in BW while extracting delta from datasource 0CO_OM_CCA_9. all other extraction jobs from R3 -> BW are successful. Even Delta init on this datasource is successful & problem is only with delta package.
I appreciate if someone could provide information based on the following error details on this issue.
here are the extraction steps we followed.
Full load of fiscal years 2006 & 2007 Into transactional cube.
load budget data into transactional cube.
compression of the cube with "0 elimination"
Delta Initialization with fiscal period selections 1/2008 to 12/9999
all the above steps were successful.
and when delta package is scheduled, we are getting following errors.
BW system log
BW Monitoring job is turning red with following message.
Technical : Processing is overdue
Processing Step : Call to BW
Sending packages from OLTP to BW lead to errors
Diagnosis
No IDocs could be sent to the SAP BW using RFC.
System response
There are IDocs in the source system ALE outbox that did not arrive in
the ALE inbox of the SAP BW.
Further analysis:
Check the TRFC log.
You can get to this log using the wizard or the menu path "Environment -> Transact. RFC -> In source system".
Removing errors:
If the TRFC is incorrect, check whether the source system is completely
connected to the SAP BW. Check especially the authorizations of the
background user in the source system.
R3 Job Log
Even after BW job turns to red, R3 job continues to run for 2 hours and
eventually gets cancelled with an ABAP dump & here is the log.
Job
started
Step 001 started (program SBIE0001, variant &0000000110473, user ID
BWREMOTE) DATASOURCE = 0CO_OM_CCA_9
Current Values for Selected Profile Parameters
abap/heap_area_nondia.........2000000000 *
abap/heap_area_total..........2000000000 *
abap/heaplimit................20000000 *
zcsa/installed_languages......EDJIM13 *
zcsa/system_language..........E *
ztta/max_memreq_MB...........2047 *
ztta/roll_area................6500000 *
ztta/roll_extension...........2000000000 *
ABAP/4 processor: SYSTEM_CANCELED
Job cancelled
Thanks,
Hari Immadi
http://immadi.com
SEM BW Analyst

Hi Hari,
We were recently having similar problems with the delta for CCA_9. And activating index 4 on COEP resolved our issues.
Yes, by default there is a 2 hour safety interval for the CCA_9 DataSource. You could run this extractor hourly but at the time of extraction you will only be pulling postings through 2 hours prior to extraction time. This can be changed for testing purposes but SAP strongly discourages changing this interval in a production environment. SAP does provide an alternative described in OSS note 553561. You may check out this note to see if it would work for your scenario.
Regards,
Todd

Dump while pulling delta with 2LIS_05_QVUDN datasource

Hell All,
We are getting dump (attached) in delta extraction to BW using 2LIS_05_QVUDN datasource. We have analyzed it byt we dont find a good clue.
Please advice,
Runtime Errors         RAISE_EXCEPTION
Date and Time          17.09.2009 05:18:14
|Short text                                                                                |
|    Exception condition "DB_CONNECTION_ERROR" raised.                                             |
|What happened?                                                                                |
|    The current ABAP/4 program encountered an unexpected                                          |
|    situation.                                                                                |
|What can you do?                                                                                |
|    Note down which actions and inputs caused the error.                                          |
|                                                                                |
|                                                                                |
|    To process the problem further, contact you SAP system                                        |
|    administrator.                                                                                |
|                                                                                |
|    Using Transaction ST22 for ABAP Dump Analysis, you can look                                   |
|    at and manage termination messages, and you can also                                          |
|    keep them for a long time.                                                                    |
|Error analysis                                                                                |
|    A RAISE statement in the program "SAPLSTD9" raised the exception                              |
|    condition "DB_CONNECTION_ERROR".                                                              |
|    Since the exception was not intercepted by a superior                                         |
|    program, processing was terminated.                                                           |
|                                                                                |
|    Short description of exception condition:                                                     |
|                                                                                |
|                                                                                |
|    For detailed documentation of the exception condition, use                                    |
|    Transaction SE37 (Function Library). You can take the called                                  |
|    function module from the display of active calls.                                             |
|    -                                                                                |
|How to correct the error                                                                          |
|                                                                                |
|    If the error occures in a non-modified SAP program, you may be able to                        |
|    find an interim solution in an SAP Note.                                                      |
|    If you have access to SAP Notes, carry out a search with the following                        |
|    keywords:                                                                                |
|                                                                                |
|    "RAISE_EXCEPTION" " "                                                                         |
|    "SAPLSTD9" or "LSTD9U09"                                                                      |
|    "DB_CONNECT"                                                                                |
|                                                                                |
|    or                                                                                |
|                                                                                |
|    "SAPLSTD9" "DB_CONNECTION_ERROR"                                                              |
|                                                                                |
|    or                                                                                |
|                                                                                |
|    "RSORACOL " "DB_CONNECTION_ERROR"                                                             |
|    If you cannot solve the problem yourself and want to send an error                            |
|    notification to SAP, include the following information:                                       |
|                                                                                |
|    1. The description of the current problem (short dump)                                        |
|                                                                                |
|       To save the description, choose "System->List->Save->Local File                            |
|    (Unconverted)".                                                                               |
|                                                                                |
|    2. Corresponding system log                                                                   |
|                                                                                |
|       Display the system log by calling transaction SM21.                                        |
|       Restrict the time interval to 10 minutes before and five minutes                           |
|    after the short dump. Then choose "System->List->Save->Local File                             |
|    (Unconverted)".                                                                               |
|                                                                                |
|    3. If the problem occurs in a problem of your own or a modified SAP                           |
|    program: The source code of the program                                                       |
|       In the editor, choose "Utilities->More                                                     |
|    Utilities->Upload/Download->Download".                                                        |
|                                                                                |
|    4. Details about the conditions under which the error occurred or which                       |
|    actions and input led to the error.                                                           |
|                                                                                |
|
|Information on where terminated                                                                   |
|    Termination occurred in the ABAP program "SAPLSTD9" - in "DB_CONNECT".                        |
|    The main program was "RSORACOL ".                                                             |
|                                                                                |
|    In the source code you have the termination point in line 80                                  |
|    of the (Include) program "LSTD9U09".                                                          |
|    The program "SAPLSTD9" was started as a background job.                                       |
|    Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR"                                               |
|    Job Initiator.. "DDIC"                                                                        |
|    Job Number..... 03512600                                                                      |
|Source Code Extract                                                                               |
|Line |SourceCde                                                                                |
                                                                                |
|   59|*&---------------------------------------------------------------------*                    |
|   60|*&      Form db_connect                                                                    |
|   61|*&---------------------------------------------------------------------*                    |
|   62|*       text                                                                                |
|   63|*----------------------------------------------------------------------*                    |
|   64|*      -->CON_NAME   text                                                                   |
|   65|*----------------------------------------------------------------------*                    |
|   66|FORM db_connect USING con_name.                                                             |
|   67| CHECK con_name <> 'DEFAULT'.                                                              |
|   68| EXEC SQL.                                                                                |
|   69|    set connection :con_name                                                                |
|   70| ENDEXEC.                                                                                |
|   71| IF sy-subrc <> 0.                                                                         |
|   72|    EXEC SQL.                                                                               |
|   73|      connect to :con_name                                                                  |
|   74|    ENDEXEC.                                                                                |
|   75|    IF sy-subrc <> 0.                                                                       |
|   76|      EXEC SQL.                                                                             |
|   77|        connect to :con_name as :con_name                                                   |
|   78|      ENDEXEC.                                                                              |
|   79|      IF sy-subrc <> 0.                                                                     |
|>>>>>|        RAISE DB_CONNECTION_ERROR.                                                          |
|   81|        EXIT.                                                                               |
|   82|      ENDIF.                                                                                |
|   83|    ENDIF.                                                                                |
|   84| ENDIF.                                                                                |
|   85|ENDFORM.                    "db_connect                                                     |
|   86|                                                                                |
|   87|*&---------------------------------------------------------------------*                    |
|   88|*&      Form db_disconnect                                                                 |
|   89|*&---------------------------------------------------------------------*                    |
|   90|*       text                                                                                |
|   91|*----------------------------------------------------------------------*                    |
|   92|*      -->CON_NAME   text                                                                   |
|   93|*----------------------------------------------------------------------*                    |
|   94|FORM db_disconnect USING con_name.                                                          |
|   95| CHECK con_name <> 'DEFAULT'.                                                              |
|   96| EXEC SQL.                                                                                |
|   97|    set connection default                                                                  |
|   98| ENDEXEC.                                                                                |
|   99|ENDFORM.                    "db_disconnect                                                  |

Hey when u getting this dump ??
after clicking on info pkg or some where else ??
Tell me ..
Ankit

Delta in Generic datasources.

For the generic datasource. I have to run Delta multiple times per day. In this case I hope that, TIMESTAMP is the suitable option to run delta. Here, to set up TIMESTAMP, I have to select the field name for Delta, based on that field name the delta will work and pick the records into BW side.I have 2 fields DATE and TIME to set up delta. I have given field DATE for delta.
For example.The data in the source system is
      IC            DATE                    TIME
      XX           22/03/2009           09:30:41
I will run delta on 22/03/2009, 10 AM , then the above record will go to BW successfully.
At 11 AM one more record will be added into the source sytem on the same date 22/03/2009. Now the data in the source system is
IC            DATE                    TIME
XX           22/03/2009           09:30:41
YY           22/03/2009           11:00:00
Again, at 11:30, I will run delta to pick the 2nd record. Here my doubt is, will that 2nd record be picked into the BW?. I doubt that, as we have set up delta based on the field DATE, Will the 2nd record will be picked into the BW side or not?. If the 2nd record will not be picked into the BW side.
How can I achieve this. But, I need to run multiple times per day and need all records.
Please let me know if you dont understand.

Hi,
I understand your requirement, as you are using date as delta specific field you would not get another record created on the same day. To solve it you have two options,
1) Field with date and time combination. - e.g 20090317164909.
2) Or can you use time field as delta field.
Any of above can solve your problem.
Hope this helps.
Regards,
Viren
Edited by: Viren Devi on Mar 22, 2009 9:11 PM

Delta in generic datasource

Hi all,
In case of standard datasource, the document posted in R/3 is written to BW delta queue. Generic datasources don't support delta update directly but support generic delta. Can you pleasce clarify what exactly happend in case of generic datasoure.
Thanks in advnce,
Zak.

based on timestamp or values of certain field generic datasource shall manage delta. Check this please - Generic Delta-
http://help.sap.com/saphelp_nw70/helpdata/en/37/4f3ca8b672a34082ab3085d3c22145/content.htm

Delta enable generic datasource

hellow sir ..
im workin on SAP BW 3.5
i'm creating the generic datasource ,, so my confusion is how to make it Delta enabled because The check box for DElta is Greyed...
so wat;s the diference between delta box checked and unchecked..
how to make that grey area checked..
thanks and regards

u r talkin about Generic Delta Tab.. where 3 option s are there,.. - YES
so wat options i shud go for.. so that it enables Delta upload at BW side. - This will not enable delta loading at BI side it will extract delta records from R/3 only, for activation BW delta you have to create a delta infopackage that will extract the delta records from R/3 to BI.
and there are 2 more options in Radio button
- Filed name : Here u specified based on which field ur delta records wil be picked up, like change date field (field name : ERDAT) then specify the name of field, as its a date field so choose the Radio button CAled day. If it had been a time stamp filed u have choosen then Timestamp radio butoon.
1) New status for change Records
2)Additive Delta..
For above read F1 help (that is very clearly explains this)
and what is the DElta check box which is there in Selection and Hide field Tab,, which comes after Saving the First Screen of RS02 ( DATASOURCE : Customer Version Edit ) - This box will become checked when u maitain any delta field in Generic delta tab. It indicates wether the datasource is delta enabled or not
Hope this is clear now.

Delta load for datasource 0RT_PA_TRAN_CONTROL

Hi SAPers,
we are implementing POS DM here and was able to successfully initialize the delta queue for 0RT_PA_TRAN_CONTROL but when i try to schedule a delta request i get the following error in the monitor:
Error in a formula function (routine ROUTINE_0034 ), record 1
This did not occur in DEV and is only happening since transported across to QA.
Any responses would be greatly appreciated.
Regards,
John

Hi,
They are datasources from the BW System itself. Goto RSA1 -> BW Source System -> Under the Application Component 0RT_PA you would find the datasources.
Bye
Dinesh

Delta in Genric datasource

Similar Messages

Maybe you are looking for