DELTA TRIGGERING

hello experts
I have one question.
we have R3 System connected to BI 7.0 system.....when someone goes into R3 system and make some changes to data in it....I know that this will be updated by delta mechanism....how do system know that some fields are changed and how it generates delta .....I hope I explained my question in right way....
Thank you.....
BI USER

hi ,
When a some change is done in R/3 side , this changes can be captured by using delta mechanism .
If it is a std D.S , this can be handled byb 3 update methods ;
1) direct delta
2) Queued Delta
3) Unserialized V3
If it is a generic DS , then by using generic delta function we can capture the lastest changes or new records based on the following
1) Numeric pointer
2) calender day
3) time stamp
For generic delta , there will be 2 limits :
1) upper limit
2 ) Lower limit
This we can say us safety delta for generic DS
Hope this helps out
Thanks
PT

Similar Messages

Why the R3 client QTY300 would have different BI delta triggers

hi GURUS,
this is an issue with my client.how shud i revert back the mail..
Can you see why the R3 client QTY300 would have different BI delta triggers than the R3 client PRD300?
We are using standard extractor 2LIS_11_VASCL, and in test cases in QTY300, we were able to make some changes and see the results of the changes in tcode rsa3. When we try he same changes in PRD300, no changes are triggered and tcode rsa3 shows no changes.
Is there a way to see if the extractor is setup differently in QTY than PRD?
reply ASAP,plzzz

Hi,
Did you initialize your delta in PRD300?
In order to get your delta in RSA3 you must enter your target system (your BW) and change the mode to D...
Or open RSA7 and check there if you have data....
hope this helps...
Olivier.

Issue in delta

Hi Experts,
I have some problem in R/3 servers,please chek it and send me solution on my mail:-<removed>
Can you see why the R3 client QTY300 would have different BI delta
triggers than the R3 client PRD300?
We are using standard extractor 2LIS_11_VASCL, and in test cases in
QTY300, we were able to make some changes and see the results of the
changes in tcode rsa3. When we try he same changes in PRD300, no changes
are triggered and tcode rsa3 shows no changes.
The extractor has been in place in PRD for over 1 year....
As to point #2, the hide field will only affect what is sent to BI, it should not effect if a delta records gets added to the R3 delta table for said extractor
Is there a way to see if the extractor is setup differently in QTY than
PRD?
Thanks & Regards,
Muddu Reddy.

Reddy,
This is a repeat post of your last post. Your last post was moved to the BI forums. You can find it here :
Issue in R/3 Client
Since this is related to BI and not BPX , the post was moved. Please the posts in a relevant area. In case you do raise it in the BPX forums , it might have been moved. You should be able to find your post by clicking on your ID on the left hand side of the window. This was done so that the relevant people can look at your post and offer their suggestions for the same.
Arun
P.S marking this post as answered and will move the same to the BI forums. Please do not keep raising the same post in case you are not able to find it in its earlier position..

The unprocessed entires in BDCPV table

Hello, Experts
There are so many unprocessed entries of master data delta 0material_attr in BDCPV table.
What does create the unprocessed entries in BDCPV table?
What should I check that before delete the unprocessed entries?
Thank you.

Entries are written to the BDCP and BDCPS tables (BDCPV is a view on these two tables) whenever changes are done to the corresponding fields identified as delta triggering fields in the ALE Delta. All the entries will initially be in the status "UNPROCESSED" until a delta load is triggered. When the load is complete, the status is changed to "PROCESSED" which helps the system identify the new change pointers.
In your case, find out the corresponding datasources which are using these change pointers for ALE Delta and trigger a delta load to change the status to Processed. Hope this helps. As you can guess by now...if you delete unprocessed change pointers, you will lose the delta records.

Any other optin.

Can you see why the R3 client QTY300 would have different BI delta
triggers than the R3 client PRD300?
We are using standard extractor 2LIS_11_VASCL, and in test cases in
QTY300, we were able to make some changes and see the results of the
changes in tcode rsa3. When we try he same changes in PRD300, no changes
are triggered and tcode rsa3 shows no changes.
Is there a way to see if the extractor is setup differently in QTY than
PRD?

Hi,
Did you initialize your delta in PRD300?
In order to get your delta in RSA3 you must enter your target system (your BW) and change the mode to D...
Or open RSA7 and check there if you have data....
hope this helps...
Olivier.

Question regarding fields triggering delta on ECC side

Hi gurus
I wonder does any field change on ECC side triggers delta queue? If not how can I know what fields do trigger deltas?
For example I use FI_AR_4 extractor, one of the extraction structure fields comes from BSEG.SGTXT. It is long text field. Then it is being changed it doesn't impact any amounts or other key information. Will BSEG.SGTXT field change trigger the delta queue if any other field of the record wasn't changed?

But this timestamp field is posted then some fields have been changed, i guess...

Selection Criteria for Delta loads triggered using MDM_CLNT_EXTR

Hi ,
Currently we are required to load data only from two specific account groups . Therefore in the selection criteria in mdm_clnt_extr we maintian these two account groups and extract data.
However, when setting up the delta load there does not to be an option to restrcit the delta to a specify an criteria. Therefore, in our case several records from account groups which are not required are passed on to the MDM system.
Is there a way to address this requirement ?
1. There is an option to run the initial load variants at regular intervals, the problem with this is that in our case we have several variant creates as the R/3 system does not allows extraction on more that 999 records at a time. Therefore at point of time to capture the delta records , if we run all these jobs our network gets choked.
2. Run delta job, but without selection criteria it pulls out records which we don't require
Any suggestions on how this problem can be addressed are welcome ,
Thanks in advance,
Anita George

Thanks Michael !
Well, regarding hte ALE settings, we did take a look in bd64 the filters are based on objects which one of these is relevant for customer account groups ? Probably in the future we would require all data, and then is it enogh to remove the filter ?
Can a filter be maintained at the XI level , this would be good as only the required account groups are passed on to MDM . Is there any documentation on available on this ?
Regarding the Import Manager, will have to check this functionality, as it is now no matter how many times we update the map/rename /load/unload it automated imports keep failing.
Our R/3 system seems to have problem extracting more than 999 records, as we tried with different number of records and all those extraction jobs got cancelled. So, currently we are running multiple jobs for the initial load and even this is very time consuming.
Thanks & Regards,
Anita George

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

Delta Records is not getting updated in delta queus when changes done

Hi All,
In Quality system , when a user makes a change to an order's ship-to address, the changes are "triggering" a delta record into the delta tables for BI to extract. This can be seen via tcode rsa3's delta tester.
In Productionn System, when the user makes the exact same change, nothing is added to the delta table and the changes never come over to BI unless a full extract is request for the order.
Why changes not getting updated, please give your inputs.
Thanks & Regards,
Venkat Vanarasi.

Do you have your V3 update job active and running? THis job wites changes to the delta queue. Of course your datasource has to been initialized and a delta queue should be setup. You can check it in RSA7.
Regards,
Juergen

Multiple Vendors for one Purchase order in delta load

Hello,
While Extracing data from 2LIS_02_SCL we are getting 2 vendors for a singe purchase order , as we know that for a purchase order we cannot have multiple vendors.
When i checked data in deta queue (RSA7) we are able to see only single vendor for 1PO, but when we load to bw and checked data in PSA we are getting 2 different vendors for same PO.
Regards,
Vasu.

Hello,
As per my understanding you are getting data upto delat queue (RSA7) Correctly and you are getting incorrect data at PSA level In bw.
i think you must have some customer exit in ECC for the datsource 2lis_02_scl. so i would say that there may be some problem in the code since the customer exit code will get triggered after RSA7 and before PSA in BW..
Additionally you can cross check in RSA3 with update mode as 'D' which gives delta before loading to BW.
Debugging option :
Load data to BW and pick the PO having multiple vendors and in ECC dubug using RSA3 with update mode as "R" inorder to fing the problem in customer exit code.
Hope this helps you..
Regards,
Srikanth.

Delta Download from ISU BP to CRM BP doesn't work

Hi Experts,
We are currently new implementing a CRM7.0 system which is connected to an existing ISU system. We now have an issue about the BP delta download from ISU -> CRM.
Replication Scenario:
ISU BP -> CRM BP, NOT SD Customer -> CRM BP. As ISU is the leading system to create BPs and in ISU a MKK BP will be created first then a SD customer will be generated based on a template. So the change of a BP is via BP transaction for MKK role, not via XD02 SD Customer.
Issue:
The middleware setting is done and initial download from ISU BP -> CRM BP is done and successful. However when I trying to change a BP (change a MKK BP via BP transaction) in ISU, the change is not replicated to CRM (no queues, no BDOCs). It seems the delta download is not triggered at all.
However, I have maintained all the settings based on the ISU Specifics on the Set-Up-and-Load Guide for BP. So the followings are maintained:
- ISU: COM_BUPA_CALL_FU maintained based on the Guide
- CRM: CRMC_BUT_CALL_FU maintained based on the note 757955
- CRM: V_SMOFEVOB maintained based on the Guide
- ISU: BTE table (T-code: BF31) maintained based on the Guide
After setting above, the initial load is working (necessary table like CRMCONSUM, CRMRFCPAR etc. are maintained otherwise the initial download won't successful). However, the delta download from ISU BP (MKK) to CRM BP doesn't work.
The only uncertain thing for me is the setting for ISU : CRMC_BUT_CALL_FU. In the Guide only one sentence saying CRMC_BUT_CALL_FU needs to be maintained both in CRM and ISU and details refer to note 757955. However, the note 757955 only talks about FMs for CRM not for ISU/ECC. So in ISU/ECC the table CRMC_BUT_CALL_FU I activated for the following entries:
BPOUT BUPA 0100000 COM_BUPA_MWX_CREATE_MAIN
X
BPOUT BUPA 1000000 BUPA_OUTBOUND_MAIN
X
BPOUT BUPA 2000000 BUPA_CREATE_CHANGE_POINTER
X
BPOUT BUPA 3000000 BUPA_OUTBOUND_ALE_MAIN
X
BPOUT BUPX 1000000 MDS_BUPA_OUTBOUND
X
CLEAR BUPA 0100000 COM_BUPA_MWX_CLEAR_FLAGS
X
CLEAR BUPA 1000000 BUPA_OUTBOUND_CLEAR_FLAGS
X
CRMIN BUPA 1000000 BUPA_INBOUND_MAIN_CENTRAL
X
CRMIN BUPA 2000000 ABA_FSBP_INBOUND_MAIN
X
CRMOU BUPA 1000000 BUPA_OUTBOUND_BPS_FILL_CENTRAL X
CRMOU BUPA 1000010 ABA_FSBP_OUTBOUND_BPS_FILL
X
CRMOU BUPA 2000000 ABA_FSBP_OUTBOUND_BPS_FILL
X
MERGE BUPA 1000000 MERGE_BUPA_CENTRAL
X
MERGE BUPA 2000000 MERGE_BUPA_FINSERV
X
MERGE BUPR 1000000 MERGE_BUPR_CENTRAL
X
PXYIN BUPA 1000000 BUPA_INBOUND
X
XIIN BUPA 1000000 ABA_BUPA_MAP_PROXY_TO_DDIC
X
XIIN BUPA 2000000 ABA_FSBP_MAP_PROXY_TO_DDIC
X
XIIN BUPA 2100000 ABA_FSBP_MAP_PROXY_TO_DDIC_1   X
XIIN BUPA 3000000 ABA_FSBP_MAP_PROXY_TO_DDIC_1   X
XIIN BUPR 1000000 ABA_BUPR_MAP_PROXY_TO_DDIC
X
XIOUT BUPA 1000000 ABA_BUPA_MAP_DDIC_TO_PROXY
X
XIOUT BUPA 9000000 ABA_FSBP_MAP_DDIC_TO_PROXY
X
XIOUT BUPA 9000010 ABA_FSBP_MAP_DDIC_TO_PROXY_1   X
XIOUT BUPR 1000000 ABA_BUPR_MAP_DDIC_TO_PROXY
X
Not sure if the above setting is correct or not (some of the setting may not necessary, is that will impact the delta download from ISU to CRM)
Also what's the purpose of maintain two tables in ISU/ECC (COM_BUPA_CALL_FU and CRMC_BUT_CALL_FU)?
Also I have read some notes that the ISU BP -> CRM BP delta download is not triggered by above tables, it is triggered by BADI PARTNET_UPDATE, is this true, a bit confused.
I am looking forward a solution from you experts.
Thanks,
Laurence

Any inputs experts?

Problem with delta update on customised export data source.

Hi all BW gurus,
I have created several customised export data sources in the R/3 system. And I have made use of the utility program <Z_CHANGE_DELTA_PROCESS> to update the ROOSOURCE table.
While this can result in being able to do initial update (instead of full update), the subsuquent delta update is not working.
In RSA7, the datasource is with green light and in RSA3, the extractor can extractor data out of it.
Does anybody have some idea on this?
I heard that there is a way to change the Business Transaction Event (BTE), but I don't quite understand how this is performed. And wonder if this is the only way out. To me, the triggering point would be the same, meaning the InfoPackage would be executed, then call the extractors in R/3 to extract the delta update in order to load into the InfoCube.
And how do others do for executing delta update of the customised data source?
Thanks a lot!!
The utility program of <Z_CHANGE_DELTA_PROCESS>:
=================================================
report z_change_delta_process .
*P_DATAS DataSource
*P_DELTAP Delta Process for DataSource
parameters:
p_datas type roosource-oltpsource,
p_deltap type roosource-delta.
tables:
roosource.
data:
ls_roosource type roosource.
if p_datas(2) ne 'Z_'.
   message 'The DataSource needs to begin with ''Z_''.' type 'E'.
endif.
select single * from roosource into ls_roosource
       where oltpsource = p_datas
       and objvers = 'A'.
if sy-subrc eq 0.
   ls_roosource-delta = p_deltap.
   update roosource from ls_roosource.
message 'The DataSource has been updated successfully.' type 'I'.
else.
   message 'The DataSource entered is not valid, try again.' type 'E'.
endif.

Doesn't anyone have any idea on this topic?
Appreciate for all the help. Thanks.

How to make added custom field Delta mechanism work for LO Cookpit?

We appended a new custome field into extraction structure of the LO Cookpit datasource 2LIS_02_ITM through RSA6. And then run CMOD to write the exit code to populate the value and it works fine. But after we read Roberto's Weblog:
/people/sap.user72/blog/2005/02/14/logistic-cockpit--when-you-need-more--first-option-enhance-it , find the enhancement we did can't make the Delta mechanism works if only this new field gets changed in a record, and the change cannot be reflected on BW.
In order to make the Delta mechansim works, one option is to append the custom field into one of the LIS Communication Structure MCEKKO of 2LIS_02_ITM extraction structure and then write the enhancement code to this LIS Communication Structure. In this way, the custom field can be treated like standard field that whenever it gets changed, the Delta mechanism or the user exit will be triggered. The enhancement for this LIS Communication Struture is LEINS001.
Now we've got two problems when doing the above enhancements of the LIS Communication structure:
1. Maintain extraction structure problem in LBWE:
We added a custom field, e.g., called ZZZ in LIS Communication structure MCEKKO (Purchasing Document Header) by creating a new custom append structure and add the field ZZZ into it, then activate the new append structure, but get warning msg like "Field name DUMMY is reserved (Do not use structure as include in DB table)".
We do find a field called DUMMY in the structure MCEKKO. How to get rid of the warning msg and successfully activate the new custom append structure with the new field ZZZ?
You could say that we can ignore the warning msg, but why the new custom field appended can not be seen from the right side pool of the Maintain Extract Structure in LBWE? We need to make the new custom field shows up in the right side pool and then drag it over to the left side frame and to activate the extraction structure to change it. But now it doesn't show up in the right frame pool!
2. Refer to Sanyam's weblog
/people/sanyam.kapur/blog/2005/04/30/custom-fields-and-bw-extractors-making-a-mixed-marriage-work-part-ii, there is a sample code inside this article which tells us how the sample code looks like to write this LIS Communicaton structure enhancement to make the Delta mechanism works, below is the code we modified to suit our needs, but don't know if it would work?
DATA: i_t_ekko LIKE ekko   OCCURS 1 WITH HEADER LINE.
DATA: ebeln LIKE ekpo-ebeln,
      it_ekko TYPE TABLE OF ekko WITH HEADER LINE,
      old_val(50) TYPE c. "For storing the value from the Field Symbol
FIELD-SYMBOLS <fs> TYPE ANY TABLE.
CASE zeitp.
WHEN 'MA'.                            "When creating a purchase order
    MOVE '(SAPLEINS)T_EKKO[]' TO old_val.
    ASSIGN (old_val) TO <fs>.
    i_t_ekko[] = <fs>.
    LOOP AT xmcekko.
      ebeln = xmcekko-ebeln.
      IF xmcekko-supkz = '1'.            "Old Value ?
        SELECT SINGLE * FROM ekko INTO it_ekko WHERE ebeln = ebeln.
        xmcekko-ZZZ = it_ekko-ZZZ.
      ELSE.                              "New Value ?
        READ TABLE i_t_ekko WITH KEY ebeln = ebeln.
        xmcekko-ZZZ = i_t_ekko-ZZZ.
      ENDIF.
      MODIFY xmcekko.
    ENDLOOP.
EndCase.
Share your ideas and we will give you reward points!

Hello Kevin
We have exactly the same problem. Did you solve it? If you did, could you please tell us how you did it? We neither see our field in LBWE. Our field is a Z field from a Z table.
I hope you could help us. We just have this issue to finish our project.
Thanks a lot in advanced

Delta drain in R/3 for FI data sources

Hi Experts,
As part of EHP4 upgrade on the R/3 side we need to drain the delta queue in R/3.
We took the downtime in R/3 and
I triggered the delta infopackages for 0fi_gl_4, 0fi_gl_6, 0fi_aa_12, 0fi_ar_4 for 5 iterations.
Please clarify the following doubts:
1. For all the iterations I got the same number of records.
Can anyone please clarify why it fetched same no of records each time .
2. Against these data sources in RSA7, the count is not becoming '0'. As I remember it is showing 2 or 3 even after each iteration.
Please explain why these data sources are not showing '0' even after a couple of iteratioins.
Note: Postings are blocked at this time.
Need ur inputs here.
Regards,
Naveen V.

Hi,
Regarding 1, I think in system settings are done for FI datasources where it will fetch data from system time 2:00 am for each delta. This way same records are fetched again and again for whole day. You can confirm this by looking at your data in PSA.
http://help.sap.com/saphelp_nw04/helpdata/en/41/4b73415fb9157de10000000a155106/content.htm
Regarding 2, Im afraid RSA7 baffles me too. I have read that for some datasources it isnt records but LUWs that are shown. In any case if postings are stopped, then it shouldnt have created LUWs.
Edited by: Parth Kulkarni on May 3, 2011 11:47 AM

Delta queue & XML data source

Hi All
Can any body pls tell mme as to what this delta que ais and where is it used and how is it created,and also i want to know what is this XML Data source.
I need to get the data from XI,so i need this integration.
I would be very thank ful if any body cuold suggest me with a link on the notes ar step by step formatt.
Point's will be awarded,Thanks in advance.
Kittu

Hi Jay,
From Delta queue(RSA7) ur BW system is going to fetch the records of R3 or source system.
After extraction process it reaches RSA7 from there when u triggers infopackage
the job is ready to flood ur D.target with records.
Ensure that records are there for corresponding D.source this has to be attained thro' various Update methods(v3).
DataSource that is generated in SAP BW on the basis of a file-DataSource and
that can be used to push data to SAP BW
for more info on creation of XML D.source refer the link
http://help.sap.com/saphelp_nw04/helpdata/en/fe/65d03b3f34d172e10000000a11402f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/0b/3bc73b24062b48e10000000a11402f/frameset.htm
Reward if it's useful.
Thnks,
Karthick.

DELTA TRIGGERING

Similar Messages

Maybe you are looking for