on 07-13-2012 12:56 PM
Hi all,
I am getting an ABAP dump ASSIGN_TYPE_CONFLICT.
Please find the details below.
Category ABAP Programming Error
Runtime Errors ASSIGN_TYPE_CONFLICT
ABAP Program SAPLSVCM
Application Component BC-CUS-TOL-TME
Date and Time 12.07.2012 09:28:32
Short text: Type conflict with ASSIGN in program "SAPLSVCM".
What happened? Error in the ABAP Application Program The current ABAP program "SAPLSVCM" had to be terminated because it has come across a statement that unfortunately cannot be executed.
Error analysis: You attempted to assign a field to a typed field symbol, but the field does not have the required type.
How to correct the error |
Adapt the type of the field symbol to the type of the field or use an |
untyped field symbol or use the "CASTING" addition. |
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: |
"ASSIGN_TYPE_CONFLICT" " " |
"SAPLSVCM" or "LSVCMU08" |
"VIEWCLUSTER_CHECK_MASTER_ENTRY" |
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. |
System environment |
SAP Release..... 702 |
SAP Basis Level. 0011 |
Application server... "GVAR3X04" |
Network address...... "10.69.48.9" |
Operating system..... "Windows NT" |
Release.............. "6.1" |
Hardware type........ "24x AMD64 Level" |
Character length.... 16 Bits |
Pointer length....... 64 Bits |
Work process number.. 3 |
Shortdump setting.... "full" |
Database server... "GVAR3X04\SB2" |
Database type..... "MSSQL" |
Database name..... "SB2" |
Database user ID.. "sb2" |
Terminal.......... "WPET-W7E-P19004" |
Char.set.... "C" |
SAP kernel....... 720 |
created (date)... "Feb 20 2012 19:16:38" |
create on........ "NT 5.2 3790 S x86 MS VC++ 14.00" |
Database version. "SQL_Server_9.00 " |
Patch level. 200 |
Patch text.. " " |
Database............. "MSSQL 9.00.2047 or higher" |
SAP database version. 720 |
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows |
NT 6.0, Windows NT 6.1, Windows NT 6.2" |
Memory consumption |
Roll.... 0 |
EM...... 25138752 |
Heap.... 0 |
Page.... 65536 |
MM Used. 15182704 |
MM Free. 1573120 |
Kindly help me on this error.
Thanks in advance.
Srikanth
Hi,
When you face this runtime error?
Can you also please check the following SAP notes..may be it will help for you.
Note 1561539 - Runtime error ASSIGN_TYPE_CONFLICT for zero suppression
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is SAP standard coding issue. I suggest you open an OSS message . In the meantime try updating the kernel or at-least the dw* package along with the DBSL.
Regards
Ratnajit
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
10 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.