Dump during delta load

We have taken down time and done a full upload to 2lis_11_vaitm. Deltas are not flowing. When checked up we found in MCEx_11 delta que lot of records are available. But in rsa7 records are 0. When scheduled from delta que to rsa7, job was cancelled and the following is the dump. For info. we have actiated only 2lis_11_vaitm in the application 11. Please help.
The termination occurred in the ABAP program "SAPLMCEX" in "MCEX_UPDATE_11".
The main program was "RMCEXUP1 ".
The termination occurred in line 72 of the source code of the (Include)
program "LMCEXU14"
of the source code of program "LMCEXU14" (when calling the editor 720).
The program "SAPLMCEX" was started as a background job.
Source code extract
000420
000430     IF NOT I_DDIC_HASH IS INITIAL.
000440
000450       IF gf_tmsp_hash_ok IS INITIAL.
000460
000470         CALL FUNCTION 'MCEX_GEN_AND_CHECK_HASH'
000480         EXPORTING
000490           I_FUNCNAME                = 'MCEX_UPDATE_11'
000500           I_COLLECTIVE_RUN          = 'X'
000510           I_APPLICATION             = '11'
000520           I_STORED_DDIC_HASH        = I_DDIC_HASH
000530           I_STORED_TMSP_HASH        = I_TMSP_HASH
000540         IMPORTING
000550           E_DDIC_HASH               = I_DDIC_HASH
000560           E_TMSP_HASH               = lf_TMSP_HASH
000570         EXCEPTIONS
000580           HASH_COMPARE_OK           = 1
000590           HASH_COMPARE_NOT_OK       = 2
000600           NO_INTERFACE              = 3
000610           HASH_ERROR                = 4
000620           DDIC_ERROR                = 5
000630           OTHERS                    = 6 .
000640
000650       IF I_TMSP_HASH = lf_tmsp_hash.
000660         gf_tmsp_hash_ok = true.
000670       ENDIF.
000680       case sy-subrc.
000690         when 0. " Compare OK - do nothing
000700         when 1. "Compare OK - do nothing
000710         when 2. " Compare not ok - abort
>           message x194(mcex) with sy-subrc.
000730         when others.
000740           message x193(mcex) with sy-subrc.
000750       endcase.
000760       endif.
000770     endif.

Hi Pooja,
Did you made any changes to the Extract structure?
If yes, then the only reason for the error message -----> message x194(mcex) with sy-subrc. is that there was data present in the extraction queue while you changed the extract structure.
There are 2 solutions:
1. Either you have to delete the data from Extraction Queue. (If the system is down i.e., still locked for users posting, you can do this)
2. Check the solution in SAP NOTE 835466
Regards
Hemant

Similar Messages

Short dump in ECC 6.0 during delta load

Hi,
We are currently working in BI upgrade project
from BW 2.1c to BI 7.0
At the same time R/3 is being upgraded from 4.0B to ECC 6.0
During delta load we are getting short dump in R/3 system.
Below is the short dump detalis
The current ABAP prgm "SAPMSSY1" had to be terminated because it has come across a statement that unfortunately cannot be executed.
The following syntax error occured in program "/BI0/SAPLQI2LIS_11_VAITM" in include "/BI0/SAPLQI2LIS_11_VAITM" is not Unicode-compatible, according to its attributes.
If any help can be provided on this issue it would be great.
Regards,
Nikhil
Edited by: Nikhil Sakhardanday on Sep 11, 2008 1:58 PM

Hi,
did you made UCCHECK ?
/manfred

Dadatasouce 0TCT_DS22 giving dump in delta load.(

H Experts,
I have Initialised technical datasource 0TCT_DS22 and immidiately wants to fetch delta but it's giving dump.
TSV_TNEW_PAGE_ALLOC_FAILED. This seems to be internal memory problem ,but after initalisation it shouldn't throw this dump.What may be another reason?
When should one go for technical content data loading?is it during normal loads?or later?
Thanks
Girish

Hi,
As Neetika mentioned, it is due to large data volume.
Please check with the basis team to get reduced the jobs scheduled for this activity or try to extract the relevant data by providing any filters if possible.
Regards,
Geeta

Job terminated in source system - Request set to red during delta load

Hi All,
There is issue with the delta load where as full load works fine and it results in below job termination with below log.
Job started
Step 001 started (program SBIE0001, variant &0000000128086, user ID ALEREMOTE1)
Asynchronous transmission of info IDoc 2 in task 0001 (0 parallel tasks)
DATASOURCE = 2LIS_13_VDITM
RLOGSYS    = BWP_010
REQUNR     = REQU_DA9R6Y5VOREXMP21CICMLZUZU
UPDMODE    = R
LANGUAGES = *
         Current Values for Selected Profile Parameters               *
abap/heap_area_nondia......... 0                                       *
abap/heap_area_total.......... 17173577728                             *
abap/heaplimit................ 40000000                                *
zcsa/installed_languages...... DE                                      *
zcsa/system_language.......... E                                       *
ztta/max_memreq_MB............ 2047                                    *
ztta/roll_area................ 3000000                                 *
ztta/roll_extension........... 2000000000                              *
Object requested is currently locked by user ALEREMOTE1
Job cancelled after system exception ERROR_MESSAGE
Please help me to resolve this issue.
Thanks,
Madhu,

Hello,
As per the screen shot provided below, data soruce belongs to LO, so first check in RSA7, whether it has got mark in RSA7, for which you have entries in RSA7 against the data source. If you are not able to find the data source in RSA7, then you need to set-up the update methods, based on the requirement.
1) Direct Delta
2) Queued Delta
3) Unserialised V3 Update
Once it is done, Delete the Previous Initilisation, again perform the Re-Init With Out data and now schedule the Delta Data Loads
Hope this may Help you.
Thanks
PT

Job is taking too much time during Delta loads

hi
when i tried to extract Delta records from R3 for Standard Extractor 0FI_GL_4 it is taking 46 mins while there are very less no. of delta records(193 records only).
PFA the R3 Job log. the major time is taking in calling the Customer enhacement BW_BTE_CALL_BW204010_E.
please let me know why this is taking too much time.
06:10:16 4 LUWs confirmed and 4 LUWs to be deleted with FB RSC2_QOUT_CONFIRM_DATA
06:56:46 Call up of customer enhancement BW_BTE_CALL_BW204010_E (BTE) with 193 records
06:56:46 Result of customer enhancement: 193 records
06:56:46 Call up of customer enhancement EXIT_SAPLRSAP_001 (CMOD) with 193 records
06:56:46 Result of customer enhancement: 193 records
06:56:46 Asynchronous sending of data package 1 in task 0002 (1 parallel tasks)
06:56:47 IDOC: InfoIDOC 2, IDOC no. 121289649, duration 00:00:00
06:56:47 IDOC: Begin 09.05.2011 06:10:15, end 09.05.2011 06:10:15
06:56:48 Asynchronous sending of InfoIDOCs 3 in task 0003 (1 parallel tasks)
06:56:48 Through selection conditions, 0 records filtered out in total
06:56:48 IDOC: InfoIDOC 3, IDOC no. 121289686, duration 00:00:00
06:56:48 IDOC: Begin 09.05.2011 06:56:48, end 09.05.2011 06:56:48
06:56:54 tRFC: Data package 1, TID = 3547D5D96D2C4DC7740F217E, duration 00:00:07, ARFCSTATE =
06:56:54 tRFC: Begin 09.05.2011 06:56:47, end 09.05.2011 06:56:54
06:56:55 Synchronous sending of InfoIDOCs 4 (0 parallel tasks)
06:56:55 IDOC: InfoIDOC 4, IDOC no. 121289687, duration 00:00:00
06:56:55 IDOC: Begin 09.05.2011 06:56:55, end 09.05.2011 06:56:55
06:56:55 Job finished
Regards
Atul

Hi Atul,
Have you written any customer exit code . If yes check for the optimization for it .
Kind Regards,
Ashutosh Singh

Error during delta load for bulk upload data object

Hi All,
I am getting the following message in the backend integration logs for one of the bulk enabled data object.
Error message:
Unable to find parent record for record of node 'CHILD2'.
Message : SMMWKGN class 005.
Does anyone know about this error.
I have defined the the fields as key in child nodes which are defined as key fields in Header structure?
Also while executing the getlist and getdetail i am able to see all the related data?
Can somebody suggest?
Thanks
Dev

found out the problem. Solved

Delta load problem in 2lis_04_p_comp

Hi
I am using data sources 2lis_04_p_comp and 2lis_04_p_matnr in my report. When I am doing full load , data is matching with R3 but during delta load , 2lis_04_p_comp is showing incorrect data.
WHEN I RUN THE DELTA REQUEST,FOR SAME ORDER NUMBER,WE GET MORE NUMBER OF RECORDS WITH THE EVENT VALUES PA,PB,PC,PD AND PF.
sO AFTER RUNNING DELTA,THE OUTPUT GI QUANTITY and GI Value FROM THE REPORT DOES NOT TALLY WITH THE R/3 DATA.
I am using cube 0pp_c05 where these GI quantities and GI Value add up giving wrong result
Please help
Regards
Megha

Hi All,
For setup table filling for PP datasources having some sequence to follow. You can see in the note 585960. The workaround given by SAP is to deactivate the MATNR data source and fill the tables and then activate and fill the MATNR stuff.
There are some local issues regarding this activation and deactivation things, because it needs lot of permissions and procedures.
Please go as per the note procedure.
Assign points if helful.
Regards
Amit

Why can't see enhanced data by delta loading

Hi Pros,
I have done enhancement in 0CA_TS_IS_1, which constantly retrieve information and append them into data package, then I tested it in RSA3, successfully. also I load data from this 0CA_TS_IS_1 by full loading, it successes. but when I load data using existing delta load infopackage, there is no expected data loaded. ( ie. there is no enhanced data appended).

Put a debug breakpoint in your code, and then run RSA3 again in Update Mode delta (D).
Check if the debugger goes into your breakpoint - it should.
If it doesn't , it may be your user exit is not activated correctly, or there is some clause in your code (check for IF-ELSEIFs) that bypasses the customer exit only during delta loads.
I hope you did the user exit correctly, because these things normally do not happen at all when implemented correctly. There are a 101 different things that could've gone wrong when these things happen. My advice is to check and re-check your user exit code in the program ZXRSAU01 to make sure everything is setup correctly.

Getting short dump "TSV_TNEW_PAGE_ALLOC_FAILED" during the load

Hi Experts,
I am getting short dump "TSV_TNEW_PAGE_ALLOC_FAILED" when loading data one ODS to Two cubes in 3.1 system . we have only 12000 records to load. this load is delta update. daily we loaded 14000 record from this load but today we are getting short dump.
Short Dump : TSV_TNEW_PAGE_ALLOC_FAILED
Description : No storage space available for extending the internal table.we attempted to extend an internal table, but the required space wasnot available.
Thanks

This is a memory issue whereby an internal table requires more memory than what is currently available. If you're executing this during processing of other ETL, then your memory is being consumed by all of the processes and you would need to change your schedule as to balance the load better.
Another possibility is that you have an extremely inefficient SQL statement in a routine that is causing the memory to be overly consumed. Even though the output may be less than average, there is a possiblity that it's reading more data in a SELECT statement and therefore requires more memory than normal.
Finally, have you Basis team look at this issue to determine if there's anything that they can do to resolve it.

Short dump error for delta load to 0CFM_C10 via 0CFM_DELTA_POSITIONS flow

hi all,
i am getting short dump error for delta load to 0CFM_C10 via 0CFM_DELTA_POSITIONS flow.
not able to figure out the actual issue and how to solve it.
can anyone suggest?
below is the details of the short dump
Short text
    Exception condition "UNKNOWN_TRANSCAT" raised.
What happened?
    The current ABAP/4 program encountered an unexpected
    situation.
What can you do?
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
Error analysis
    A RAISE statement in the program "CL_SERVICE_TRG================CP" raised the
     exception
    condition "UNKNOWN_TRANSCAT".
    Since the exception was not intercepted by a superior
    program, processing was terminated.
    Short description of exception condition:
    For detailed documentation of the exception condition, use
    Transaction SE37 (Function Library). You can take the called
    function module from the display of active calls.
How to correct the error
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "RAISE_EXCEPTION" " "
    "CL_SERVICE_TRG================CP" or "CL_SERVICE_TRG================CM003"
    "SORT_TRANSACTIONS"
    or
    "CL_SERVICE_TRG================CP" "UNKNOWN_TRANSCAT"
    or
    "SBIE0001 " "UNKNOWN_TRANSCAT"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
       To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
       Display the system log by calling transaction SM21.
       Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
       In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.

Hi,
It seems like some routine are there and check your rotines , transformation etc.
Regards
sivaraju

Delta load failing with dump TSV_TNEW_PAGE_ALLOC_FAILED

Hi,
When we are loading BW statistics delta load, the load is failing with error "Job in source system terminated --> Request is set to red." and its giving short dump with "TSV_TNEW_PAGE_ALLOC_FAILED".
I have already gone through Forum and changed package size also. But could not solve the problem.
We are using 3.5 version, Could you please post your thought ASAP.
Regards
Satya

Hi there,
Yes that dump is lack of memory...
So probably your package has too many records to be processed, especially if you have code in start routine or end routine or something like that, the process for each package might take too long and fails with out of memory.
Try in fact change the package size to a smaller size, so fewer records are processed in each package.
Diogo.

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.

Repair request for Delta load? Orders missing in Billing line Items

Hi
I am using BW 3.5; Some Orders are missing in BW for Billing line item reports (2LIS_13_VDITM) according to the users.
The report is based on Cube directly, ODS is not used. I planned to do a repair full request for this month's data so as to get the missing orders.
Could you please advice me on correct procedure to do that? Delta loads runs every day and todays delta is completed.
Thanks and BR
P.B

While it's usually recommended to execute setups during "quiet time", it's not required. Especially in this case. Since you're going to be restricting the setup to only extract a range of Billing Documents that are representative of the dates of data missing (or purely the identified missing documents), there is no need to wait for "quiet time" because you'll pick up the data either in your Full Repair extract or in the delta extract. Depending on how the target InfoProvider for this data is setup (cumulative v. non-cumulative), you may have to look out for duplicate data.
My recommendation would be to run your setup for only those documents that have been identified as missing. That way, you're limiting the amount of data that's required to be extracted to the setup table and then into BW, but also will remove any risk of duplicate data in your target InfoProviders.

Loading through Process Chains 2 Delta Loads and 1 Full Load (ODS to Cube).

Dear All,
I am loading through Process chains with 2 Delta Loads and 1 Full load from ODS to Cube in 3.5. Am in the development process.
My loading process is:
Start - 2 Delta Loads - 1 Full Load - ODS Activation - Delete Index - Further Update - Delete overlapping requests from infocube - Creating Index.
My question is:
When am loading for the first am getting some data and for the next load i should get as Zero as there is no data for the next load but am getting same no of records for the next load. May be it is taking data from full upload, i guess. Please, guide me.
Krishna.

Hi,
The reason you are getting the same no. of records is as you said (Full load), after running the delta you got all the changed records but after those two delta's again you have a full load step which will pick whole of the data all over again.
The reason you are getting same no. of records is:
1> You are running the chain for the first time.
2> You ran this delta ip's for the first time, as such while initializing these deltas you might have choosen "Initialization without data transfer", as such now when you ran these deltas for the first time they picked whole of the data.Running a full load after that will also pick the same no. of records too.
If the two delats you are talking are one after another then is say u got the data because of some changes, since you are loading for a single ods to a cube both your delta and full will pick same "For the first time " during data marting, for they have the same data source(ODS).
Hope fully this will serve your purpose and will be expedite.
Thax & Regards
Vaibhave Sharma
Edited by: Vaibhave Sharma on Sep 3, 2008 10:28 PM

Delta load of customer from R/3 (ECC5.0) to CRM5.0

We have done an initial load of customers from ECC to CRM (R3AS). A change is done on a customer in ECC. I expect the changes to be reflected in CRM as a delta load. I do not see the changes. What am I missing?
All responses are appreciated and will be rewarded.

Hi Mani,
Here are some clues on how to proceed with processing of incomplete or failed BP deltas:
First of all you have to note that during the initial download, no delta download can occur. In particular, no delta download of customers occurs if the initial download of materials occurs at the same time. This is because the material download depends on the customer download.
During the delta download, the CRM system uses the inbound queues R3AD_CUSTOME<nnnnnnnnnn> where <nnnnnnnnnn> corresponds to the customer number in the R/3 system. If an error occurs during the download, the inbound queue for this customer is stopped. You can see the error messages in the flow trace. For the delta download, you have the option to use Transaction CRMM_BUPA_MAP for the error analysis. If you enter the customer and press Enter here, you can display the business partner number for a customer and all open BDocs (that is, those which contain errors or are being processed). To do this, you only have to click the 'Queues and BDocs during download' pushbutton. The system issues an overview of the queue and the open BDocs for this customer and in particular, you can 'look into' the BDoc. As a result, you return to the flow trace and you can display the error messages which occured as described above. During the delta download, you have the option to send the same BDoc again. This is useful if you can simply solve the problem by correcting Customizing in the CRM system. To do this, you simply click the corresponding icon in the flow trace (currently, this is the second icon from the left).
If you have to correct the error in the R/3 system, you have to delete the existing BDoc since it cannot be processed further. As a result, the inbound queue in the CRM system is released again. In this case, you are recommended to delete all existing open BDocs and to make the changes in the R/3 system.
If inconsistencies occur between the R/3 system and the CRM system, you can start a request for the customer. To do this, click the 'Get customer from the R/3 system' pushbutton. This starts a request which uses the inbound queue R3AR_CUSTOMER. Process possible errors as during an initial download.
If you still have problems and don't know how to fix, please post more specific information from the BDoc queue, such as what error message you are getting. It helps us better identify the problem.
Regards,
Rahul
PS. Please award points if it helps!
PPS. For future reference: this info was found in note 362621: Error drng data exchange customer<->business partner

Dump during delta load

Similar Messages

Maybe you are looking for