on 07-25-2012 5:58 PM
Runtime Errors ASSIGN_TYPE_CONFLICT
Date and Time 06.07.2012 13:31:07
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|Short text |
| Type conflict with ASSIGN in program "GP4NELZAC37D24EXBID921O7HA3". |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|What happened? |
| Error in the ABAP Application Program |
| |
| The current ABAP program "GP4NELZAC37D24EXBID921O7HA3" 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 |
| 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" " " |
| "GP4NELZAC37D24EXBID921O7HA3" or "GP4NELZAC37D24EXBID921O7HA3" |
| "WRITE_DATA_CHAVL" |
| |
| 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 701 |
| |
| Application server... "sape301" |
| Network address...... "10.26.111.59" |
| Operating system..... "AIX" |
| Release.............. "6.1" |
| Hardware type........ "00CE55FA4C00" |
| Character length.... 16 Bits |
| Pointer length....... 64 Bits |
| Work process number.. 46 |
| Shortdump setting.... "full" |
| |
| Database server... "sape301" |
| Database type..... "ORACLE" |
| Database name..... "EP1" |
| Database user ID.. "SAPSR3" |
| |
| Terminal.......... " " |
| |
| Char.set.... "C" |
| |
| SAP kernel....... 701 |
| created (date)... "Jul 3 2011 21:35:33" |
| create on........ "AIX 2 5 00CB5A5B4C00" |
| Database version. "OCI_102 (10.2.0.2.0) " |
| |
| Patch level. 150 |
| Patch text.. " " |
| |
| Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*" |
| SAP database version. 701 |
| Operating system..... "AIX 1 5, AIX 2 5, AIX 3 5, AIX 1 6, AIX 1 7" |
| |
| Memory consumption |
| Roll.... 16192 |
| EM...... 117369216 |
| Heap.... 0 |
| Page.... 24576 |
| MM Used. 77360912 |
| MM Free. 31623408 |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|User and Transaction |
| |
| Client.............. 700 |
| User................ "JAVIERF01TRI" |
| Language key........ "E" |
| Transaction......... " " |
| Transactions ID..... "4FF6767468653BA0E10080000A1A6F3B" |
| |
| Program............. "GP4NELZAC37D24EXBID921O7HA3" |
| Screen.............. "SAPMSSY0 1000" |
| Screen line......... 6 |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|Information on where terminated |
| Termination occurred in the ABAP program "GP4NELZAC37D24EXBID921O7HA3" - in |
| "WRITE_DATA_CHAVL". |
| The main program was "RSBATCH_EXECUTE_PROZESS ". |
| |
| In the source code you have the termination point in line 586 |
| of the (Include) program "GP4NELZAC37D24EXBID921O7HA3". |
| The program "GP4NELZAC37D24EXBID921O7HA3" was started as a background job. |
| Job Name....... "BIDTPR_387320_1" |
| Job Initiator.. "JAVIERF01TRI" |
| Job Number..... 13310400 |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|Source Code Extract |
----------------------------------------------------------------------------------------------------
|Line |SourceCde |
----------------------------------------------------------------------------------------------------
| 556| i_t_tabix TYPE gt_t_tabix |
| 557| i_tab_val_init TYPE rs_bool |
| 558| i_pkg_id TYPE rssid |
| 559| CHANGING |
| 560| c_subrc TYPE i. |
| 561| |
| 562| DATA: |
| 563| l_recno LIKE sy-tabix, |
| 564| l_erridx LIKE sy-tabix, |
| 565| l_errnumbers TYPE i, |
| 566| l_nexterr LIKE sy-tabix, |
| 567| l_subrc1 LIKE sy-subrc, |
| 568| l_pdimid TYPE rssid. |
| 569| |
| 570| FIELD-SYMBOLS: |
| 571| <l_t_cubeval> TYPE g_t_cubecha, |
| 572| <l_s_cubecha> TYPE g_s_cubecha. |
| 573| |
| 574| if i_pkg_id <> 0. |
| 575|* bug, cube is not delta write enabled... |
| 576| cl_rsdd_cube_writer=>monitor_log( |
| 577| i_recno = 0 |
| 578| i_msgid = 'DBMAN' |
| 579| i_msgno = '971' |
| 580| i_errtp = '' |
| 581| i_errnm = '' |
| 582| i_fieldnm = '' ). |
| 583| c_subrc = cl_rsdd_cube_writer=>nc_error-no_continue. |
| 584| return. |
| 585| endif. |
|>>>>>| |
| 587| |
| 588| ASSIGN i_r_data->* TO <l_t_cubeval>. |
| 589| g_tab_val_init = i_tab_val_init. |
| 590| |
| 591| CHECK LINES( <l_t_cubeval> ) > 0. |
| 592| |
| 593| l_errnumbers = LINES( i_t_tabix ). |
| 594| |
| 595|******** Derive DIMID of packagedimension ******** |
| 596| IF l_pdimid IS INITIAL. |
| 597| cl_rsdd_cube_writer=>read_pdimid( |
| 598| EXPORTING |
| 599| i_infocube = 'ZSCRECB3E' |
| 600| i_trexaggr = i_trexaggr |
| 601| i_simulation = i_simulation |
| 602| i_requid = i_req_sid |
| 603| i_refpoint = g_tab_val_init |
| 604| IMPORTING |
| 605| e_pdimid = l_pdimid |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|Contents of system fields |
----------------------------------------------------------------------------------------------------
|Name |Val. |
----------------------------------------------------------------------------------------------------
|SY-SUBRC|0 |
|SY-INDEX|3 |
|SY-TABIX|0 |
|SY-DBCNT|1 |
|SY-FDPOS|1 |
|SY-LSIND|0 |
|SY-PAGNO|0 |
|SY-LINNO|1 |
|SY-COLNO|1 |
|SY-PFKEY| |
|SY-UCOMM| |
|SY-TITLE|Execute Batch Process |
|SY-MSGTY|S |
|SY-MSGID|RSDA |
|SY-MSGNO|230 |
|SY-MSGV1|ZSCRECB3E |
|SY-MSGV2| |
|SY-MSGV3| |
|SY-MSGV4| |
|SY-MODNO|0 |
|SY-DATUM|20120706 |
|SY-UZEIT|133107 |
|SY-XPROG|SAPCNVE |
|SY-XFORM|CONVERSION_EXIT |
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|Active Calls/Events |
----------------------------------------------------------------------------------------------------
|No. Ty. Program Include Line |
| Name |
----------------------------------------------------------------------------------------------------
| 7 FORM GP4NELZAC37D24EXBID921O7HA3 GP4NELZAC37D24EXBID921O7HA3 586 |
| WRITE_DATA_CHAVL |
| 6 METHOD CL_RSDD_CUBE_WRITER===========CP CL_RSDD_CUBE_WRITER===========CM00A 156 |
| CL_RSDD_CUBE_WRITER=>WRITE_DTP |
| 5 METHOD CL_RSDD_U_CUBE================CP CL_RSDD_U_CUBE================CM005 33 |
| CL_RSDD_U_CUBE=>IF_RSBK_CMD_U~RECEIVE_DATAPACKAGE |
| 4 METHOD CL_RSBK_PROCESS===============CP CL_RSBK_PROCESS===============CM00Q 130 |
| CL_RSBK_PROCESS=>PROCESS_REQUEST |
| 3 METHOD CL_RSBK_PROCESS===============CP CL_RSBK_PROCESS===============CM002 13 |
| CL_RSBK_PROCESS=>IF_RSBATCH_EXECUTE~EXECUTE |
| 2 FUNCTION SAPLRSBATCH LRSBATCHU13 429 |
| RSBATCH_EXECUTE_PROCESS |
| 1 EVENT RSBATCH_EXECUTE_PROZESS RSBATCH_EXECUTE_PROZESS 359 |
| START-OF-SELECTION |
----------------------------------------------------------------------------------------------------
Please help by suggesting probable cause of this issue and solution.
Kindly let me know for any other required details, if any.
Many thanks in advance.
Hello!
if the symptom occurs in a BW instance during a DTP execution, then there is an Sap Oss note providing the solution:
Still the note does not explain the root causes. In our case we have this error after a transformation in imported and the dtp is executed the first time. The provided solution fixes the error. In our case the repeat of the DTP is also successfull.
Regards,
Alessandro
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Did you do any research yourself before dumping dumps? What did you find out so far?
Thomas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Please exlplain the context.
Regards
Clemens
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
108 | |
12 | |
11 | |
6 | |
5 | |
4 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.