ASSIGN_TYPE_CONFLICT - /UI2/CL_LPD_UTILS=============CP

Hi All
Is anyone else experiencing a similar issues with the latest launchpad release?
All tiles are working one day, and then a day later they were not. A message would appear suggesting that the app configuration was incorrect.
The Web Inspector in chorme was pointing to an issue with /INTEROP service, which was unable to resolve the application link
My investigation revealed the following:
Several dumps were being registered in ST22.
ASSIGN_TYPE_CONFLICT - /UI2/CL_LPD_UTILS=============CP
After spending some time debugging this class, it turns out that the ABAP may be incorrect... pointing to a type conflict a method that determines if LPD_CUST settings have changed. (I.e. The transaction in SAP GUI where we register new apps). Basically if we keep changing the settings every day it will be fine. Once the settings are over a day old, the class will reach the point in the code that throws the illegal conflict.
Sergio

Hello,
For some reason unknown to me the blob read from the UI2 Cache was 39 chars long while the field symbol assigned to it 40. This was the reason for the runtime error in method HAS_LPD_CHANGED (/UI2/CL_LPD_UTILS), line 105, instruction assign lr_blob->* to <ls_blob>.
I therefore cleaned up the UI2 Cache and retested. It works. To clean up your area in the UI2 Cache call report /UI2/DELETE_CACHE, to clean up all user entries from the cache across all clients call report /UI2/DELETE_CACHE_AFTER_IMP.
I have observed this only in a 7.40 system so far.
Kind regards,
Otto Makris

Similar Messages

ASSIGN_TYPE_CONFLICT

I am getting a fatal error short-dump ASSIGN_TYPE_CONFLICT while executing DTP--- 0CO_OM_WBS_6 -> ODS_01. I have checked all the mappings. All are correct. Even I kept only 2 characterstics and one key figure (that is also constant value), but i got the same error.
I saw the SAP Notes. it advise that the complete design (ODS, transformation, DTP) should be activated. I did it. But I m getting the same error(short-dump).
Short-dump description is as follows:
rror in the ABAP Application Program
The current ABAP program "GP4A1N0850K4T7RMBJJDJ8V7DG9" had to be terminated
because it has
come across a statement that unfortunately cannot be executed.
407
408     rTG_1              = e_r_outbound->get_segment( 001 ).
409     rdtTG_1_dp         = rTG_1->get_empty_table( ).
>>>>     assign rdtTG_1_dp->*         to <_yt_TG_1>.
In above line error is prsent.
Please suggest.
Regards,
Rakesh Jangir

Hi Rakesh,
Do you have written any code in the transformation, if so then please check the code first. If you are calling any finction module in that then please look for the data type's for the import and export parameter's.
Once again activate everything, from cube to DTP and then again run it.
If again get dump then you can also do debugging of the DTP. And track out where the problem is.
Thanks
Dipika

Query gives ASSIGN_TYPE_CONFLICT error while execution.

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?

Hi Anil,
I am facing same Runtime error in ST22.
Can you help me out with solution.
Thanks n Regards.
Chetna

Data Load Short Dump (ABAP/4 processor: ASSIGN_TYPE_CONFLICT)

Hi Experts,
I made few changes to the exisisting data target and transported it to Test system...
Today when i loaded test data i got Dump: ABAP/4 processor: ASSIGN_TYPE_CONFLICT error
Now i need to reactivate the Transformations and DTP's that will fix the error
What is the reason for this error
Thanks

Yes, you are correct, you need to activate your transformation and then DTP to get rid of this error.
The reason for this error is inconsistency b/w transformation and DTP.If you have made any changes to trasforamtion and activated it, then you need to activate the DTP also. If you are loading the data without DTP activation, you will get this error. This is because the DTP is build on transformation.
Thanks...
Shambhu

How to catch a ASSIGN_TYPE_CONFLICT

Gurus.
My badi is working OK, but how can I prevent a short-dump "ASSIGN_TYPE_CONFLICT" if standard "gt_outtab" is changed ?
Casting ?
IF_EX_ME_POHIST_DISP_CUST~OUTTAB_CHANGE
method if_ex_me_pohist_disp_cust~outtab_change.
*-The "original" gt_outtab is defined in program LMMHIPOTOP   -*
*-The type gt_outtab in this method must have the same fields -*
*- ...otherwise: ASSIGN_TYPE_CONFLICT                         -*
types: begin of gt_outtab,
         knumv        type ekbe-knumv,
         srvpos       type ekbe-srvpos,
         ktext1       type ml_esll-ktext1.
include      type mmhipo_mainlist.
types: end of gt_outtab.
field-symbols <gs_outtab> type gt_outtab.
case im_pohist_badi_caller.
    when '0'.
        loop at ct_outtab assigning <gs_outtab>.
          <gs_outtab>-zztracking = 'SE19 + Test + ES_BADI_ME_POHIST'.
        endloop.
endcase.
endmethod.
Please advice.

Hello,
Check if this works:
field-symbols <gs_outtab> LIKE LINE of ct_outtab.
Edited by: Suhas Saha on Jan 3, 2011 5:34 PM:
Since the table CT_OUTTAB is generic (TYPE STANDARD TABLE) you can define the work area as generic & make use of ASSIGN COMPONENT to modify the table:
FIELD-SYMBOLS:
<GS_OUTTAB> TYPE ANY,
<GV_VAL> TYPE ANY.
case im_pohist_badi_caller.
    when '0'.
        loop at ct_outtab assigning <gs_outtab>.
*        <gs_outtab>-zztracking = 'SE19 + Test + ES_BADI_ME_POHIST'.
           ASSIGN COMPONENT 'ZZTRACKING' OF STRUCTURE <GS_OUTTAB> TO <GV_VAL>.
           IF SY-SUBRC = 0.
             <GV_VAL> = 'SE19 + Test + ES_BADI_ME_POHIST'.
           ENDIF.
        endloop.
endcase.
BR,
Suhas

DTP Load Error ( ASSIGN_TYPE_CONFLICT)

Hi All,
I have added new field in Open Hub table then I tried to load the data to Open Hub table.
DTP, I have filter selections based on CALMONTH = 201409
I am getting dump -- ASSIGN_TYPE_CONFLICT
Please help me..!
Thanks
Prakash

Hi Ramanjaneyulu,
Thanks for the reply...
My DTP Load is "FULL" Load with selection CALMONTH = 201409 (OLAP Variable) this is running daily basis in P as per the requirement I have added new field and triggered load but I checked data in cube level same selection I found no data but I am getting error message ASSIGN_TYPE_CONFLICT Dump(ST22)
Please help me
Thanks
Prakash

ABAP/4 processor : ASSIGN_TYPE_CONFLICT

I am recieveing this error message ABAP/4 processor : ASSIGN_TYPE_CONFLICT when i ran a DTP from a flat file datasource
to the data source object (DSO) Can someone help me ?? please...

Hi,
if you have written some own code in transformation please make sure that you are using fields witch have the same data type...
ASSIGN_TYPE_CONFLICT
DTP -ASSIGN_TYPE_CONFLICT
DTP failure
Regards
Andreas

DUmp Erro ASSIGN_TYPE_CONFLICT while loading from DSO to INFOCUBE

HI ALL,
Here i had rquirement of modifying the Tranformation rules and i have done some routine coding for a particular infoobject
and deleted the data from DOS & Cube , then i started Loading to DSO, here i got the sucess for DSO, now i have got the modified data of the particular Infoobject in the DSO,
But i am facing a Dump Error while loading data from DSO to Cube thorugh the DTP .
HEre is the Error "ASSIGN_TYPE_CONFLICT" which i see in ST22.
Plz,
Thanks in Advance,
sravan

HI,
When i started the load for the first time i got he same error, so i have activated the DTP and laoded it again,
then i faced the same problem,
where the Modified data is already in DSO and i have validated the Data also, that is ok ...
so i need to Delete or to need to create another DTP to load the data from DSA to CUBE.
and even i have cheked all the tansformation rules they are all fine the DSO structure and Infocube Structure is ok,
Please suggest,
Thanks LAX,

Short Dump ASSIGN_TYPE_CONFLICT in Virtual KF implementation

Hi
Iam getting a short dump in my virtual KF code. Here is the code that I have written. If I have only bill date it works fine. The minute I add company code it gives the short dump. Can you pls let me know what is it that Iam doing wrong. any help will be greatly useful. Thanks.
INCLUDE ZXRSRU02
DATA: L_S_CHANM TYPE RRKE_S_CHANM.
DATA: L_SUBRC1 TYPE SY-SUBRC. "execute only, if key figure really used
CASE I_S_RKB1D-INFOCUBE.
   WHEN '0SD_C03'.
            L_S_CHANM-CHANM = '0BILL_DATE'.
            L_S_CHANM-MODE = RRKE_C_MODE-READ.
            APPEND L_S_CHANM TO E_T_CHANM.
            L_S_CHANM-CHANM = '0COMP_CODE'.
            L_S_CHANM-MODE = RRKE_C_MODE-READ.
            APPEND L_S_CHANM TO E_T_CHANM.
            APPEND 'ZCOUNT1' TO E_T_KYFNM.
ENDCASE.
*Include ZXRSRTOP*
DATA : G_POS_0SD_C03_0BILL_DATE TYPE I.
DATA : G_POS_0SD_C03_0COMP_CODE(4).
DATA : G_POS_0SD_C03_ZCOUNT1 TYPE I.
Include ZXRSRZZZ
FORM USER_0SD_C03 USING I_S_RKB1D TYPE RSR_S_RKB1D
CHANGING C_S_DATA TYPE ANY.
DATA: l_zcount1 TYPE int4.
FIELD-SYMBOLS <L_0BILL_DATE>.
FIELD-SYMBOLS <L_0COMP_CODE>.
FIELD-SYMBOLS <L_ZCOUNT1>.
ASSIGN COMPONENT G_POS_0SD_C03_0BILL_DATE
OF STRUCTURE C_S_DATA TO <L_0BILL_DATE>.
ASSIGN COMPONENT G_POS_0SD_C03_0COMP_CODE
OF STRUCTURE C_S_DATA TO <L_0COMP_CODE>.
ASSIGN COMPONENT G_POS_0SD_C03_ZCOUNT1
OF STRUCTURE C_S_DATA TO <L_ZCOUNT1>.
IF <L_0COMP_CODE> = 'AB99'.
    CALL FUNCTION 'ZCALC_WDAYS_BETWEEN_DATES'
      EXPORTING
        P_DATE1 = <L_0BILL_DATE>
        P_DATE2 = SY-DATUM
        P_CAL_ID = 'Z1'
      IMPORTING
        P_DAYS   = l_zcount1.
    <L_ZCOUNT1> = l_zcount1.
ELSEIF <L_0COMP_CODE> = 'DC99'.
    CALL FUNCTION 'ZCALC_WDAYS_BETWEEN_DATES'
      EXPORTING
        P_DATE1 = <L_0BILL_DATE>
        P_DATE2 = SY-DATUM
        P_CAL_ID = 'Z2'
      IMPORTING
        P_DAYS   = l_zcount1.
    <L_ZCOUNT1> = l_zcount1.
ENDIF.
The short dump:
ASSIGN_TYPE_CONFLICT
"CL_IM_RSR_OLAP_BADI===========CP" or "CL_IM_RSR_OLAP_BADI===========CM002"
"IF_EX_RSR_OLAP_BADI~INITIALIZE"
get field postions for characteristics in structure
LOOP AT i_th_sfc ASSIGNING <l_s_sfc>
     WHERE user_exit NE rrke_c_mode-none.
field name in structure is keyreturnnm
name of the global variable
CONCATENATE '(SAPLXRSR)G_POS' i_s_rkb1d-infocube <l_s_sfc>-chanm
      INTO l_global_name
      SEPARATED BY '_'.
fill the global variable
UNASSIGN <l_global>.
>>>>>>>> ASSIGN (l_global_name) TO <l_global>.

My suggestion is that you review the how-to papers on SDN regarding exit RSR00002 or RSR_OLAP_BADI. These are alternative methods of accomplishing virtual characteristics and key figures. The code you have given is for exit RSR00002 (although it is full of syntax errors so is not executable), but the short dump you are getting refers to RSR_OLAP_BADI, so you must have implemented that Class as well, but incompletely.
Which method are you attempting to use?

Runtime Errors         ASSIGN_TYPE_CONFLICT.

Hi,
Can any one help me on the below error.
Runtime Errors         ASSIGN_TYPE_CONFLICT.
I am trying to load Master data text for 0CUSTOMER and the DTP fails.I am in BI 7.0 environment.
Thanks
Raj

This is for 0CUSTOMER Text master data load.
I did a transport from DEV to QAS.It worked fine in DEV but not in QAS.
The transformation is pretty simple
KUNNR(customer) -
> 0CUSTOMER
TXTMD(Name)       -
> 0TXTMD(Medium Description)
The info package works fine but the DTP fails.
Runtime Errors         ASSIGN_TYPE_CONFLICT
Date and Time          19.11.2007 13:48:33
The detailed error message :
Short text
     Type conflict with ASSIGN in program "GPCFUGFSZVTSH2ZBSQO537K7P2W".
What happened?
     Error in the ABAP Application Program
     The current ABAP program "GPCFUGFSZVTSH2ZBSQO537K7P2W" 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" " "
     "GPCFUGFSZVTSH2ZBSQO537K7P2W" or "GPCFUGFSZVTSH2ZBSQO537K7P2W"
     "EXECUTE"
     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.
Thanks
Raj

Short dump:ASSIGN_TYPE_CONFLICT- While loading data through DTP

Dear all:
We currently work with BI NW2004s SP10. We created transformation for mapping InfoSource and InfoCube based on 3.x transfer rule. For example, we used cube 0PUR_C04 and Data Source 2LIS_02_ITM_CP. And the transformation is "TRCS Z2LIS_02_ITM_CP -> CUBE 0PUR_C04". Everytime when we tried to load data via DTP. A runtime short dump occurred: ASSIGN_TYPE_CONFLICT
Error analysis:
You attempted to assign a field to a typed fie but the field does not have the required type.
we went back and forth to activated transformation and DTP. But still, same error occurred.
Any idea, please !!!!
BR
SzuFen

Hi Pavel:
Please refer to the following information-
User and Transaction
    Client.............. 888
    User................ "TW_S
    Language key........ "E"
    Transaction......... " "
    Program............. "GPD0
    Screen.............. "SAPM
    Screen line......... 6
===========================================================
Information on where terminated
    Termination occurred in the ABAP program "GPD0QBVJ2WFQZZXBD0IJ1DSZAEL" - in
     "EXECUTE".
    The main program was "RSBATCH_EXECUTE_PROZESS ".
    In the source code you have the termination point in line 704
    of the (Include) program "GPD0QBVJ2WFQZZXBD0IJ1DSZAEL".
    The program "GPD0QBVJ2WFQZZXBD0IJ1DSZAEL" was started as a background job.
    Job Name....... "BIDTPR_284_1"
    Job Initiator.. "TW_SZU"
    Job Number..... 16454800
===========================================================
Short text
    Type conflict with ASSIGN in program "GPD0QBVJ2WFQZZXBD0IJ1DSZAEL".
===========================================================
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 "GPD0QBVJ2WFQZZXBD0IJ1DSZAEL" - in
     "EXECUTE".
    The main program was "RSBATCH_EXECUTE_PROZESS ".
    In the source code you have the termination point in line 704
    of the (Include) program "GPD0QBVJ2WFQZZXBD0IJ1DSZAEL".
    The program "GPD0QBVJ2WFQZZXBD0IJ1DSZAEL" was started as a background job.
    Job Name....... "BIDTPR_284_1"
    Job Initiator.. "TW_SZU"
    Job Number..... 16454800
===========================================================
Line SourceCde
674         ELSE.
675           ASSIGN rdsTG_1->*          to <_ys_TG_1>.
676           CLEAR <_ys_TG_1>.
677           MOVE-CORRESPONDING G1 TO <_ys_TG_1>.
678           <_ys_TG_1>-requid    = l_requid.
679           l_recno_TG_1          = l_recno_TG_1 + 1.
680           ls_cross-insegid      = 1.
681           ls_cross-inrecord     = l_recno_SC_1.
682           ls_cross-outsegid     = 1.
683           ls_cross-outrecord    = l_recno_TG_1.
684
685           CALL METHOD i_r_log->add_cross_tab
686             EXPORTING
687               I_S_CROSSTAB = ls_cross.
688
689 **     Record# in target = sy-tabix - if sorting of table won't be changed
690           <_ys_TG_1>-record     = l_recno_TG_1.
691           INSERT <_ys_TG_1> INTO TABLE <_yth_TG_1>.
692           IF sy-subrc <> 0.
693             CALL METHOD cl_rsbm_log_step=>raise_step_failed_callstack.
694           ENDIF.
695
696         ENDIF.      "Read table
697 *
698       ENDIF.
699       CLEAR skipseg_all.
700     ENDLOOP.
701 * -
insert table into outbound segment -
702
703     <_yt_TG_1>[] = <_yth_TG_1>[].
>>>>>
705     rTG_1->insert_table( rdtTG_1_dp ).
706   ENDMETHOD.                 "execute
707
708
709
710 endclass.                    "lcl_transform IMPLEMENTATION
711
712 &----
713 *&      Form get_runtime_ref
714 &----
715 *       text
716 ----
717 *      -->C_R_EXE    text
718 ----
719 form get_runtime_ref
720 changing c_r_exe type ref to object.
721
722   data: l_r_exe type ref to lcl_transform.
723   create object l_r_exe.
===========================================================
Contents of system fields
Name     Val.
SY-SUBRC 0
SY-INDEX 3
SY-TABIX 0
SY-DBCNT 1
SY-FDPOS 0
SY-LSIND 0
SY-PAGNO 0
SY-LINNO 1
SY-COLNO 1
SY-PFKEY
SY-UCOMM
SY-TITLE Execute Batch Process
SY-MSGTY E
SY-MSGID R7
SY-MSGNO 057
SY-MSGV1 0TOTDELTIME
SY-MSGV2 A
SY-MSGV3
SY-MSGV4
SY-MODNO 0
SY-DATUM 20070420
SY-UZEIT 164557
SY-XPROG SAPCNVE
SY-XFORM CONVERSION_EXIT
===========================================================
Active Calls/Events
No.   Ty.          Program                             Include
      Name
    6 METHOD       GPD0QBVJ2WFQZZXBD0IJ1DSZAEL         GPD0QBVJ2WFQZZXBD0IJ1DSZAEL
      LCL_TRANSFORM=>EXECUTE
    5 METHOD       CL_RSTRAN_TRFN_CMD============CP    CL_RSTRAN_TRFN_CMD============CM005
      CL_RSTRAN_TRFN_CMD=>IF_RSBK_CMD_T~TRANSFORM
    4 METHOD       CL_RSBK_PROCESS===============CP    CL_RSBK_PROCESS===============CM00Q
      CL_RSBK_PROCESS=>PROCESS_REQUEST
    3 METHOD       CL_RSBK_PROCESS===============CP    CL_RSBK_PROCESS===============CM002
      CL_RSBK_PROCESS=>IF_RSBATCH_EXECUTE~EXECUTE
    2 FUNCTION     SAPLRSBATCH                         LRSBATCHU13
      RSBATCH_EXECUTE_PROCESS
    1 EVENT        RSBATCH_EXECUTE_PROZESS             RSBATCH_EXECUTE_PROZESS
      START-OF-SELECTION
===========================================================
Thank you and BR
SF

Handling the ASSIGN_TYPE_CONFLICT in a try catch block

Hi,
Post WAS 610 all system exceptions are handled by exception classes, I could not find the exception class for the runtime exception ASSIGN_TYPE_CONFLICT, if any body is in knowledge of the same or knows of a better way to handle the runtime exception kindly let me know.
Thanks in advance.
Aniruddha Gargya

Hi Raja,
I have already tried all teh exceptions listed for type conversion and assign. The help document also suggested that teh exception class name for a runtime exception will appear in the system trace.
The issue still remains where it was, When i get this execption from a web page the same is not being caught.
Thanks and Regards,
Aniruddha Gargya

Dump ASSIGN_TYPE_CONFLICT when loading into Cube

Hi,
since an few weeks we have sometimes a problem when loading data from DSO to cube.
After transport a changed cube the first dataload into the cube dumps with ASSIGN_TYPE_CONFLICT.
We always activate all transformations and all DTPs which belong to the changed cube and also transport them.
When we repeat the dataload after the dump there is no problem and the data will be loaded successfully.
The dump appears on a very strange coding-place:
* FORM WRITE_DATA_CHAVL                                              *
* Kommentar: incoming data is based in characteritic values!        *
*              Transformation to Dimension Id's needs first to        *
*              translate the charateristic values into SID's          *
FORM write_data_chavl
USING
    i_r_data       TYPE REF TO data
    i_simulation   TYPE rs_bool
    i_trexaggr     TYPE rs_bool
    i_req_sid      TYPE rssid
    i_t_tabix      TYPE gt_t_tabix
    i_ncum_loadtp TYPE ncum_loadtype
    i_pkg_id       TYPE rssid
CHANGING
    c_subrc        TYPE i.
DATA:
    l_recno       LIKE sy-tabix,
    l_erridx      LIKE sy-tabix,
    l_nexterr     LIKE sy-tabix,
    l_errnumbers TYPE i,
    l_subrc1      LIKE sy-subrc,
    l_pdimid      TYPE rssid.
FIELD-SYMBOLS:
    <l_t_cubeval> TYPE g_t_cubecha,
    <l_s_cubecha> TYPE g_s_cubecha.
IF i_pkg_id <> 0.
*   bug, cube is not delta write enabled...
    cl_rsdd_cube_writer=>monitor_log(
      i_recno    = 0
      i_msgid    = 'DBMAN'
>>>      i_msgno    = '971'
      i_errtp    = ''
      i_errnm    = ''
      i_fieldnm = '' ).
    c_subrc = cl_rsdd_cube_writer=>nc_error-no_continue.
    RETURN.
ENDIF.
Does anyone else have this problem?
Or does anyone even have the solution?
I haven't found anything useful in SDN and SAP-Notes....
Christian

Hi Christian,
In that case check if this helps.....
1905680 - SP32: 'ASSIGN_TYPE_CONFLICT' in transformation during loading data using DTP
It says
SAP NetWeaver BW 7.31 (SAP NW BW 7.3 EnhP 1)
Import Support Package 10 for SAP NetWeaver BW 7.31 (SAPKW73110) into your BW system.
Regards

DTP -ASSIGN_TYPE_CONFLICT

Hi,
I am getting an error in my DTP as ASSIGN_TYPE_CONFLICT. i'm loading the data from cube to cube. Please suggest... i did check some OSS notes and they just say about re-activation and it's not working.
I write the code at second cube transformation.
IF SOURCE_FIELDS-Mat_grp = '#' OR
        SOURCE_FIELDS-Mat_grp = ''.
         RESULT = SOURCE_FIELDS-DOC_NO.
     ELSE.
         RESULT = 0.
         RAISE EXCEPTION TYPE CX_RSROUT_SKIP_RECORD.
     ENDIF.
It's urgent issue.
Thanks
Kris

Hi,
Thanks for reply,
I activated Cube,Transformation and DTP even i am facing same problem. I re-transported the Cube , trans and DTP even same issue i am getting. Any inputs.
I am guess issue with this code   RAISE EXCEPTION TYPE CX_RSROUT_SKIP_RECORD.
Thanks
Kris

Shortdump ASSIGN_TYPE_CONFLICT

Hi,
when i start a DTP (with info source), I get a runtime error (ASSIGN_TYPE_CONFLICT), especially flatfiles
DEMOSYSTEM: Netweaver 2004s SPS5
Can anybody help me, please.
Thanks.
Bernd

hi Bernd,
you may need sp6
908427
Symptom
When you execute the data transfer process (DTP), the process terminates with the "ASSIGN_TYPE_CONFLICT" runtime error in the generated transformation program.
Other terms
Program position where the error occurs:
    assign rdsTG_1->*            to <_ys_TG_1>.
Reason and Prerequisites
Reason: This problem is caused by a program error.
Prerequisite: An InfoSource is involved in the transformation.
Solution
SAP NetWeaver 2004s BI
           If the error occurs in a note you implemented or in Support Package 06 or higher, you must follow the manual troubleshooting steps<AS Char>described below.
           Import Support Package 06 for SAP NetWeaver 2004s BI (BI Patch 07 or SAPKW70006) into your BI system. The Support Package is available when Note 0872278 "SAPBINews BI 7.0 Support Package 06", which describes t his Support Package in more detail, is released for customers.
In urgent cases, you can use the correction instructions.
You must then proceed as follows:
Manual steps for troubleshooting:
The transformation(s) involved must be newly activated or you must reset the generation status:
Carry out the following steps to reset the status:
Call Transaction 'RSSGPCLA'
Place the cursor on the 'RSTRAN_MASTER_TMPL' program class.
Choose the 'Set status' pushbutton (CTRL+F3)
To provide advance information, the notes mentioned above may be available before the Support Package is released. In this case, the short text of the note still contains the words "Preliminary version".

ASSIGN_TYPE_CONFLICT - /UI2/CL_LPD_UTILS=============CP

Similar Messages

Maybe you are looking for