R3AC1 Delta Load Filter Issues

Hello,
When a R/3 sales order (Sales Org 3020) is created it is being replicated from R/3 > CRM.
My filter in R3AC1 is set for Object Name SALESDOCUMENT:
VBAK-VKORG <> 3020.
I generated the filter after making the changed and the sales order will still come to CRM and it should not.
I have tried different scenarios also for example the PROCESS-TYPE of my sales orders in R/3 = OR.
I set the filter in SALESDOCUMENT to:
VBAK-AUART <> OR and still when a sales order was created, it came to CRM.

Maintain following entry, filter should work
Parameter name - CRM_FILTERING_ACTIVE
Param. Name 2 - SALESDOCUMENT
Param. Name 3 - SALESDOCUMENT
User - CRM
Param.Value - X

Similar Messages

SAP Mobile Sales 2.0 delta load issue for Sales Orders

Hello,
we have used Mobile Sales 2.0 with a Windows app for a while now. Our current issue is that sales reps won't see any historical sales order data on their devices.
Background
Due customer requirements, we need to make small changes to customer master data attributes and reload all customers from ERP to CRM. Then we ran delta loads (MAS_PARTNER followed by all other objects) to DOE, in which virtually all 5000+ customer accounts were compared. The delta load ran for about 3 days (some performance bottleneck we haven't located yet).
During the delta load, data on devices was inconsistent. Accounts were missing and all transaction data disappeared. After the delta loads, all accounts and contacts are OK, save for a few. Data from activities (appointments, tasks) have reappeared, as they should. Only sales orders won't reappear. The sales orders exist in the backend and belong to active accounts and sales reps.
Settings and troubleshooting so far
We don't have any limitations for sales orders in CRM Sales Mobile configuration.
We've run delta loads for all objects in transaction SDOE_LOAD.
MAS_CUSTOMIZATION etc seem fine.
We've re-run initial load for sales orders from CRM.
In the test system, we've even reinitialized the whole CDS database on DOE and on the devices, then re-ran the loads.
Checked steps suggested in discussion
SAP CRM 2.0 initial load issue
Historical sales orders (those created before the master data reload) exist in the backend, but don't show up on the device.
If I change one of those historical sales orders in the backend, it gets sent to the device.
If I create a new sales order in the backend or on the device, it is saved and replicated just fine.
To sum it up, it seems DOE is unable to identify the sales orders relevant for replication.

First Doubt i got clarify by my self as we can go with Unwired Runtime option .
But i still have doubt in :
2. How can i Modifying the Main Menu for iOS.
i am able to customize the same for windows using files SybaseCRM.Configuration.xml file.
Same how can i do for iphone/ipad.

Issue in the Delta load using RDA

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

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

Issue with Delta Load in BI 7.0... Need resolution

Hi
I am having difficulty in Delta load which uses a Generic Extractor. The generic extractor is based on a view of two Tables. I use the system date to perform the delta load. If the system date increaes by a day, the load is expected to pick up the extra records. One of the tables used in the view for master data does not have the system date in it.
the data does not even come up to PSA. It keeps saying there are no records.... Is it because I loaded the data for yesterday and manually adding today's data...?
Not sure what is the cuase of delta failing....
Appreciate any suggestions to take care of the issue.
Thanks.... SMaa

Hi
The Generic DataSource supports following delta types:
1. Calender day
2. Numeric Pointer
3. Time stamp
Calday u2013 it is based on a calday, we can run delta only once per day that to at the end of the clock to minimize the missing of delta records.
Numeric pointer u2013 This type of delta is suitable only when we are extracting data from a table which supports only creation of new records / change of existing records.
It supports
Additive Delta: With delta type additive delta, the record to be loaded only returns the respective changes to key figures for key figures that can be aggregated. The extracted data is added in BI (Targets: DSO and InfoCube)
New status for changed records: With delta type new status for changed records, each of the records to be
loaded returns the new status for all key figures and characteristics. The values in BI are overwritten (Targets: DSO and Master Data)
Time stamp u2013 Using timestamp we can run delta multiple times per day but we need to use the safety lower limit and safety upper limit with minimum of 5 minutes.
As you specified, the DS is based on VIEW (of two tables, with one containing date and other does not).
Kindly check the above lines and verify, if the view (primary key) could be used to determine the Delta for your DS.
Also let us the if any standard SAP tables used in creating VIEW and if so, what is the size of the DS load every day?
Thanks.
Nazeer

Issues with 0PP_C03 delta loads

Hi,
I loaded the data from 2LIS_04_P_ARBPL & 0PP_WCCP to 0PP_C03. Initialization of the data load went fine. Did the delta loads to BI and observed that I am not getting any of the Key figure data in the cube. All the values are showing as Zero.
When I observed the in the PSA table and in the RSA3 , I observed that for every order 2 entries got created, One is with +ve values and another with u2013ve. So at the end while updating to cube its nullifying the values. Because of this reason I am not able to view the latest data which is updated as Deltas.
I am not sure what settings I missed. Could some one please help me to fix this issue.
Thanks & Regards,
Shanthi.

Thanks Francisco Milan and Shilpa for the links. Itu2019s very useful. But still I didnu2019t able to find the cause of the issue.
My data source 2LIS_04_P_ARBPL is of ABR type and the update mode for KF is Summation. In the data source level, I am getting the values with before & after image (same entries one with +ve & another with u2013ve) and as I am using the u201CSummation as my update type for KF its getting nullified.
Because of this reason I could not able to get the values in my report. Could any one pls help me on this as I am reaching the go-live date. I need to address this issue immediately. Thanks for all your inputs.
Regards,
Shanthi.

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

Issue with delta load from R/3 to BW

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

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

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

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.

Issues with Delta Loads.

Hi All,
I hope you don’t mind to provide a suggestion about the delta load of Purchase Orders.
There was a request from Procurement team and they complaint that the data is not looking right.
For example: for a given purchase order the exemption flag is displayed as ADE.
Before change:
Purchase Doc Number
Puchase Exemption flag
90002106
ADE
They want this to be displayed as:
After Change :
Purchase Doc Number
Puchase Exemption flag
90002106
So ABAPER has included the logic in ECC Functional Module to populate the Extract Structure for Data Source to display above result. But the overnight run didn’t pick up the changes to above record in BW. The loads are delta loads.
So my Question is:
· This load for the Infocube Purchase Orders is delta load. Does change to Function Module will pick up the changes to old records as well? I mean if we are doing delta load does the old records gets changed and updated in CUBE or should I delete the data from all the PSA and Infocube and run the load into CUBE to pick up the changes. Am bit worried about deleting the data from Infocube as it may have history data (because of delta load). Total records in cube are 800000 records.
· Another question does the process chain trigger the function module to load the data into Extract Structure of data source in ECC (am bit confused about this process in ECC)?
Please suggest me how can I capture those changed records?
Any help would be much appreciated. Please let me know if you need more info.
Thanks in advance
Sandeep

Hi Sandeep,
I am little confused from your post. You are using 2lis_02_SCL or the generic FM datasource?.
Also it looks like new custom field added in your client. I never saw any purchase exemption flag even though i am working in purchasing flow for last 2 years.
W.r.t purchasing , deletion flag will be there which will come from EKPO and have the values S or L ( Deleted or Blocked).
You can block or delete a PO aslong as GR was not happened. Other wise you can do it. So use the EKPO-LOEKZ for your use.
Regards,
Rajesh

Material delta load parameter table it_marc is empty

Hi,
we are on SRM 7.0 using classic szenario. We use middleware to download material master from ECC. We us BADI Method IF_EX_PRODUCT_CUSTOMER2~MAP_R3_TO_CRM_MATERIAL to set the material status in SRM depending on MARC data.
When we do the initial download then the parameter table IT_MARC is not empty, and we can use it to set the material status depending on MARC data.
But when the material in ECC is changed, and the delta load runs, the parameter table is empty! Even when values in ECC table MARC are changed. In R3AC1 Filter the table is activ.
Does anyone have an idea why the parameter table IT_MARC is empty in BADI Method?
Best Regards,
Ben

Hi Ben,
I suggest you check documentation in note 428989. This should be of help to use this BADI.
Regards,
Ivy

Connection Object Delta Load not happening

Hi Gurus,
             I am doing integration between ISU and CRM 5.0. I have achieved integration both sides for BP , Contract Account. I have also done initial load for Connection Objects using object 'SI_CONNOBJ'. We are able to see IBase getting created for the Connection Objects but when I change the data in a particular Connection Object it is not trigerring Delta Load for the Object.
            Please help me for the same.

Hi Aishuman,,
Please check for the following entry in R/3 table TBE31:
EVENT    IBSSICON
LAND
APPLK    BC-MID
FUNCT    ECRM_CONTRACT_COLLECT_DATA
which brings the delta change to CRM.
Also,in CRM txn:R3AC1,check for the filter setting for object SI_CONNOBJ.
Also,in R/3 table CRMRFCPAR ,make sure that for object SI_CONNOBJ(or *) for consumser CRM(or *),value of DISCARDDAT is not set to X.If set to X,would prevent delta change to flow to CRM.
Also,check for the queue registration in txn:SMQR.If your queue is de-registered or lock is set,then entry will not be processed in CRM.
Hope this helps!
Regards,
Shanthala Kudva.

Cannot deactivate delta load of materials from R/3

Hi,
we have a problem deactivating the delta load of materials from R/3.
I deactivated the adapter objects MATERIAL and PRODUCT_MAT in R3AC1.
I even deleted the class MATERIAL in R3AC4.
The Bdoc's are not created any more, but the queues are still getting generated in SMQ2:
R3AD_MATERIA***
Am i wrong in assuming that this settings have to prevent queue creation?
Is this an error that anyone encountered or are there any other settings that I forgot to check?
Thank you,
Borut

Hi,
I have a similar problem. I have to deactivate delta flow of materials from ONE SITE only (F6A) and keep it flowing from other sites N6A and A6A - our CRM system is connected to multiple backends.
For the required site, i have removed all the conditions in the filter settings but still delta queue keeps on coming. Also, the queue is in SYSFAIL state - we are not able to download material from other sites - supposedly material from the other two sites gets queued up in this stuck queue.
Is there any way to stop the download from one particular site only?

Restrict Delta Load of Service orders in CRM

Hi,
<u>For the Techie guys in CRM:</u>
Can anybody please let me know how to Restrict the Delta load of Service Orders coming in CRM version 4.0 .
The Bdoc type coming is CRM_SO_DMBDOC.
Thanks,
Shobhit

You should be able to achieve this by doing some filter settings in R3AC1, isn't it?
Regards,
Kaushal

Delta load " material" object ?

Hi ,
I'm new to middleware ,i was trying to download the object material for delta load between R/3 to CRM ,in R3AS it is running more than 2 days &still ...
I am new to this middleware,i am like to know this process takes how much time to excute ?
2)we trying to dwnload saledocument in CRM,sender:r/3 receiver :CRM,but when we start excute for salesdocument it shows error :"no filiter citeria specfied (VBAK-ERDAT),object will not be loaded?
Please let me know about this issue..
Thanks,
Vasu

Hi Vasu,
It all depends upon the mass of the data. I recommend you to put some filter and then do the initial load through R3AS. Since your load is running for more than 2 days I will suggest to check the CRM inbound in transaction /nSMQ2. Some time it happens that the queue got stuck due to some error entry.
regarding the salesdocument you should only download the sales document once the load of BP, MATERIAL,CONDITIONS etc are completed. You should also put some filter that till what date you want to load the sales document. To do that you use the Transaction /nR3AC1 and select the object salesdocument and put the filter.
Hope this will help..
<b>Allot points if my post helps!!</b>
Best regards,
Vikash.

R3AC1 Delta Load Filter Issues

Similar Messages

Maybe you are looking for