cancel
Showing results for 
Search instead for 
Did you mean: 

Query gives ASSIGN_TYPE_CONFLICT error while execution.

Former Member
0 Kudos

Hi,

I am using BEX 3.5 and I get the following error when I excecute a query built on a virtual provider.

Runtime Errors ASSIGN_TYPE_CONFLICT

Date and Time 04.02.2009 07:26:14

Short text

Type conflict with ASSIGN in program "GP46IJU3DHHM7BMOVYK5C25VPU9".

What happened?

Error in the ABAP Application Program

The current ABAP program "GP46IJU3DHHM7BMOVYK5C25VPU9" 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.

Information on where terminated

Termination occurred in the ABAP program "GP46IJU3DHHM7BMOVYK5C25VPU9" - in

"EXECUTE".

The main program was "SAPMSSY1 ".

In the source code you have the termination point in line 345

of the (Include) program "GP46IJU3DHHM7BMOVYK5C25VPU9".

Line SourceCde

315 currrule-tranid = '0AUBIMFV5RTEC7OMK4S551BJENDOPH2N'.

316 currrule-progid = '46IJU3DHHM7BMOVYK5C25VPU9'.

317 currrule-version = '0'.

318

319 call method cl_rstran_runtime_exe=>get_suppressed_rules

320 EXPORTING

321 i_tranid = currrule-tranid

322 i_r_data = e_r_outbound

323 IMPORTING

324 e_s_suppressed_rules = lssupp.

325

326 * set attributs

327 p_check_master_data_exist = i_master_data_exist.

328 p_r_request = i_r_request.

329

330

331 * ==== Debugging ====

332 * Breakpoint after start routine

333 if i_r_trfn_cmd is bound.

334 READ TABLE i_r_trfn_cmd->n_th_bp

335 TRANSPORTING NO FIELDS

336 WITH TABLE KEY bpid = 3

337 datapid = i_r_inbound->n_datapakid.

338 IF sy-subrc = 0.

339 BREAK-POINT. "#EC NOBREAK

340 ENDIF.

341 endif.

342

343 * ==== 2. process data package

344 i_r_log->add_substep( 'RULES' ).

>>>> LOOP AT <_yt_SC_1> assigning <_ys_SC_1>.

346

347 CLEAR:

348 G1,

349 ltmsg_rec,

350 ltmsg.

351 currrule-record = l_recno_SC_1 = <_ys_SC_1>-record.

352 TRY.

353 CALL METHOD i_r_log->verify_record

354 EXPORTING

355 i_segid = 0001

356 i_record = <_ys_SC_1>-record

357 RECEIVING

358 r_skip = _skip

359 EXCEPTIONS

360 TOO_MANY_ERRORS = 1

361 NOT_IN_CROSSTAB = 2

362 others = 3.

363 IF sy-subrc <> 0.

364 CALL FUNCTION 'RS_SYMESSAGE_TO_EXCEPTION'

Please can someone help me with this?

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Is there any exit or code wrtitten for this query?

Regards

Bibhu

Former Member
0 Kudos

Hi Anil,

I am facing same Runtime error in ST22.

Can you help me out with solution.

Thanks n Regards.

Chetna