Dump "DBSQL_DBSL_CONVERSION_ERROR" in select statement for AUFM Table

[KarthikeyanN]

Hi All,

We are getting the ABAP Runtime dump "DBSQL_DBSL_CONVERSION_ERROR" for the select statement on AUFM Table written in the custom program. Attached the select statement here.select.png

SELECT mblnr " Material Document Number
mjahr " Fiscal year
aufnr " Order Number
werks " Plant
matnr " Material Number
menge " Quantity
meins " Unit of Measure
bwart " Movement type
FROM aufm
INTO TABLE lt_mseg_temp
FOR ALL ENTRIES IN lt_temp
WHERE aufnr EQ lt_temp-aufnr
AND bwart EQ lc_101 "Defect#12426
OR bwart EQ lc_102 "Defect#12426
AND werks EQ lt_temp-werks
AND matnr EQ lt_temp-matnr.

Dump screen is also uploaded here.dump.png

Types for this internal tabletypes.png

This is bit urgent getting many dumps in production.

Response is appreciated.

Thanks

[matt]

Better to post text of code rather than just images. And I don't see the point of your dump picture, since it's the same as your code picture, effectively.

If this is standard SAP code, and it's "urgent", then raise a priority 1 message at support.sap.com

[KarthikeyanN]

Category ABAP programming errorRuntime Errors DBSQL_DBSL_CONVERSION_ERRORExcept. CX_SY_OPEN_SQL_DBABAP Program ZPPPRR00018Application Component Not assignedDate and Time 07/26/2018 11:50:01Short TextConversion not possible.What happened?Error in the ABAP application program.The current ABAP program "ZPPPRR00018" had to be terminated because it found astatement that could not be executed.What can I do?Note which actions and entries caused the error to occur.Consult your SAP administrator.Using transaction ST22 for ABAP dump analysis, you can view, manage,and retain termination messages for longer periods.Using Transaction ST22 for ABAP Dump Analysis, you can lookat and manage termination messages, and you can alsokeep them for a long time.Error analysisAn exception has occurred which is explained in more detail below. Theexception is assigned to class 'CX_SY_OPEN_SQL_DB' and was not caught inprocedure"GET_AUFM" "(FORM)", nor was it propagated by a RAISING clause.Since the caller of the procedure could not have anticipated thisexception, the current program was terminated.The reason for the exception is:During a SELECT access, the read data could not be placed in the targetfield.Either the conversion is not supported for the target field type, thetarget field is too small to take the value, or the data does not havethe required format for the target field.How to correct the errorThe exception must either be prevented, caught in procedure "GET_AUFM""(FORM)", orthe possibility of it occurring must be declared in the RAISING clausein the procedure.To prevent the exception, note the following:Navigate to the "Database Interface Information" node.This provides details about the type and length of the database field,and the ABAP field where this field should be imported into.If the error occurs in a non-modfied SAP program, you might be able tofind a solution in the SAP Notes system. If you have access to the SAPNotes system, check there first using the following keywords:"DBSQL_DBSL_CONVERSION_ERROR" CX_SY_OPEN_SQL_DB"ZPPPRR00018" bzw. ZPPPRR00018_F01"GET_AUFM"

[matt]

Not exactly making it easy for people to help you! How about formatting a bit so that it's readable? Anyway, which part of the following are you having difficulty with?

The reason for the exception is:

During a SELECT access, the read data could not be placed in the target field. Either the conversion is not supported for the target field type, the target field is too small to take the value, or the data does not have the required format for the target field.

How to correct the error

The exception must either be prevented, caught in procedure "GET_AUFM""(FORM)", orthe possibility of it occurring must be declared in the RAISING clausein the procedure.To prevent the exception, note the following:Navigate to the "Database Interface Information" node. This provides details about the type and length of the database field,and the ABAP field where this field should be imported into.

[raymond_giuseppi]

1. Look at the OR in the WHERE clause, an reflect on use of parentheses in logical expression
2. Check field definitions of your internal table, is type 'ZMENGE' compatible with 'MENGE_D'
3. No ABAPer on site, they have fled?
4. No test in quality or an error in sequence of imports or impact of another change, check recent import log?

[KarthikeyanN]

we are getting dump for few scenarios and its working fine for couple of scenarios. can you help us further

[raymond_giuseppi]

Did you look at

• ZMENGE definition (with SE11 data-element) vs MENGE_D (with SE11 data-element) check length values
• recent import (STMS, log)

As I'm not able to connect to your system (and not paid for this...) no, you have to look by yourself (no crystal ball available) much too many options (also if you correctly posted the source code, the where clause is obviously wrong due to the OR without parentheses in the middle of a series of AND...)

[horst_keller]

Follow the rules

https://help.sap.com/http.svc/rc/abapdocu_752_index_htm/7.52/en-US/index.htm?file=abenselect_into_co...

[roberto_forti]

Hi,

Consider reading Quantity Fields from SAP documentation as well as improve abap code implementing catch exception to CX_SY_OPEN_SQL_DB.

Problem is menge type zmenge from ty_mseg.

Check it again and implement one type which It will works for all scenarios.

Regards,