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

Similar Messages

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

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

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

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

DTP to 0RPM_C02 (Capacity Management) InfoCube is getting failed

Hi,
I have installed the BI Content InfoCube 0RPM_C02 and all its data flow objects. After all the objects are moved to our Production Server, I am getting an error while executing the DTP. But, I didn't get any error while doing the same in Development Server.
I am not able to understand what could be the problem and I do not know how to debug the error. Can you please help me out.
Below given are the details of this problem
Data Flow : 0RPM_C02
DTPs to load the data from the 3rd Data Source (0RPM_BUPA_AVL) is happening smoothly. But the other 2 are giving the error, which is shown below.
Please help me in debugging this problem.
Thanks & Regards,
Ranjan Jinka
+919008477785

Hi all,
I found the solution to this problem. Thanks to Edwin Harpino
He has given the solution a long back. For anybody who wants to understand the solution, here is the link Shortdump ASSIGN_TYPE_CONFLICT
However, Thanks Phani for your time.
Regards,
Ranjan Jinka
+919008477785

ABAP DUMP IN DTP

Hi All,
i got a ABAP Dump in the DTP while i am loading the Text data stating " ASSIGN_TYPE_CONFLICT" . I had chked but unable to find any reason if any one is familiar abt this plz help me out.
Regards
KK

I had a similar problem. It is not enough to activate the transformation.
We changed the target structure by deleting a field (I think add a field should be fine, too), activated everything and changed the structure and transformation back after this.
The change of structure lead to a complete new generation of the generic code. Activation alone is not enough, a bigger change is necessary!
After this change and activation everything run perfect!

DTP failure

Hi There,
DTP has got failed due to ASSIGN_TYPE_CONFLICT, this dtp is getting failed daily coz of teh same eror. but at times I it works when we delte the bad request and repeat the dtp..
Could any one plz give me sol for this!!
Jyothi

Hi...
This dump is very common with data load based on DTP (Data Transform Process). You can observe you failed load in DTP Monitor as follows:
If you clink on ABAP dump icon as above you go to TA ST22 (ABAP Runtime Error) to see dump.
It is caused by changed meta data of objects involved in this data loads. A process (mode) used for the runtime of BI objects has a certain and determined lifetime. Generated program (GP) which is serving for transformation (TRAN) between source and target objects of your load no longer match the metadata because the metadata changes during this lifetime. It means that you have recently changed something within your source and target objects (e.g. via TA RSA1) then you transported just some part of your changes recently but not whole data flow. Therefore your GP* program is referencing to u201Eoldu201C runtime version of objects and they are already changed to u201Enewu201C version
To solve such a failed upload you need to regenerate your GP* program u2013 this involves re-activate transformation. This can be a 1st step. If this doesnu2019t help you need to go deeper and re-activate and re-transport other objects involved in data flow like 1. source object of the DTP (DSO/DS/IS for example; depending in your particular flow); 2. target object of the DTP (e.g. InfoCube/DSO/InfoProvider IO); 3. transformation; 4. the DTP as it self.
Kindly assign me some points if this helps you...
Regards,
Debjani...
Edited by: Debjani Mukherjee on Sep 6, 2008 11:27 AM

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

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,

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

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

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 in Prod

hi...i am in production server now and when i try to load data from psa to the dso in bw, i having the error called = Assign_Type_Conflict when execute the dtp process. Since i am in prod server, i cannot do any changes directly in prod, is there any way can troubleshoot this without doing any transport from the dev to prod?? Help needed alot here.

HI please follow following steps:
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)
for more refer
Note 908427 - 'ASSIGN_TYPE_CONFLICT' dump in the DTP with InfoSource
Assign point if helpful

ASSIGN_TYPE_CONFLICT dump with 2LIS_13_VDITM

Hi Expert
When i execute 2LIS_13_VDITM DTP for the cube 0SD_C03 I gt a dump with this message: ASSIGN_TYPE_CONFLICT
I use the SAP transformation and SAP DTP. All the routine are SAP routine. No generic abap exist
Can any one help me please?
Thanks

Hi
It's OK, juste reactivate the tranformation... Incroyable
Thanks

DTP -ASSIGN_TYPE_CONFLICT

Similar Messages

Maybe you are looking for