Problem with delta in 2LIS_02_ITM

Hi All,
I tried to load delta data from 2LIS_02_ITM, but when the Job to populate the delta queue, the job was terminated with dump.
I scheduled the job in transaction LBWE and when the job was run I received the short dump "MESSAGE_TYPE_X".
Anybody knows How can I resolved this issue?
Regards,
Cesar Batista

Hi MD,
I did do that!!
I delete the delta queue in RSA7 and the setup data in LBWG. After that, I initialization the delta process of this datasource.
When I schedule the job to populated delta queue, I received this short dump.
Is there another thing that I need to do?
Tks,
Cesar Batista

Similar Messages

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

Generic delta has problem with delts pointer time stamp

Hi All,
We have generic delta data source with Delte pointer as Time stamp. We have not used any safety limits. We are loading the data to DSO and using Additive delta. But the problem is when delta flag is set, there might be a case where some records still being inserted to table with lower time stamp. These records are not being fetched in next delta.
We are planning to keep a safety upper limit of 5 min so that those records can not be missed. But we have a doubt as it is a Additive delta duplicate records will be loaded. If we make the delta to 'new status to changed records', it is going to work?? Any other things we have to check when we make this changes??
Thanks
Haaris

Hi
If you had selected additive delta then you can load data to DSo with addition mode only. No overwrite possible.
If you want to select new or changed status then you can load to DSO with overwrite mode only.
Additive or changed delta depends on your requirement because if you want to add data to the DSO then you can go ahead with additive otherwise you have to use DSO with overwrite mode only.
You can either give safety upper limit or lower limit but if you give safety lower limit then you can only load data to DSO with overwrite mode because there could be some duplicate records.
Hope it clarifies.
Regards
Sadeesh

Problems with delta from 0HR_PT_1

Dear all,
we have some problems with the delta mechnism of 0HR_PT_1. We know that it generates Infotype 0439 when being initialized for each employee that is in the initial selection, but then we don't get any data for further changes to the workschedule.
Does anybody know the exact menaing of the fields
*Last Changed     01.04.2010*
*Transfer to                          31.03.2010*
*Latest transfer until     31.12.9999*
The overall entries in PA0439 looks like this.
Any help is highly appreciated.
Kind regards, Philipp
Client     600
Personnel number     8000617
Subtype     0001
Object ID
Lock indicator
End Date     31.12.9999
Start Date     01.01.1800
Infotype record no.
Changed on     03.03.2010
Changed by     SAPLHRMS_BIW
Last Changed     01.04.2010
Transfer to                          31.03.2010
Latest transfer until     31.12.9999
Carry out transfer     X
Current Date     03.03.2010
Time     16:52:21

Hi
We are experiencing the same pattern for 0HR_PT_2
We are able to extrat some delta data but for unknown reasons some timesheet seem to be totally reversed...So the delta data we extract is inconsistent with the dat we can see in ECC6
Have you find out the root cause of your problem ?
Thanks for your help
PY

Problems with Delta Extraction for 0CRM_OPPT_H (no data found)

Hi,
I've some problems with the Delta Extraction of the Infosource 0crm_oppt_h (CRM Opportunities Header). After initialization I get no delta data from the CRM system.
What I already did:
Activated 0crm_oppt_h Data Source (checked functionality with rsa3)
Started Info Package (Init) on BW side (worked fine)
Checked the status of the Data Source on the CRM system using BWA7 ("initial upload" is unmarked; "delta active" is marked and what makes me worry is that the column "Queue exists" in unmarked...)
If I change anything (like Phase, Expected Sales Vol.) in the opportunity, the Delta Extraction get no changes.
Could You help me out, please?
Best regards,
Markus Svec

hi Markus,
try to check oss note 788172
Release Status Released for Customer
Released on 23.03.2005
Priority Correction with high priority
Category Program error
Symptom
No data exists in delta extraction from the CRM server to the BW system for business transactions, if parallel processing is applied as per note 639072. But Data is extracted if parallel processing is switched off.ie. when BWA_NUMBER_OFF_PROCESSES is set to 1,there is data during delta. This applies to the following DataSources:
0BBP_TD_CONTR_1
0CRM_COMPLAINTS_I
0CRM_LEAD_ATTR
0CRM_LEAD_H
0CRM_LEAD_I
0CRM_OPPT_ATTR
0CRM_OPPT_H
0CRM_OPP T_I
0CRM_QUOTATION_I
0CRM_QUOTA_ORDER_I
0CRM_SALES_ACT_1
0CRM_SALES_CONTR_I
0CRM_SALES_ORDER_I
0CRM_SRV_CODES
0 CRM_SRV_CONFIRM_H
0CRM_SRV_CONFIRM_I
0CRM_SRV_CONTRACT_H
0CRM_SRV_PROCESS_H
0CRM_SRV_PROCESS_I
Other terms
DataSources, BWA, initial extraction, delta init, parallel processing, no data in delta.
Reason and Prerequisites
There is an update on the generated delta table which causes data corruption in running delta initializations as the changed delta sets will be deleted with every further update on documents. An open cursor statement is there without fetch data in SMOX3_GET_DATA.
Solution
The problem is solved with the attached corrections.After applying the corrections a new initialization of the affected datasources is necessary.

Delta Mechanism CRM to BW - Problem with delta update

Hi BW Gurus
Delta update from CRM - BW 3.X is not pulling all the newly added records and records which were saved with error, warning in CRM to BW
Can any one suggest me an approch to fix this issue
please let me know if you need more info
Thanks in Advance,
Shilpi

Hi Shilpi
Did you manage to find a solution for this problem? If so, could you please let me know how you solved it.
I am also having a problem with datasource 0CRM_SALES_ACT_1 - when I do a full load, it works, but when I try to do a Delta load, it does not bring across any data. In transaction RSA7 on the CRM source system, the entry looks like this:
Green: Delta is recorded 0CRM_SALES_ACT_1 BWQCLNT320 0
Regards
Rayan

Problem with Delta Links

I have :
- a standard Workset with pages that are delta-linked to standard pages (nothing extraordinary so far...)
- a delta-link copy of that Workset
Consequently, the pages in my Workset are linked to pages in the standard Workset (themselves delta-linked to the "stand-alone" pages). Here is the link chain :
Pages <- Pages (Workset) <- Pages (specific Workset)
I deleted certain pages in the specific Workset.
Question :
1) How can I put those pages back in the specific Workset as if they hadn't been deleted ?
(if I copy the standalone standard pages with Delta-Link, I will lose 1 level in the Delta-Link hierarchy, am I wrong ?!
Indeed, I have this actual link chain :
Pages <- Pages (specific Workset)
instead of
Pages <- Pages (Workset) <- Pages (specific Workset)
2) Is it possible to change the ID of pages inside my own Workset for I have annoying suffixes (like '_2') that I think disturb the Navigation (I am implementing xRPM 2.0) ?
Thanks for your answers.

Hi Rajeev,
1) As illustrated, the only way I found to replace the deleted Pages in my Workset was to copy them from the standard Pages.
 However, doing so, you can see in the Delta-Link tracer that this implies a direct Link from the Pages in my Workset to the standard pages.
==> this means that if the Pages in the standard Workset are modified, modifications will NOT be reported in my pages.
 Only modifications on the standard Pages will be reported...
For instance :
a or A : Pages (stand-alone)
b : Pages (standard Workset)
c or C : Pages (specific Workset)
By copying the Workset, we create this Delta-Link chain :
a1 <- b1 <- c1
an <- bn <- cn
But, by copying directly from standard Pages, we've got this :
A1 <- C1
An <- Cn
As a consequence, changes on the standard pages are OK in both cases.
ai' <- bi' <- ci'
Ai' <- Ci'
We have : ci = Ci
But changes on the pages inside the standard Workset is troublesome :
ai <- bi' <- ci'
Ai <- Ci
We get : ci' <> Ci
The whole point is : is it possible to copy the pages inside the standard Workset ?
Hope it is clearer now...

Delta reocrds are not getting extracted . Problem with delta Quaue

Hello friends .
Could you please help me in this scenario ?
Its related to delta load from application 12 , - 2LIS_12_VCITM.
Some how data is not getting transferred from LBWQ to RSA7 . There are more than 200000 entries in LBWQ , but the job is not able to transfer any entries to RSA7.
For rest other application , data is going correctly .
The job status showing is correct , like XXXXX LUW are transferred there is no error in Job log , it technically correct .
I have found one notes , in SAP service market place , but still it doesnt match with my job status . My job status is NOTESID ..where as per the notes it should WKEDPI*** ( something like this ) .
I have taken below steps to solve this problem but still it doesnt work .
1.     Removed job from schedule ( the job for LBWQ to RSA7 ) and Executed the job manually .
2.     Executed Program RMSBW12.
3.     Deleted the Delta Q from RSA for application 12 and regenerated the same once again by running the infopackage , early delta initialization with out data transfer , . Once Delta Q is generated , run the job once again .
I hope , I tried with all correct way ..but still I could not able to transfer the data .
But with all above steps , still data is not transferred . Daily infopackage is running as per the schedule , and bringing only 0 record . If it still doesnt work then I have to do Re-initilization . and this is big cost for us . as we have to lock the sys for users and so on .
Could you please give me some tips , that how can I transferr the data from LBWQ to delta Q ( RSA7) . If it works then definitely , I will save my lot of time .
Please suggest me , how can I proceed . Please save me from this situation.
Many many thanks in advance.
Regards,

Hi Akshay,
Go to SMQ1 and check MCEX12 Queue. If your delta records are piling up in SMQ1 and not being transfered to RSA7, you need to check your back gound job control option once again.
The back ground collector job will collect the recrords from SMQ1 and push to RSA7.
Try to execute RMBWV312 program in SE38 and manully push all the recrods to RSA7. Once all the records are available in RSA7 you will find the MCEX12 queue will be cleared in SMQ1.
Cheers
Praveen

Problem with Delta IP on 0TCT_DS23 in Production system

Hi all,
I'm encountering a quite tricky problem: I'm currently working on the 0TCT_DS23 Datasource, with the technical content cube.
I can run an init infopackage on our 3 environments, Dev, Quality and production. Same for full packages. But when I try to run a delta IP, it is failing on the production system, with a dump of the extractor.
Looking at ST22, it's saying that there is
a syntax error in program "/BI0/SAPLQI0TCT_DS23 ".
Causes
    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/SAPLQI0TCT_DS23 " in
     include "/BI0/LQI0TCT_DS23$02 " in
    line 7:
    "A FUNCTION already exists with the name "/BI0/QI0TCT_DS23"."
    The include has been created and last changed by:
    Created by: "SAP* "
    Last changed by: "******"
When browsing the program, it's really the case, in the include   /BI0/LQI0TCT_DS23UXX, there are 3 includes,
*   THIS FILE IS GENERATED BY THE FUNCTION LIBRARY.             *
*   NEVER CHANGE IT MANUALLY, PLEASE!                           *
INCLUDE /BI0/LQI0TCT_DS23U01.
                    "/BI0/QI0TCT_DS23
INCLUDE /BI0/LQI0TCT_DS23U02.
                    "/BI0/QI0TCT_DS23
INCLUDE /BI0/LQI0TCT_DS23U03.
                    "/BI0/QI0TCT_DS230001
The U01 and U02 are containing the same function, so it's failing.
Do you ever have encountered the same problem, and if yes, how to solve it ? It already tried to reactivate the DS, but no way.
Thanks in advance
Frederic

Hi, Ralf
Thanks ! It worked ! I had to repair the function module. I assigned the points
Edited by: Frédéric GAUTHIER on Jan 29, 2010 11:12 AM

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.

Help! Problems with delta extraction

Hi All,
We've been trying to run a delta load of material master data and because there are so many change records (2.6m) it has been failing on memory errors. We have now run full load and it completed successfully. Ran delta again expecting that it would pull 0 records but it is still trying to pull all 2.6m records. Ran init w/o data. Ran delta again - still pulling 2.6m and failing.
Since we have successfully run full load, is it okay to delete the records from BDCP/BDCPS??
Other suggestions??

If you are not using it for other uses (eg. ALE with change pointers), it would be safe to remove the change pointers. You can use BD22 to delete them.

Problem with delta on Business Partner on CRM

Hi all!!
I´m trying to send delta from Business Partners on CRM. I have activated the change pointers for the message type BUS1006, object BUPA_BUP and for table BUT000 on transaction BD52.
When I create a new Business Partner an entry must be inserted on BDCPV view and is not, however When I modify a Business Partner, its corresponding entry is inserted on view.
I have seen for other message types this doesn´t occur.
Can somebody help me, please???
Thanks in advance and regards.

Hi, Ralf
Thanks ! It worked ! I had to repair the function module. I assigned the points
Edited by: Frédéric GAUTHIER on Jan 29, 2010 11:12 AM

Problem with delta load

Hi Gurus,
When I am doing a delta load from ODS to Cube it is taking lot of time....
When I clicked on PSA it is saying " An error occured when reading PSA DATA"...
What should I do???
Data is coming from flat file....

Hi
could you give the complete information about the error msg from monitor screen..status tab.
Check if any shortdumps in st22
Check for error logs
Also check in sm21.
It would be easy for us to give solution if you give the complete error msg.
REgards
Rak

PC issue.--Problem with index step.

Hi
Today our two chains are failed at loading ..
source is R/3 & update mode is delta.
Iam corrected the error and loaded the delta again useing repeat option,in cube request showing repeat of last delta.In monitor screen overall status is green but Total status showing is RED.But in cube it is showing green.loaded fine
For one chain when iam click on repeat on loading step ,it is loaded data fine into cube ,but unfortunately deleting index turned into yellow looking like execuating .This index step avalible on top of the loading step. before index step executed fine, load step is failed.when iam clck on repeat it is went to executing index step. I donot no why..but it is still showing yellow...
Now my question is, weather chains run tommrow with out any problem with deltas..? because chain still showing red colour.
Thanks
Bk

Hello Krishna Rao
I will explain clearly we have one PC haveing say 5 steps.1 2 3 4 5.
Third step is Deleting Index and Fourth step is Loading into cube.
Today our chain is failed at fourth step.Iam corrected the error and clicked on the repeat ..loading into cube done fine
But strangely in went to Third step to execute. that is still in yellow colour .But total chain status is showing red.
And also in batch monitor job was finished successfully.But in chain index step showing still yellow..
I think now iam clear for you...
Bk

Remote Delta link setup problem with Bean / Access Service

Hello,
I am trying to setup Remote Delta Link (RDL) between two portals. (Both portals same version - EP 7.0 EHP1 SP 05 - are in the same domain)
I already have the Remote Role Assignment working without any issues.
The following have been done successfully:
1. Same user repository has been setup for both the portals
2. Setup trust between producer and consumer (SSO working fine)
3. Producer added and registered succesfully on consumer
4. Permissions setup on producer and consumer
4. pcd_service user with required UME actions setup
I am able to see all the remote content in the Consumer portal.
When I try to copy the remote content and paste it as local content, I am getting the following error:
Could not create remote delta link to object 'page id'. Could not connect to the remote portal. The remote portal may be down, there may be a network problem, or your connection settings to the remote portal may be configured incorrectly.
After increasing the log severity, I am able to see the following in Default Trace:
com.sap.portal.fpn.transport.Trying to lookup access service (P4-RMI) for connecting to producer 'ess_int' with information: com.sap.portal.fpn.remote.AccessServiceInformation@31c92207[connectionURL=hostname.mycompany.com:50004, shouldUseSSL=false, RemoteName=AccessService]
com.sap.portal.fpn.transport.Unable to lookup access service (P4-RMI) with information: com.sap.portal.fpn.remote.AccessServiceInformation@31c92207[connectionURL=hostname.mycompany.com:50004, shouldUseSSL=false, RemoteName=AccessService]
AbstractAdvancedOperation.handleDirOperationException
[EXCEPTION]
com.sap.portal.pcm.admin.exceptions.DirOperationFailedException: Could not retrieve the bean / access service to connect with producer
Could not retrieve the bean / access service to connect with producer
Like you can see above, there is some bean / access service which is not retrieved successfully. I am not sure if this is a permission problem on the consumer.
I have checked that the P4 ports are configured correctly (standard - not changed) and I am able to telnet from producer to consumer (and vice versa) on the P4 port.
I am stuck at this point and am not able to find any information on this.
I would really appreciate if some one can point me in the right direction.
Thank you for reading.
- Raj

Hi Raj,
Please check your config of the P4 port on the producer. Is it really 50004 (check SystemInfo of the producer)?
I do think there's a problem with the P4 communication since RDL requires P4 connection.
Do you have load balanced consumer-producer connection? Please refer to this blog for further details
Little known ways to create a load balanced Consumer Producer connection in a FPN scenario
Regards,
Dao

Problem with delta in 2LIS_02_ITM

Similar Messages

Maybe you are looking for