Caller 09 contains an error message at PSA

[Former Member]

When i runnign infopackage for 2LIS_05_QVUDN, till 1 crore records it is pulling fine, once it crossed 1 crore it is throught the below error:

Error message from the source system

Diagnosis

An error occurred in the source system.

System Response

Caller 09 contains an error message.

Further analysis:

The error occurred in Extractor .

Refer to the error message.

Procedure

How you remove the error depends on the error message.

Note

If the source system is a Client Workstation, then it is possible that the file that you wanted to load was being edited at the time of the data request. Make sure that the file is in the specified directory, that it is not being processed at the moment, and restart the request.

Can some one please guide me on this...

Thanks,

Malathi

[former_member182516]

Hi Malathi,

Check the below points

1) Check the source system job log why the job got terminated.

2) check for the short dumps in Tcode ST22 in the source system. and try to analyse the dump and post the dump details.

Regards

KP

[former_member210676]

Hi Malathi,

Caller 9 errors are due to job termination in source system.

Can you check the job log in source system to see where it failed?

Yours,

Hari ...

[Former Member]

Hi Koralla,

Please check the details tabs ,of monitor tab in IP .

Select environment -> job overview ->  source system  as given screen shot.

In environment, you can find reason for extraction failure.

Regards,

Anand Mehrotra.

[Former Member]

hi,

In job log it is displaying the following error:

Error  When importing the object "MC05QV0UDN_TAB", the component 80 in the dataset

had a different length from the corresponding component of the

target object in the program "SAPLMCEX".

But in my program i coudnt find "MC05QV0UDN_TAB" this object..

and the dump details are:

Error analysis
    A RAISE statement in the program "CL_GUI_CFW====================CP" raised the
     exception
    condition "CNTL_ERROR".
    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.
    -"

Please guide me further..

thanks.

[former_member182516]

Hi Malathi,

Simply posting the half of the log will not be helpful to provide the inputs. Can you please post the Short dump exception and dump name as well. also can you post more details of short dump.

Regards

KP

[Former Member]

Hi KP,

Kindly ignore my previous post.

Please find the details below:

Category               ABAP Programming Error
Runtime Errors         CONNE_IMPORT_WRONG_COMP_LENG
Except.                CX_SY_IMPORT_MISMATCH_ERROR
ABAP Program           SAPLMCEX
Application Component  LO-LIS
Date and Time          20.09.2012 11:36:08
	Short text
	Error when attempting to IMPORT object "MC05QV0UDN_TAB".
	What happened?
	Error in the ABAP Application Program
	The current ABAP program "SAPLMCEX" had to be terminated because it has
	come across a statement that unfortunately cannot be executed.
	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
	An exception occurred that is explained in detail below.
	The exception, which is assigned to class 'CX_SY_IMPORT_MISMATCH_ERROR', was
	not caught in
	procedure "MCEX_BW_LO_API" "(FUNCTION)", nor was it propagated by a RAISING
	clause.
	Since the caller of the procedure could not have anticipated that the
	exception would occur, the current program is terminated.
	The reason for the exception is:
	When importing the object "MC05QV0UDN_TAB", the component 80 in the dataset
	had a different length from the corresponding component of the
	target object in the program "SAPLMCEX".
	The length is 2 in the dataset, but 36 in the program.
	How to correct the error
	Try to find out why the length of the object should be 2.
	There are various possible options:
	1. The length of the imported field has changed in the Data Dictionary.
	Make sure that the length of the imported field matches the length
	of the field in the Data Dictionary.
	If the data cannot be restored from another source, the data must be
	read by the 'old' structure, converted und again eported with the new
	structure, so that future IMPORTs will always function with the new
	structure.
	2. A new program version is active, which no longer fits the dataset.
	Try to solve the error generating the program "SAPLMCEX" again. This
	works as follows: Select transaction SE38 in the SAP system. Enter
	the program name "SAPLMCEX". Then activate the function 'Generate'.
	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:
	"CONNE_IMPORT_WRONG_COMP_LENG" "CX_SY_IMPORT_MISMATCH_ERROR"
	"SAPLMCEX" or "LMCEXU06"
	"MCEX_BW_LO_API"
	The exception must either be prevented, caught within proedure
	"MCEX_BW_LO_API" "(FUNCTION)", or its possible occurrence must be declared in
	the
	RAISING clause of the procedure.

Information on where terminated
Termination occurred in the ABAP program "SAPLMCEX" - in "MCEX_BW_LO_API".
The main program was "SBIE0001 ".
In the source code you have the termination point in line 246
of the (Include) program "LMCEXU06".
The program "SAPLMCEX" was started as a background job.
Job Name....... "BIREQU_DDP0IOOA2NPI93LDLX1D1A8UW"
Job Number..... 10281900
The termination is caused because exception "CX_SY_IMPORT_MISMATCH_ERROR"
occurred in
procedure "MCEX_BW_LO_API" "(FUNCTION)", but it was neither handled locally nor
declared
in the RAISING clause of its signature.
The procedure is in program "SAPLMCEX "; its source code begins in line
1 of the (Include program "LMCEXU06 ".
Source Code Extract
Line		SourceCde
216		ENHANCEMENT-POINT EHP603_LMCEXU06_01 SPOTS ES_SAPLMCEX.
217
218
219		ENHANCEMENT-POINT EHP_MCEX_BW_LO_API_002 SPOTS ES_SAPLMCEX.
220
221		ENHANCEMENT-SECTION     EHP_MCEX_BW_LO_API_001 SPOTS ES_SAPLMCEX.
222		CASE s_estruc.
223		*           extractstruc   internal table    setup table
224		*-- MM-PUR
225		sel 'MC02M_0HDR'   mc02m_0hdr_tab    mc02m_0hdrsetup.
226		sel 'MC02M_0ITM'   mc02m_0itm_tab    mc02m_0itmsetup.
227		sel 'MC02M_0SCL'   mc02m_0scl_tab    mc02m_0sclsetup.
228		sel 'MC02M_0SGR'   mc02m_0sgr_tab    mc02m_0sgrsetup.
229		sel 'MC02M_0SCN'   mc02m_0scn_tab    mc02m_0scnsetup.
230		sel 'MC02M_0CGR'   mc02m_0cgr_tab    mc02m_0cgrsetup.
231		sel 'MC02M_0ACC'   mc02m_0acc_tab    mc02m_0accsetup.
232		*-- Application '03' (Inventory Management)
233		sel 'MC03BF0'      mc03bf0_tab       mc03bf0setup.
234		sel 'MC03BX0'      mc03bx0_tab       mc03bx0setup.
235		sel 'MC03UM0'      mc03um0_tab       mc03um0setup.
236		*-- Application '04'
237		sel 'MC04P_0MAT'   mc04p_0mat_tab    mc04p_0matsetup.
238		sel 'MC04P_0ARB'   mc04p_0arb_tab    mc04p_0arbsetup.
239		sel 'MC04P_0COM'   mc04p_0com_tab    mc04p_0comsetup.
240		sel 'MC04PE0MAT'   mc04pe0mat_tab    mc04pe0matsetup.
241		sel 'MC04PE0ARB'   mc04pe0arb_tab    mc04pe0arbsetup.
242		sel 'MC04PE0COM'   mc04pe0com_tab    mc04pe0comsetup.
243		*-- Application '05' (Quality Management)
244		sel 'MC05Q1_0INSP' mc05q1_0insp_tab  mc05q1_inspsetup.
245		sel 'MC05Q2_0INSP' mc05q2_0insp_tab  mc05q2_inspsetup.
>>>>>		sel 'MC05QV0UDN'   mc05qv0udn_tab    mc05qv0udnsetup.
247		sel 'MC05Q00NTF'   mc05q00ntf_tab    mc05q00ntfsetup.
248		sel 'MC05Q00ITM'   mc05q00itm_tab    mc05q00itmsetup.
249		sel 'MC05Q00CSE'   mc05q00cse_tab    mc05q00csesetup.
250		sel 'MC05Q00TSK'   mc05q00tsk_tab    mc05q00tsksetup.
251		sel 'MC05Q00ACT'   mc05q00act_tab    mc05q00actsetup.
252		*-- Application '06' (Invoice verification)
253		sel 'MC06M_0ITM'    mc06m_0itm_tab    mc06m_0itmsetup.
254		*-- Application '08 (Transportation)
255		sel 'MC08TR0FKP' mc08tr0fkp_tab  mc08tr0fkpsetup.
256		sel 'MC08TR0FKZ' mc08tr0fkz_tab  mc08tr0fkzsetup.
257		sel 'MC08TR0TK' mc08tr0tk_tab  mc08tr0tksetup.
258		sel 'MC08TR0TLP' mc08tr0tlp_tab  mc08tr0tlpsetup.
259		sel 'MC08TR0TS' mc08tr0ts_tab  mc08tr0tssetup.
260		*-- Application '11' (Sales)
261		sel 'MC11VA0HDR' mc11va0hdr_tab  mc11va0hdrsetup.
262		sel 'MC11VA0STH' mc11va0sth_tab  mc11va0sthsetup.
263		sel 'MC11VA0ITM' mc11va0itm_tab  mc11va0itmsetup.
264		sel 'MC11VA0STI' mc11va0sti_tab  mc11va0stisetup.
265		sel 'MC11VA0SCL' mc11va0scl_tab  mc11va0sclsetup.

[Former Member]

Your extract structure must have changed(new version of the datasource activated/transported, without clearing the delta queues). Now there is data in your setup tables/extraction queue, that do not correspond to your new extract structure. There are specific notes from SAP that explains how to deal with this issue, but it is very tricky.

My recommendation is to get SAP Support involved. If deleting the setup tables and doing another statistical setup is an option, you may want to consider that.