The delta load for generic machine in CRM doesnt run.

When the machine was dismantled from a location and installed on a different Functional location. The changes didnt download to CRM. Even the request load fails for the same. The machine is a generic Machine.
In R/3, the queue is in STOP status and gives the error Generic stop set on activation.
User had changed the Functional Location for a Generic machine in R/3. The changes didnt upload to CRM. Even the request load failed to upload the changes.
The Idoc is failed on R/3 , it gives the error message - Generic Stop Set.
Thanks in advance

Hello Mohammed,
I have also met with this issue in the past, and I have resolved it by steps described in this link: http://scn.sap.com/docs/DOC-56972
Hope it helps.
Best regards,
Jerry

Similar Messages

Delta Loads for 2lis_02_scl and 2lis_02_itm

Hi Experts,
I am facing an issue, After initializing the setup tables and doing the init load for 2lis_02_scl and 2lis_02_itm whenever I do the delta loading for these two, all the dataload finish with green status and extracting 0 from 0 records.
I can see the queues for both these datasources in RSA7 in R/3, yet no record is extracted.
Any help will be appreciated.
Regards.

Hi,
have a look into transaction smq1. there you should be able to see your extraction queues with the entry MCEX02 (or likewise)
Please schedule the program RMBWV302 and when this one is finished, start the deltapackage.
hth
cheers
sven

Initialize the delta load

Hi BW Experts,
I have question...
1. There is a ODS01 which feeds many data targets.
2. We created a ODS02 which also will be loaded by this ODS01. The update type would be DELTA.
3. We created a INFOCUBE01 which will be loaded by the ODS02. The update method would be FULL UPDATE.
4. The first time (later on i didnt get this msg) when i went to the infosource for the 8ODS02 and tried to create a infopakge to load the full update of the INFOCUBE01, i got a msg that " THERE IS NO ACTIVE DELTA INITIALIZATION FOR THIS DATASOURCE".
The details of the msg is:
Procedure
You have to initialize the delta load for a DataSource before you are able to load the delta data from it.
If you want to load deltas only for the purposes of testing, or you do not require any initialization data (because you have already uploaded it using a full upload, for example) use an initialization simulation.
This way, only the init. entries you require are made in the control tables of the source system, and a 'dummy' entry appears in the Monitor, setting the load status to green.
No data is in fact loaded, however, and the initialization takes only a few seconds to complete.
Does this mean i have initialize the delta load in the ODS02 or the INFOCUBE01.
How do i do that ?
(I actually did few full loads then i was informed that it would be a delta load from the ODS01 to ODS02,
within the infopkg for ODS02, I selected the Delta update next time, and did start immdtly, then check the monitor, it displays no records)
I'm little confused with this initialization, and in what cases would i do it.
Would you please help...
Thank you,
Tia
Message was edited by: Tia Ismail

1. so, you are saying for the ODS02, do a full load first.
2. Then do a "Initialize delta process".
3. Then do a "delta process".
I had partially tried this, I did a full load first in one infopackage, then created another infopackage trying to do a "Initialize delta process". I get a msg as following:
Diagnosis
Deltas have already been loaded for the init. selection of request REQU_3ZEHH34LV68LVHAWT75TJVIF8. A second initialization is therefore not possible with these selection conditions.
Procedure
If you want to carry out a new initialization, you have to choose selections that do not overlap.
If you want to repeat the init. for the same selection, you have to delete the delta queue in the source system, and restart the delta process.
Choose the menu entry 'Init. Selections in the Source System' from the Scheduler.
Any thoughts...
Thank you,
Tia

Middleware - Delta load is not working from CRM to R/3

Hi Experts,
Our client is using SAP-R/3 4.7 and CRM 5.0
Connectivity was established via Middleware and initial load of Customizing objects and Master data( Customer and Material) was finished successfully.
Now if i create any Customer or Product in R/3 they were replicating to CRM(Delta load), but this delta load is not working in CRM to R/3 direction.
In CRM Administration console( Transaction code - SMOEAC) R/3 site was maintained and subscribed for Publications - All Business Partners, All Business Transactions and All Business partner Relationships.
Can anybody help me out that why Delta load is not happening from CRM to R/3 Direction.
Thanks in advance
Nadh.

Hi Nadh,
for BPs check PIDE settings once agiain, i hope u ve already downloaded all mandatory obects for BP, because u already told that replication from r/3 to crm is ok, so check once again PIDE settings (CRM to R/3),
for Products u ve to manual upload only
for Products
This may be necessary because the data is required in the OLTP System for a number of logistical processes such as procurement, inventory management, billing, financial accounting, controlling.
cheers
Ranga

Restrict Delta Load of Service orders in CRM

Hi,
For the Techie guys in CRM:
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 loading of generic data source.

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

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

Delta loading in Generic extraction

Hi Everybody,
Can anybody explain the procedure of delta loading in generic extraction.
With Regards
Raju

Raju,
Just goto RSO2->Enter your datasource name->Click Generic Delta
Select one in Delta Specfied field.
Either Time stamp or Calender day or numeric Pointer.
If you select Numeric Pointer then enter the filed name on which you want to creat delta in Field name.
Or just browse in Field name , it will display you all valid fields for delta.
Check new status for changed records.
Now save.You know the next steps.
If you need any thing else.Buzz me.
Thanks
Ram
"BW is Everywhere"
Then make necessary setting in setting.
Safety interval upperlimit-1
Safety interval lowetlimit-1

I can not make delta load for some component of public sector management

Hello All:
I´am using these three data source 0PU_IS_PS_31, 0PU_IS_PS_32 and 0PU_IS_PS_42 and I realize that I can not make delta loads. When I make the full load everything is correct even when I made the delta, the problem is that the Delta load is not extracting any new data or changed data.
Do you have any idea to fix this issue?
Thanks
Message was edited by: Víctor Olivera

Hello Victor,
As u have already tried the delta load,I assume that u have already done the init load too.As system will not allow u to do delta load without doing an init load first.
The first datasource u talked about..31..it needs new records created in table FMIOI table.
What happens is..if u run a delta load immediately after an init load,there might not be new or changed records created in the system..therefore there arent any records in the delta queue.
Could u try creating some commitment document transaction data,so that records get added in FMIOI table.Then see if the delta queue for this datasource shows any records.
Links to BC pages for these datasources are below..
http://help.sap.com/saphelp_nw04/helpdata/en/1a/8c425e8afe11d496d80000e835339d/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/1a/8c42618afe11d496d80000e835339d/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/e1/46a53ec5f0c0428fa8b9cfcdcd9fcd/frameset.htm
Note that for 42 datasource..page says that delta update is not supported(though it does talk about updating delta queue).
For 32 datasource source tables are FMIFIIT and FMIFIHD.
For 42 datasource table is FMBDP.
cheers,
Vishvesh

Delta load for 2LIS_06_INV is failing after EHP5 upgrade of ECC system

Hi Experts,
Our ECC Production system was upgraded to EHP5 last weekend.
Since then Delta load for datasource 2LIS_06_INV is failing. This is the only datasource got impacted. Full Load and Initialization Loads are running fine. Only Delta load is failing because of following error:
Error in the ABAP Application Program
The current ABAP program "SAPMSSY1" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "/BI0/SAPLQI2LIS_06_INV " in
include "/BI0/LQI2LIS_06_INVU04 " in
line 1:
"Function "/BI0/QI2LIS_06_INV0002" not found in Function Library."
Thanks and Regards,
Sandeep Sharma

SAP suggested Note to fix this issue.

Duplcate records in the delta load

BW experts,
I am getting the following errors when doing a delta load from 2LIS_02_ITM
into OBBP_CON, 0BBP_INV, 0BBP_PO, 0SRCT_DS1, 0SR_VEGUID.
The delta loads show a green light for all the targets except 0SR_VEGUID and
the error message is
3 Duplicate record found. 2295 records used in /BIO/XSR_VEGUID
3 Duplicate record found. 2295 records used in /BIO/PSR_VEGUID
I tried to check the contents of the both /BIO/XSR_VEGUID and
/BIO/PSR_VEGUID but i get a message saying the tables are not active in the
dictionary.
However, i can view the data in the Info object OSR_VEGUID.
How can i resolve this issue ?
Any help will be appreciated.
Many Thanks

Kiran,
Welcome to SDN,
P and X tables are created only if you have 1. Time dependent Navigational Attributes ( X Table)
2. Time Independent Master Data Attributes.. ( P table)
Otherwise the tables will not be created.
Arun
What table do you see in the header when you see the data for the infoobject ? on the creen - do you see something like
/bi0/XX0SR_VEGUID where XX xould be some characters ... Ideally P table should be viewable...

Delta load for a data source not enabled

Dear Experts,
We have got the requirement to create reports on shipment details.
Based on the requirement we have identified the
Infosouce/ Data source : 0OI_TD_OIGSII
Info Cube: 0OI_TDC01. we think this cube will satisfy the requiremnt.
But the problem is the data source is not delta enabled. so how do we extract the data and how to capture the delta.
when we checked in Roosource table the delta field is blank (Delta only with Full Upload (ODS or InfoPackage Selection))
These data sources are IS OIL specific, so dont know the data extraction procedure.
Please through some light and help me.
Please advise.
Regards
venu

Delete duplicate request is a process chain variant, which will allow you to set the duplicate request deletion options. You need to explore those options.
Now say you have a routine in the DTPs.
DTP1 = Current Month
DTP2 = Prevoius Month
In the month of July,
DTP1 = 07/2009
DTP2 = 06/2009
On daily basis DTP1 will load data for July and DTP2 will load data for June. Now delete duplicate request will delete the previous requests loaded by each of them for the same month. Meaning delete duplicate request for DTP1, will delete the request loaded for 07/2009 and DTP2 will delete the duplicate request for 06/2009.
Now when you will be in Aug, the routine will change the selection criteria
DTP1 = 08/2009
DTP2 = 07/2009, so now DTP2 will delete teh duplicate request for 07/2009 and load the new data. Now the data changed for 06/2009 is not possible to load as you have only 2 DTPs.
For safer side, you can create 3 DTPs to take care of the last 3 months, but first test the logic for two DTPs and then go further for the third DTP.
- Danny

Re: Delta Load for master attribute CUSTOMER

Dear All,
I have got the delta loading into 0customer_attr and 0 material_attr in production. Yesterday the load failed because the previous change run run has been terminated and locked the attributes of characterstics 0 material and 0customer.
To solve this i went back and ran the attribute change run and all the locks got released.
Now i know that i need to repaeat the delta load.
If we go to the RSMO for the failed load i see that under details tab in processin option we have as follows
Transfer rules(67-->67 records):No errors(This is Green)
   Master data received:Processing being started(Green)
   Transfer 67 data records in communication structure(Green)
This is where the processing stopped.
Update(0new/0changed)(in red): Errors occured
My doubt is if i now repeat the load in process chain will the 67 records come into the0customer infoobject.
Will this have any impact on the next day delta load.
Kindly advice.
Regards
Madhuri

Hi abhijit,
When i tried to do a repeat delta the load failed again and when i check for the error message i get the following
Diagnosis
    The application program for the extraction of the data was called using
    update mode R . However, this is not supported by the InfoSource.
System Response
    The data extraction is terminated.
Procedure
    Check for relevant OSS Notes, or send a problem message of your own.
Procedure for System Administration
How do i proceed further.
Regards
Madhuri

Delta load for 0customer

Hi Friends,
I have a issue in delta load for 0customer. The load was initialized with data transfer for the first time load ,The data was loaded succesfully , now we have enhaced the 0customer_attr with customer group .In RSA3 if we check we are getting values for customer group. we created one delta infopackage with update status as delta and scheduled the load .we are getting data load success status but with 0 records. Please can anybody share the process for delta load for master data objects. Iam facing similar problem while uploading delta load for 0MATERIAL.
Regards,
Dippy

Hi
in source system, check whether your enhanced field is with hide check box ticked.
As soon as you add filed in append structure by default it is having that field is hidden. You have to uncheck it.
Then replicate the datasource in BW.
Now if delta is the issue that you are not getting ant record, that may be because there is no change in master data, delta will only bring records when there will be nay change in master data update.
So my suggestion is to crate a full repair infopackage, extract everything in to PSA and then load the data with FULL DTP.
I hope this will work.
Thank-You.
Regards,
Vinod

Delta Option for Generic Data Source

Hi ,
My requirement is Delta Option for Generic Data Source. This Data Source is getting Extracted from Function Module.
For this requirement I have followed below steps.
1) Added the Field (On which Delta gets enabled) to the extract structure by using Append Structure
2) Enabled Delta On this Filed.
3) If I try to save the Data Source, I have gone to a screen where I am able to see 4 coloumns
a) Selection
b) Hide Field
c) Inversion
d) Filed Only known in User Exit.
By default Hide Field and Filed Only known in User Exit check boxes have been checked.
Would you please tell what is the use of Filled Only known in User Exit check biox.
As My data source is getting the data buy using the Function Module, Shall I uncheck this Check Box.
Thanks and Regards,
K.Krishna Chaitanya.

Hi Krishna,
The "FIELD" should be checked if we write any enhancement in CMOD, so that system can identify that this particular field has enhancement written to it,
But even in real time systems i usually find that even though we check the "FIELD" or not , there is no effect .
So Checking "FIELD" or not will not impose any isses .
Regards,
Krishna

Delta loading through Generic extractor - function module not found

Hi,
I'm working on a BW3.5 system and we have some generic delta FM extractors. One of these is called ZBW_CONF_DELTA and the FM is also called ZBW_CONF_DELTA. It is a delta-enabled extractor. Whenever an extraction is done in the init delta mode, the data gets picked up from SAP.
However, whenever we load subsequent deltas, the extractor brings zero records. When I look in the SM37 logs in R/3, it says "Function module /BIC/QIZBW_CONF_DELTA0001 does not exist"
I'm not sure where the "/BIC/QIZBW_CONF_DELTA0001" function module name came from, because I haven't given it like that (if I did, the init load would also have failed).
Due to this problem, I'm unable to perform any delta loads. Is there anything I could be doing to fix this?
Regards

Hi,
First check how extractor works in R/3 side using RSA3
Make a full load.
Now check the generic delta field of your generic extractor, lets say changed on date.
Do the SAP transaction ( take help from some Functional COnsultant ) to update that delta field. Note that record.
Now if u do the delta load with same extractor, you are suppose to get that record.
If not then there is some problem with FM or extracor.
Let me know what happens.
Thank-You.
Regards,
Vinod

The delta load for generic machine in CRM doesnt run.

Similar Messages

Maybe you are looking for