Problem in initialization delta load

Hi All,
I am facing a problem while doing an initialization delta from one ODS obj to another.
Error says "data is not been updated in PSA table"
The ODS object I am trying to load is getting data from 3 ods below ODS obj, out of 3ODS's 2 were successfully loaded.
While doing this particular load it's coming with the same error. I tried full load also, but results are same.
Can anyone have some answers?
Regards,
Kironmoy

Hi,
In first init the data will move from the active data table to further data target then we will run delta at that tome the dat will go from change log table to further datatarget in our case u rrunning init but there is no daa in active data table so it is happening
here two options are there
1)either u can delete the change log table data and reload the data once again and do INIT with data transfer for further data target then it goes for next onwords delta data will come from change log table.
2)otherwise u go for INIT WITH OUT DATATRANSFER now no records will come to ur targeted datatarget just it gives delta flexibility only (by default 1 record willl come it is for delta initilization) now u go for the delta. now which are the records are avilable in change log those records will move from changelog to ur targeted datatarget.
Thanks
sathish

Similar Messages

Initialize Delta Load in Info Package

Hi,
I want to create 2 info packages for my load from datasource.
One with setting " Initialize Delta load with data transfer " in info package for my first load.
Second info package should be with " Delta Lad " which i am not finding in the second info package i am creating. Can you please tell me how can i get this setting as i am getting only Full or Intialize delta load only.
Regards
Syed

Make sure the following:
1) DataSource is Delta Enabled
2) An Init (or an Early Init) has already been done successfully. You should see the entry in RSA7 of the Source ERP
You should then be able to get the Delta option in the InfoPackage

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

Problem with initialization Delta queue

Hi Gurus,
I have problem with initialization of delta queue when I try load transaction data from R3 (FM) to BI.
Error message: Deviation of (64 seconds) between qRFC counter (000012365466830000080000) and actual time (08.03.2009 21:10:19).
I have no idea where is the problem because this problem occurs only in PRD systems. In DEV and QUA system everything is OK.
System BI: BI 7.0
Source system: ECC 6.0
Thank you for all answers!
mp

Hi,
Replicate the DS in BW Prod and then Activate Transfer rules and then try.
First you delete the DElta quae in RSA7 for the particular datasource in the R/3
source system then you try to intialize, here you are trying to intialize datasource with
same selection conditons . thats why it is giving shortdump
Check
Business Content and Extractors
Thanks
Reddy

Problem in running Delta load for 2LIS_13_VDKON

Hi Friends,
I am working on LO Data Source i.e., 2LIS_13_VDKON, i have run the INIT setup tables through OLI9BW. There were 2389443 records.
Now, since in BW these records multiply depending on condition types I didn't want unnecessary records. So I have run multiple INITs in BW with selection criterias as I wanted data only from 01-Jan-10. Having done that, now I want to run deltas but the BW system is not letting me do. If I click on Delta in the infopackage (in update rule) then it selection criteria it adds up all those INIT selection criteria that I have run and I can't change it (as in it becomes non-updatable); why is it adding up all those selection criteria in Delta infopackage?
I want to fetch all deltas from the day I ran OLI9BW...How to run delta for those records updated after run of OLI9BW.
Thanks!

Hi,
Follow the steps, these steps are for SD module, but for your datasource, change the Tcode to fill setup tables and replace the SD DataSource with your datasource in the following steps.
1. First Install the DataSOurce in RSA5 and see it in RSA6 and activate in LBWE.
Before doing the steps from 2 to 6 lock the ECC System, i.e. no transaction will happen
2. Then delete the Queues in LBWQ like below
     MCEX11 --> For 2LIS_11_*
     MCEX12 --> For 2LIS_12_*
     MCEX13 --> For 2LIS_13_*
Be carefull while doing all these deleations in Production Servers
3. Then delete if any entry is there in RSA7
     Eg:
     2LIS_11_*
     2LIS_12_*
     2LIS_13_*
4. Then delete setp tables using LBWG Tocde and select Application Number. i.e. 11, 12 and 13.
5. Then Load Setup Tables using OLI7BW, OLI8BW and OLI9BW.
   Give Name of run = XYZ, Termination Date = tomorrows date and execute it in background.
   i.e. Program-->Execute in Background.
   2LIS_11_* Use OLI7BW Tcode to fill the Setup tables
   2LIS_12_* Use OLI8BW Tcode to fill the Setup tables
   2LIS_13_* Use OLI9BW Tcode to fill the Setup tables
At the time of setup table filling no entry will exists in LBWQ in ECC for the following Queues.
     MCEX11 --> For 2LIS_11_*
     MCEX12 --> For 2LIS_12_*
     MCEX13 --> For 2LIS_13_*
6. Check the job status in SM37 and once finish it then goto RSA3 and then execute it and check.
7. Then Replicate the DataSource in BW.
8. Install InfoCube/DSO from Business Content or cretae InfoCube/DSO and then Map the ECC DataSOurce Fields and BW          InfoObejcts in Transfer Rules (in BW 3.5) or in Transfermations (in BI 7.0).
9. Map the InfoObejcts in InfoSource and InfoObejects in InfoCube/DSO in in Update Rules (in BW 3.5) or in Transfermations
   (in BI 7.0).
10.Create InfoPackage and Load Init/Full.
11.Using DTP you can load to InfoCube/DSO (if it is BI 7.0)
Thanks
Reddy

ODS Delta Load --- Activation problem

Hi
I had an ODS, newly transported in to procuction. I did Initialization for that with out having any problem. But i am facing problem in the delta load. I can see that delta data load is successfull. But couldnot able to Activate the delta load request.
I can able to see following comments in cancelled job log.
Key value exists in duplicate (Not allowed by the ODS object type)
System error occurred (RFC
call)
Errors occured when carrying out activation
Can you please help me out why activation of delta request cancelling?
Thanks & Best Regards,
Venkata

hi..
for ur ODS..right click..go to change..in the settings..the checkbox for 'unique data records' must be ticked.
in dev..remove this checkbox and then save/activate the ODS.
transport this change to prod and then reload the data to the ODS in prod.
the delta request will surely load(and also activate) without any problem.
cheers,
Vishvesh
Message was edited by: Vishvesh

Delta load probelm in production orders

Hi Friends,
       I did initialization delta load successfully for both ODS and CUBE. i am using the data source shop floor control application of material view of PP.
         now i am going to schdeled deltas.
   what i need to do for delta in r/3 side and bw side.
Please give me advices on this. because previously i did the deltas for same data source not getting the delta recorde.then i deleted every thing i do again init.
Please give me clear steps on this. iam waiting for reply.
Thanks,
Guna.

Hi............
For scheduling V3 job Go to LBWE--Select the Application Area - select Job Controland give your periodicity .
Check this Links :
/people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146
LOGISTIC COCKPIT DELTA MECHANISM - Episode three: the new update methods
LOGISTIC COCKPIT - WHEN YOU NEED MORE - First option: enhance it !
LOGISTIC COCKPIT DELTA MECHANISM - Episode two: V3 Update, when some problems can occur...
LOGISTIC COCKPIT: a new deal overshadowed by the old-fashioned LIS ?
v1 , v2 , and v3 updates
Regards,
Debjani...........
Edited by: Debjani Mukherjee on Sep 17, 2008 10:54 AM
Edited by: Debjani Mukherjee on Sep 17, 2008 10:55 AM

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?

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 load problem after Initialization

Hi everyone.........................I need your inputs on the following problem that I ran into:
I have an ODS which gets supplied by regular delta loads.
Accidentlly, I have deleted the Initialization(Info Package->Scheduler->Initialization options for source systems). Because of this the delta loads are broken.
I am now trying to fix this by Initializing it again(but without data transfer as I dont need all the data till this current point again). That worked successfully.
But the deltas after this initialization are causing a problem. The first delta that I loaded failed with an error :
"Delta Request REQU123XYZ is incorrect in the monitor.
A repeat needs to be requested. Data target (ODS) still includes delta request REQU123XYZ. If the repeat is now loaded, then after the load there could be duplicate data in the data target.
Request the repeat?"
I repeat the delta load and this time around it loads correctly.
The next delta that I load after this is again an error. The repeat of this is again a correct one.
This problem continues.
Can anyone throw some light on whats going wrong?
Thanks.

Hi Sat,
I tried your suggestion by turning the failed request manually to green.
However, for the next delta load, the info package just wouldnt allow me to initate a load saying that-
"Last delta update is not yet completed
Therefore, no new delta update is possible.
You can start the request again
if the last delta request is red or green in the monitor".
Although it says not yet completed, I can see that the request has failed.
Any more alternatives will be highly appreciated.
Thanks.

Problem in delta load with Z field

Hello Experts,
We have CRM 5.0 system and as per the requirement we have
added ZFIELD to BUT000 table. This field is added to BUT000 via EEWB – Easy
Enhancement Workbench. This field is also BW enabled.
BW enabled means – this field is used / available to BW
extractor for further analysis.
We update this ZFIELD with custom program – FM BUPA_CENTRAL_CI_CHANGE.
When full load is done – data flows to BW correctly, ZFIELD
values are reflecting correctly. But when we are doing delta load it is not
working.
If we use BP t-code delta works perfectly. So issue from BW
side is ruled out. The FM BUPA_CENTRAL_CI_CHANGE is not triggering the change
record for this BP. But then I don’t see any other FM / BAPI to use so that
change record is also created.
Could you please provide any pointers or any checks to
overcome this problem?
Thanks in advance.

Hi Ashtankar,
When you are changing the attributes(say ZFIELD) and save the transaction in BP, Is this updating the CHDAT(Change date) in BUT000?
If the change date is being applied, then Delta shouldnt be a problem - if you are using datasource 0BPARTNER_ATTR.
In order to check if the delta is being captured or not, you could use TCODE RSA7. Also, this brings the Doubt when you say Full load works while delta doesnt, try Re-initializing the datasource from BW after Datasource replication - because there have been some changes effective in Source system which the BW system/Delta queue might take into consideration.
Regards,
Thejas K

Problem with delta load urgent!!

Hi,
I have a problem with delta load
We have an IP, which loads data from R/3 system daily, its a delta load to the ODS and it updates to the cube with the selection on Company Codes and 0FISCPER
we are in 3.5 system
For a couple of company codes A & B, the init was done for the period 07.2010 to 12.2099 and after tht the deltas are loaded from 07.2010 till 12.2099 and there's no pblm with tht
Now, there was some updation in R/3 system and the data was maintained for the company codes in A& B for the FISCPER 001.2010 to 006.2010, for which init wasnt maintained...
now how shall we need to load the init in this case? dnt ask me how the postings was done in R/3, but my pblm is purely related to the loading data in BW from R/3, as its very imp for the customer to see the data from 01.2010 to 12.2010 in reports, but the data was only available in reports from 07.2010 onwards
do i need to create another IP and maintain the init for 01.2010 to 06.2010? so tht this selection will automatically appear in the ODS delta loading infopackage
pls throw ur inputs ASAP
thank you

Hi Prince,
No need to maintain any Init for this data, It will be enough if you can load the data from jan 2010 to jun 2010 into your Info Cube.
Follow the below steps:
1)create full load IP for this data source.
2) give the selection as A and B company codes and 0FISCPER as 001.2010 to 006.2010
3) in menu bar, click on scheduler --> select full repair request
4) In the next screen check the check box and save
5) Now execute the IP, it will the data with out disturbing your daily delta.
follow the same procedure to load data till to your Info Cube.
Please revert if you have any questions
Regards,
Venkatesh

GenericServiceFactory initialization problem when trying to load Web servic

Hi,
I am making a Guided procedure that calls a webservice. I have created a new Destination Template and was able to load the webservice definition successfully, but when I test the callable object I created for that same webservice y get the error:
GenericServiceFactory initialization problem when trying to load Web service model for WSDL.
Somehow I think there is something wrong with the user authentication. The Destination template has a user and password but somehow I think the callable object test is not using this information at all.
Can anyone help ?
Thanks in advance

Hi Hans,
Have you verified if you can call any external web service calls from your J2EE engine? Go into the SOA Management / Global settings (if you are on CE - if you're on 7.0 it's in manage WS desintations).
Look at your proxy settings and set them like your web browser that enables external calls. For example, in the SAP network I set my global proxy settings on my local J2EE engine to be:
Proxy host: proxy
Proxy port: 8080
Exclude list: *.sap.corp
Does that make sense - have you verified if your settings are correct for your company?
Regards
Ginger

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

Initialization of delta loads possible with process chain?

hello all,
followed situation:
i load data from file and sap extractor to ods 1. from this ods i have an automatic delta load to another ods 2, where the data are filtered and aggregated.
its possible that some of the data change their state from filtered out to in but are not in ods 2 because of the earlier criterias they had have. now i want a weekly load (initial load) from ods 1 to ods 2 and a daily delta load if new data arrived ods 1 to the no 2.
i tried to create a process chain for that but i cant! i cannot use the info package for the initialization of the load from ods 1 to 2 because it is generated info package. and if i use the process "update ods object data" there is always tried to make a delta load! at first step i delete all data of ods 2, so i need an initialization with data as next step.
how can i do what i want?
thanks for any idea
Frank

Hello Tom,
ok, i understand but i dont know how...
The only way i know to create an InfoPackage between ODS is to use "Update ODS Data in Data Target" of the context menu of an ODS. Then i chose between full/delta/init load and the infopackage will be generated. How else can i create it?
Frank

Problem in initialization delta load

Similar Messages

Maybe you are looking for