NLS_LENGTH_SEMANTICS and work tables in KMs

Hi everybody,
I'm working on an interface that uses a 11g-based workarea. A quick query on v$nls_parameters returns:
NLS_CHARACTERSET: AL32UTF8
NLS_LENGTH_SEMANTICS: BYTE
Because of this every time a km creates a "$" table, CHAR and VARCHAR2 column lengths are implicitly defined in bytes.
Obviously when a 30-chars string (source datastores are on DB2) exceeds those 30 bytes target length, the execution fails.
Is there any way to avoid this? I've tried adding "ALTER SESSION ..." as a step in the "LKM SQL to Oracle" km I'm using but from what I understand every action performed by it on the database lives in its own session.
I'd prefer to avoid performing ALTER SYSTEM as the 11g instance has other apps/products installed.
Sorry for my bad english and thanks in advance for any suggestion...

Sutirtha, your post was sort of inspiring!
I've found a partial solution to my problem by changing in Topology Manager the CHAR and VARCHAR2 datatypes implementation for the Oracle technology:
!http://www.abload.de/img/odi-datatype-implementu55n.png!
Now only a little annoyance remains, caused by a known bug (4485954) within the Oracle JDBC driver: when I reverse engineer tables from a UTF8 physical schema, ALL_TAB_COLUMNS.COLUMN_LENGTH is used instead of ALL_TAB_COLUMNS.CHAR_LENGTH.
I should try to use a newer jdbc .jar but IIRC that bug is resolved only with db 11g that ships with JDK 1.5/1.6 drivers which ODI (1.4 based) cannot use...

Similar Messages

How can we use TABLE CONTROL in BDC and WORK FLOW of ABAP.

how can we use TABLE CONTROL in BDC and WORK FLOW of ABAP.?
please explain the important questions.

How to deal with table control / step loop in BDC
Steploop and table contol is inevitable in certain transactions. When we run BDC for such transactions, we will face the situation: how many visible lines of steploop/tablecontrol are on the screen? Although we can always find certain method to deal with it, such as function code 'NP', 'POPO', considering some extreme situation: there is only one line visible one the screen, our BDC program should display an error message. (See transaction 'ME21', we you resize your screen to let only one row visible, you can not enter mutiple lines on this screen even you use 'NP')
Now with the help of Poonam on sapfans.com developement forum, I find a method with which we can determine the number of visible lines on Transaction Screen from our Calling BDC program. Maybe it is useless to you, but I think it will give your some idea.
Demo ABAP code has two purposes:
1. how to determine number of visible lines and how to calculte page number;
(the 'calpage' routine has been modify to meet general purpose usage)
2. using field symbol in BDC program, please pay special attention to the difference in Static ASSIGN and Dynamic ASSIGN.
Now I begin to describe the step to implement my method:
(I use transaction 'ME21', screen 121 for sample,
the method using is Call Transation Using..)
Step1: go to screen painter to display the screen 121, then we can count the fixed line on this screen, there is 7 lines above the steploop and 2 lines below the steploop, so there are total 9 fixed lines on this screen. This means except these 9 lines, all the other line is for step loop. Then have a look at steploop itselp, one entry of it will occupy two lines.
(Be careful, for table control, the head and the bottom scroll bar will possess another two fixed lines, and there is a maximum number for table line)
Now we have : FixedLine = 9
              LoopLine = 2(for table control, LoopLine is always equal to 1)
Step2: go to transaction itself(ME21) to see how it roll page, in ME21, the first line of new page is always occupied by the last line of last page, so it begin with index '02', but in some other case, fisrt line is empty and ready for input.
Now we have: FirstLine = 0
          or FirstLine = 1 ( in our case, FirstLine is 1 because the first line of new page is fulfilled)
Step3: write a subroutine calcalculating number of pages
(here, the name of actual parameter is the same as formal parameter)
global data:    FixedLine type i, " number of fixed line on a certain screen
                LoopLine type i, " the number of lines occupied by one steploop item
                FirstLine type i, " possbile value 0 or 1, 0 stand for the first line of new                                                               " scrolling screen is empty, otherwise is 1
                Dataline type i, " number of items you will use in BDC, using DESCRIBE to get
                pageno    type i, " you need to scroll screen how many times.
                line      type i, " number of lines appears on the screen.
                index(2) type N, " the screen index for certain item
                begin     type i, " from parameter of loop
                end       type i. " to parameter of loop
*in code sample, the DataTable-linindex stands for the table index number of this line
form calpage using FixedLine type i (see step 1)
                   LoopLine type i (see step 1)
                   FirstLine type i (see step 2)
                   DataLine type i ( this is the item number you will enter in transaction)
          changing pageno    type i (return the number of page, depends on run-time visible                                                                             line in table control/ Step Loop)
          changing line      type i.(visible lines one the screen)
data: midd type i,
      vline type i, "visible lines
if DataLine eq 0.
   Message eXXX.
endif.
vline = ( sy-srows - FixedLine ) div LoopLine.
*for table control, you should compare vline with maximum line of
*table control, then take the small one that is min(vline, maximum)
*here only illustrate step loop
if FirstLine eq 0.
        pageno = DataLine div vline.
        if pageno eq 0.
           pageno = pageno + 1.
        endif.
elseif FirstLine eq 1.
        pageno = ( DataLine - 1 ) div ( vline - 1 ) + 1.
        midd = ( DataLine - 1 ) mod ( vline - 1).
        if midd = 0 and DataLine gt 1.
                pageno = pageno - 1.
        endif.
endif.
line = vline.
endform.
Step4 write a subroutine to calculate the line index for each item.
form calindex using Line type i (visible lines on the screen)
                    FirstLine type i(see step 2)
                    LineIndex type i(item index)
          changing Index type n.    (index on the screen)
if FirstLine = 0.
        index = LineIndex mod Line.
        if index = '00'.
                index = Line.
        endif.
elseif FirstLine = 1.
        index = LineIndex mod ( Line - 1 ).
        if ( index between 1 and 0 ) and LineIndex gt 1.
                index = index + Line - 1.
        endif.
        if Line = 2.
                index = index + Line - 1.
        endif.
endif.
endform.
Step5 write a subroutine to calculate the loop range.
form calrange using Line type i ( visible lines on the screen)
                    DataLine type i
                    FirstLine type i
                    loopindex like sy-index
        changing    begin type i
                    end type i.
If FirstLine = 0.
   if loopindex = 1.
        begin = 1.
        if DataLine <= Line.
                end = DataLine.
        else.
                end = Line.
        endif.
   elseif loopindex gt 1.
        begin = Line * ( loopindex - 1 ) + 1.
        end   = Line * loopindex.
        if end gt DataLine.
           end = DataLine.
        endif.
   endif.
elseif FirstLine = 1.
if loopindex = 1.
        begin = 1.
        if DataLine <= Line.
                end = DataLine.
        else.
                end = Line.
        endif.
elseif loop index gt 1.
        begin = ( Line - 1 ) * ( loopindex - 1 ) + 2.
        end =   ( Line - 1 ) * ( loopindex - 1 ) + Line.
        if end gt DataLine.
                end = DataLine.
        endif.
endif.
endif.
endform.
Step6 using field sysbol in your BDC, for example: in ME21, but you should calculate each item will correponding to which index in steploop/Table Control
form creat_bdc.
field-symbols: <material>, <quan>, <indicator>.
data: name1(14) value 'EKPO-EMATN(XX)',
      name2(14) value 'EKPO-MENGE(XX)',
      name3(15) value 'RM06E-SELKZ(XX)'.
assign:         name1 to <material>,
                name2 to <quan>,
                name3 to <indicator>.
do pageno times.
if sy-index gt 1
*insert scroll page ok_code"
endif.
        perform calrange using Line DataLine FirstLine sy-index
                         changing begin end.
loop at DataTable from begin to end.
        perform calindex using Line FirstLine DataTable-LineIndex changing Index.
        name1+11(2) = Index.
        name2+11(2) = Index.
        name3+12(2) = Index.
        perform bdcfield using <material> DataTable-matnr.
        perform bdcfield using <quan>     DataTable-menge.
        perform bdcfield using <indicator> DataTable-indicator.
endloop.
enddo.
An example abap program of handling Table Control during bdc programming.
REPORT zmm_bdcp_purchaseorderkb02
       NO STANDARD PAGE HEADING LINE-SIZE 255.
                Declaring internal tables                            *
*-----Declaring line structure
DATA : BEGIN OF it_dummy OCCURS 0,
         dummy(255) TYPE c,
       END OF it_dummy.
*-----Internal table for line items
DATA : BEGIN OF it_idata OCCURS 0,
          ematn(18),      "Material Number.
          menge(13),      "Qyantity.
          netpr(11),      "Net Price.
          werks(4),       "Plant.
          ebelp(5),       "Item Number.
        END OF it_idata.
*-----Deep structure for header data and line items
DATA : BEGIN OF it_me21 OCCURS 0,
           lifnr(10),      "Vendor A/c No.
           bsart(4),       "A/c Type.
           bedat(8),       "Date of creation of PO.
           ekorg(4),       "Purchasing Organisation.
           ekgrp(3),       "Purchasing Group.
           x_data LIKE TABLE OF it_idata,
         END OF it_me21.
DATA : x_idata LIKE LINE OF it_idata.
DATA : v_delimit VALUE ','.
DATA : v_indx(3) TYPE n.
DATA : v_fnam(30) TYPE c.
DATA : v_count TYPE n.
DATA : v_ne TYPE i.
DATA : v_ns TYPE i.
*include bdcrecx1.
INCLUDE zmm_incl_purchaseorderkb01.
                Search help for file                                 *
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.
CALL FUNCTION 'F4_FILENAME'
    EXPORTING
      program_name = syst-cprog
      dynpro_number = syst-dynnr
    IMPORTING
      file_name     = p_file.
START-OF-SELECTION.
       To upload the data into line structure                        *
CALL FUNCTION 'WS_UPLOAD'
    EXPORTING
      filename = p_file
      filetype = 'DAT'
    TABLES
      data_tab = it_dummy.
    Processing the data from line structure to internal tables       *
REFRESH:it_me21.
CLEAR :it_me21.
LOOP AT it_dummy.
    IF it_dummy-dummy+0(01) = 'H'.
      v_indx = v_indx + 1.
      CLEAR   it_idata.
      REFRESH it_idata.
      CLEAR   it_me21-x_data.
      REFRESH it_me21-x_data.
      SHIFT it_dummy.
      SPLIT it_dummy AT v_delimit INTO it_me21-lifnr
                                       it_me21-bsart
                                       it_me21-bedat
                                       it_me21-ekorg
                                       it_me21-ekgrp.
      APPEND it_me21.
    ELSEIF it_dummy-dummy+0(01) = 'L'.
      SHIFT it_dummy.
      SPLIT it_dummy AT v_delimit INTO it_idata-ematn
                                       it_idata-menge
                                       it_idata-netpr
                                       it_idata-werks
                                       it_idata-ebelp.
      APPEND it_idata TO it_me21-x_data.
      MODIFY it_me21 INDEX v_indx.
    ENDIF.
ENDLOOP.
                To open the group                                    *
PERFORM open_group.
        To populate the bdcdata table for header data                *
LOOP AT it_me21.
    v_count = v_count + 1.
    REFRESH it_bdcdata.
    PERFORM subr_bdc_table USING:   'X' 'SAPMM06E'    '0100',
                                    ' ' 'BDC_CURSOR' 'EKKO-LIFNR',
                                    ' ' 'BDC_OKCODE' '/00',
                                    ' ' 'EKKO-LIFNR' it_me21-lifnr,
                                    ' ' 'RM06E-BSART' it_me21-bsart,
                                    ' ' 'RM06E-BEDAT' it_me21-bedat,
                                    ' ' 'EKKO-EKORG' it_me21-ekorg,
                                    ' ' 'EKKO-EKGRP' it_me21-ekgrp,
                                    ' ' 'RM06E-LPEIN' 'T'.
    PERFORM subr_bdc_table USING:   'X' 'SAPMM06E'    '0120',
                                    ' ' 'BDC_CURSOR' 'RM06E-EBELP',
                                    ' ' 'BDC_OKCODE' '/00'.
    MOVE 1 TO v_indx.
*-----To populate the bdcdata table for line item data
    LOOP AT it_me21-x_data INTO x_idata.
      CONCATENATE 'EKPO-EMATN(' v_indx ')' INTO v_fnam.
      PERFORM subr_bdc_table USING ' ' v_fnam x_idata-ematn.
      CONCATENATE 'EKPO-MENGE(' v_indx ')' INTO v_fnam.
      PERFORM subr_bdc_table USING ' ' v_fnam x_idata-menge.
      CONCATENATE 'EKPO-NETPR(' v_indx ')' INTO v_fnam.
      PERFORM subr_bdc_table USING ' ' v_fnam x_idata-netpr.
      CONCATENATE 'EKPO-WERKS(' v_indx ')' INTO v_fnam.
      PERFORM subr_bdc_table USING ' ' v_fnam x_idata-werks.
      v_indx = v_indx + 1.
      PERFORM subr_bdc_table USING: 'X' 'SAPMM06E'    '0120',
                                     ' ' 'BDC_CURSOR' 'RM06E-EBELP',
                                     ' ' 'BDC_OKCODE' '/00'.
    ENDLOOP.
    PERFORM subr_bdc_table USING:    'X' 'SAPMM06E'    '0120',
                                     ' ' 'BDC_CURSOR' 'RM06E-EBELP',
                                     ' ' 'BDC_OKCODE' '=BU'.
    PERFORM bdc_transaction USING 'ME21'.
ENDLOOP.
PERFORM close_group.
                  End of selection event                             *
END-OF-SELECTION.
IF session NE 'X'.
*-----To display the successful records
    WRITE :/10 text-001.          "Sucess records
    WRITE :/10 SY-ULINE(20).
    SKIP.
    IF it_sucess IS INITIAL.
      WRITE :/ text-002.
    ELSE.
      WRITE :/   text-008,          "Total number of Succesful records
              35 v_ns.
      SKIP.
      WRITE:/   text-003,          "Vendor Number
             17 text-004,          "Record number
             30 text-005.          "Message
    ENDIF.
    LOOP AT it_sucess.
      WRITE:/4 it_sucess-lifnr,
             17 it_sucess-tabix CENTERED,
             30 it_sucess-sucess_rec.
    ENDLOOP.
    SKIP.
*-----To display the erroneous records
    WRITE:/10   text-006.          "Error Records
    WRITE:/10   SY-ULINE(17).
    SKIP.
    IF it_error IS INITIAL.
      WRITE:/   text-007.          "No error records
    ELSE.
      WRITE:/   text-009,          "Total number of erroneous records
             35 v_ne.
      SKIP.
      WRITE:/   text-003,          "Vendor Number
             17 text-004,          "Record number
             30 text-005.          "Message
    ENDIF.
    LOOP AT it_error.
      WRITE:/4 it_error-lifnr,
             17 it_error-tabix CENTERED,
             30 it_error-error_rec.
    ENDLOOP.
    REFRESH it_sucess.
    REFRESH it_error.
ENDIF.
CODE IN INCLUDE.
Include           ZMM_INCL_PURCHASEORDERKB01
DATA:   it_BDCDATA LIKE BDCDATA    OCCURS 0 WITH HEADER LINE.
DATA:   it_MESSTAB LIKE BDCMSGCOLL OCCURS 0 WITH HEADER LINE.
DATA:   E_GROUP_OPENED.
*-----Internal table to store sucess records
DATA:BEGIN OF it_sucess OCCURS 0,
       msgtyp(1)   TYPE c,
       lifnr LIKE ekko-lifnr,
       tabix LIKE sy-tabix,
       sucess_rec(125),
     END OF it_sucess.
DATA: g_mess(125) type c.
*-----Internal table to store error records
DATA:BEGIN OF it_error OCCURS 0,
       msgtyp(1)   TYPE c,
       lifnr LIKE ekko-lifnr,
       tabix LIKE sy-tabix,
       error_rec(125),
     END OF it_error.
       Selection screen
SELECTION-SCREEN BEGIN OF LINE.
PARAMETERS session RADIOBUTTON GROUP ctu. "create session
SELECTION-SCREEN COMMENT 3(20) text-s07 FOR FIELD session.
SELECTION-SCREEN POSITION 45.
PARAMETERS ctu RADIOBUTTON GROUP ctu.     "call transaction
SELECTION-SCREEN COMMENT 48(20) text-s08 FOR FIELD ctu.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 3(20) text-s01 FOR FIELD group.
SELECTION-SCREEN POSITION 25.
PARAMETERS group(12).                      "group name of session
SELECTION-SCREEN COMMENT 48(20) text-s05 FOR FIELD ctumode.
SELECTION-SCREEN POSITION 70.
PARAMETERS ctumode LIKE ctu_params-dismode DEFAULT 'N'.
"A: show all dynpros
"E: show dynpro on error only
"N: do not display dynpro
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 48(20) text-s06 FOR FIELD cupdate.
SELECTION-SCREEN POSITION 70.
PARAMETERS cupdate LIKE ctu_params-updmode DEFAULT 'L'.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 3(20) text-s03 FOR FIELD keep.
SELECTION-SCREEN POSITION 25.
PARAMETERS: keep AS CHECKBOX.       "' ' = delete session if finished
"'X' = keep   session if finished
SELECTION-SCREEN COMMENT 48(20) text-s09 FOR FIELD e_group.
SELECTION-SCREEN POSITION 70.
PARAMETERS e_group(12).             "group name of error-session
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 51(17) text-s03 FOR FIELD e_keep.
SELECTION-SCREEN POSITION 70.
PARAMETERS: e_keep AS CHECKBOX.     "' ' = delete session if finished
"'X' = keep   session if finished
SELECTION-SCREEN END OF LINE.
PARAMETERS:p_file LIKE rlgrap-filename.
at selection screen                                                *
AT SELECTION-SCREEN.
group and user must be filled for create session
IF SESSION = 'X' AND
     GROUP = SPACE. "OR USER = SPACE.
    MESSAGE E613(MS).
ENDIF.
create batchinput session                                          *
FORM OPEN_GROUP.
IF SESSION = 'X'.
    SKIP.
    WRITE: /(20) 'Create group'(I01), GROUP.
    SKIP.
*----open batchinput group
    CALL FUNCTION 'BDC_OPEN_GROUP'
      EXPORTING
        CLIENT = SY-MANDT
        GROUP = GROUP
        USER   = sy-uname.
    WRITE:/(30) 'BDC_OPEN_GROUP'(I02),
            (12) 'returncode:'(I05),
                 SY-SUBRC.
ENDIF.
ENDFORM.                    "OPEN_GROUP
end batchinput session                                             *
FORM CLOSE_GROUP.
IF SESSION = 'X'.
*------close batchinput group
    CALL FUNCTION 'BDC_CLOSE_GROUP'.
    WRITE: /(30) 'BDC_CLOSE_GROUP'(I04),
            (12) 'returncode:'(I05),
                 SY-SUBRC.
ELSE.
    IF E_GROUP_OPENED = 'X'.
      CALL FUNCTION 'BDC_CLOSE_GROUP'.
      WRITE: /.
      WRITE: /(30) 'Fehlermappe wurde erzeugt'(I06).
    ENDIF.
ENDIF.
ENDFORM.                    "CLOSE_GROUP
       Start new transaction according to parameters                 *
FORM BDC_TRANSACTION USING TCODE TYPE ANY.
DATA: L_SUBRC LIKE SY-SUBRC.
*------batch input session
IF SESSION = 'X'.
    CALL FUNCTION 'BDC_INSERT'
      EXPORTING
        TCODE     = TCODE
      TABLES
        DYNPROTAB = it_BDCDATA.
    WRITE: / 'BDC_INSERT'(I03),
             TCODE,
             'returncode:'(I05),
             SY-SUBRC,
             'RECORD:',
             SY-INDEX.
ELSE.
    REFRESH it_MESSTAB.
    CALL TRANSACTION TCODE USING it_BDCDATA
                     MODE   CTUMODE
                     UPDATE CUPDATE
                     MESSAGES INTO it_MESSTAB.
    L_SUBRC = SY-SUBRC.
    WRITE: / 'CALL_TRANSACTION',
             TCODE,
             'returncode:'(I05),
             L_SUBRC,
             'RECORD:',
             SY-INDEX.
ENDIF.
Message handling for Call Transaction                              *
perform subr_mess_hand using g_mess.
*-----Erzeugen fehlermappe
IF L_SUBRC <> 0 AND E_GROUP <> SPACE.
    IF E_GROUP_OPENED = ' '.
      CALL FUNCTION 'BDC_OPEN_GROUP'
        EXPORTING
          CLIENT = SY-MANDT
          GROUP = E_GROUP
          USER   = sy-uname
          KEEP   = E_KEEP.
      E_GROUP_OPENED = 'X'.
    ENDIF.
    CALL FUNCTION 'BDC_INSERT'
      EXPORTING
        TCODE     = TCODE
      TABLES
        DYNPROTAB = it_BDCDATA.
ENDIF.
REFRESH it_BDCDATA.
ENDFORM.                    "BDC_TRANSACTION
     Form subr_bdc_table                                            *
      text
     -->P_0220   text                                                *
     -->P_0221   text                                                *
     -->P_0222   text                                                *
FORM subr_bdc_table USING      VALUE(P_0220) TYPE ANY
                                VALUE(P_0221) TYPE ANY
                                VALUE(P_0222) TYPE ANY.
CLEAR it_bdcdata.
IF P_0220 = ' '.
    CLEAR it_bdcdata.
    it_bdcdata-fnam     = P_0221.
    it_bdcdata-fval     = P_0222.
    APPEND it_bdcdata.
ELSE.
    it_bdcdata-dynbegin = P_0220.
    it_bdcdata-program = P_0221.
    it_bdcdata-dynpro   = P_0222.
    APPEND it_bdcdata.
ENDIF.
ENDFORM.                    " subr_bdc_table
     Form subr_mess_hand                                            *
      text                                                           *
     -->P_G_MESS text                                               *
FORM subr_mess_hand USING P_G_MESS TYPE ANY.
LOOP AT IT_MESSTAB.
    CALL FUNCTION 'FORMAT_MESSAGE'
      EXPORTING
        ID     = it_messtab-msgid
        LANG   = it_messtab-msgspra
        NO     = it_messtab-msgnr
        v1     = it_messtab-msgv1
        v2     = it_messtab-msgv2
      IMPORTING
        MSG    = P_G_MESS
      EXCEPTIONS
        OTHERS = 0.
    CASE it_messtab-msgtyp.
      when 'E'.
        it_error-error_rec   = P_G_MESS.
        it_error-lifnr       = it_me21-lifnr.
        it_error-tabix       = v_count.
        APPEND IT_ERROR.
      when 'S'.
        it_sucess-sucess_rec = P_G_MESS.
        it_sucess-lifnr      = it_me21-lifnr.
        it_sucess-tabix      = v_count.
        APPEND IT_SUCESS.
    endcase.
ENDLOOP.
Describe table it_sucess lines v_ns.
Describe table it_error lines v_ne.
ENDFORM.                    " subr_mess_hand
Also refer
http://sap.ittoolbox.com/groups/technical-functional/sap-dev/bdc-table-control-668404
and
http://www.sap-img.com/abap/bdc-example-using-table-control-in-bdc.htm
Regards,
srinivas
<b>*reward for useful answers*</b>

The type of the database table and work area (or internal table)...

Hello
I am trying to use a database and select all records from it and store them into an internal table.
My code:
Select * from xixi_dbcurrency into table gt_currency.
The error:
"The type of the database table and work area (or internal table) "GT_CURRENCY" are not Unicode-convertible . . . . . . . . . .     "
Any suggestions?
Thank you

Hi Thomas,
Thank you for your inputs above.
But as you suggested is we use INTO CORRESPONDING FIELDS OF TABLE then it resolve the error.
But I have below piece of code:
DATA:    it_new_source TYPE STANDARD TABLE OF _ty_s_sc_1,
              wa_source TYPE _ty_s_sc_1,
              wa_new_source TYPE _ty_s_sc_1,
              ls_target_key TYPE t_target_key.
SELECT * INTO CORRESPONDING FIELDS OF TABLE it_new_source
       FROM /bic/afao06pa100
       FOR ALL ENTRIES IN SOURCE_PACKAGE
       where /bic/fcckjobno = SOURCE_PACKAGE-/bic/fcckjobno
       and /bic/fcckjitid = SOURCE_PACKAGE-/bic/fcckjitid.
But since this is reading into corresponding fields of table the data load from one DSO to other DOS is running for long more that 15 hours and still not getting completed and giving dump.
So if I switch the search to below:
SELECT * FROM /bic/afao06pa100
   INTO TABLE it_new_source
       FOR ALL ENTRIES IN SOURCE_PACKAGE
       where /bic/fcckjobno = SOURCE_PACKAGE-/bic/fcckjobno
       and /bic/fcckjitid = SOURCE_PACKAGE-/bic/fcckjitid.
Then I am getting below error:E:The type of the database table and work area (or internal table) "IT_NEW_SOURCE" are not Unicode convertible.
Can you please advice on this, as performance need to improve in start routine code.
Thank You.

The type of the database table and work area are not Unicode convertible

***Data declaration
TYPES : BEGIN OF t_zle_lagerplanung,
                   SEl, "stores which row user has selected
                   kdauf TYPE zle_lagerplanung-kdauf,
                   kdpos TYPE zle_lagerplanung-kdpos,
                   etenr TYPE zle_lagerplanung-etenr,
                   papiermaschine TYPE zle_lagerplanung-papiermaschine,
                   runnr TYPE zle_lagerplanung-runnr,
                   prio TYPE zle_lagerplanung-prio,
                   werk TYPE zle_lagerplanung-werk,
                   durchmesser TYPE zle_lagerplanung-durchmesser,
                   breite TYPE zle_lagerplanung-breite,
                   anzle TYPE zle_lagerplanung-anzle,
                   lgpla TYPE zle_lagerplanung-lgpla,
                   lgtyp TYPE zle_lagerplanung-lgtyp,
                   art TYPE zle_lagerplanung-art,
                   anzhoehe TYPE zle_lagerplanung-anzle,
                   fa TYPE zle_lagerplanung-fa,
END OF t_zle_lagerplanung.
DATA : it_zle_lagerplanung TYPE STANDARD TABLE OF t_zle_lagerplanung INITIAL SIZE 0,
            wa_zle_lagerplanung TYPE t_zle_lagerplanung.
Here I am getting the data in internal table by using thiis select statement.
SELECT kdauf kdpos etenr papiermaschine runnr prio werk durchmesser breite
              anzle lgpla lgtyp art anzhoehe fa
FROM    zle_lagerplanung INTO CORRESPONDING FIELDS OF TABLE it_zle_lagerplanung
WHERE kdauf IN s_kdauf
AND       KDPOS IN s_kdpos
AND      werk = p_werks.
But while updating the particular field in zle_lagerplanung using this statement
UPDATE zle_lagerplanung from table it_zle_lagerplanung.
it is giving syntax error
"The type of the database table and work area (or internal table)
"IT_ZLE_LAGERPLANUNG" are not Unicode convertible. "
Could any one help me out how to resolve this problem....
Thanks in advance

Dear Shayamal,
XXX....are not Unicode convertible
This error comes while inserting or updating database and the fields are not matching between data base table and structure .
Check you fields of data base table and "zle_lagerplanung" and struture "it_zle_lagerplanung" . There fields must match.
thanks and regrds,
Anup Banerjee

Internal table and work area

Hi,
can anybody explain the concepts of Internal table and work area.Thanks in advance.

hai,
This may help u.
WORKAREA is a structure that can hold only one record at a time. It is a collection of fields. We use workarea as we cannot directly read from a table. In order to interact with a table we need workarea. When a Select Statement is executed on a table then the first record is read and put into the header of the table and from there put into the header or the workarea(of the same structure as that of the table)of the internal table and then transferred top the body of the internal table or directly displayed from the workarea.
Each row in a table is a record and each column is a field.
While adding or retrieving records to / from internal table we have to keep the record temporarily.
The area where this record is kept is called as work area for the internal table. The area must have the same structure as that of internal table. An internal table consists of a body and an optional header line.
Header line is a implicit work area for the internal table. It depends on how the internal table is declared that the itab will have the header line or not.
e.g.
data: begin of itab occurs 10,
ab type c,
cd type i,
end of itab. " this table will have the header line.
data: wa_itab like itab. " explicit work area for itab
data: itab1 like itab occurs 10. " table is without header line.
Internal tables are used for storing records which are obtained as a result when we use select statement on database. internal tables are run time entities and doesn't occupy any memory. they are dynamic.
internal tables are of types.
1. internal tables with header line. [header and body]
2. internal tables with out header line. [only body]
Workarea is the concept which is mainly useful when working with internal tables with out header line.
at any point of time we can access only one record through header of a internal table. every thing should be done [inserting,modifying, reading ] through header only.
ex: data: itab like standard table of mara with header line.
for internal tables with out header line we will create a work area [explicit header] as type of table for storing data into internal table.
ex: data: itab like mara,
wa like mara.
more about internal table types:
Standard table:
The key access to a standard table uses a sequential search. The time required for an access is linearly dependent on the number of entries in the internal table.
You should usually access a standard table with index operations.
Sorted table:
The table is always stored internally sorted by its key. Key access to a sorted table can therefore use a binary search. If the key is not unique, the entry with the lowest index is accessed. The time required for an access is logarithmically dependent on the number of entries in the internal table.
Index accesses to sorted tables are also allowed. You should usually access a sorted table using its key.
Hash table:
The table is internally managed with a hash procedure. All the entries must have a unique key. The time required for a key access is constant, that is it does not depend on the number of entries in the internal table.
You cannot access a hash table with an index. Accesses must use generic key operations (SORT, LOOP, etc.).
Hashed tables
This is the most appropriate type for any table where the main operation is key access. You cannot access a hashed table using its index.
The response time for key access remains constant, regardless of the number of table entries. Like database tables, hashed tables always
have a unique key. Hashed tables are useful if you want to construct and use an internal table which resembles a database table or for
processing large amounts of data.
TYPES VECTOR TYPE HASHED TABLE OF I WITH UNIQUE KEY TABLE LINE.
TYPES: BEGIN OF LINE,
COLUMN1 TYPE I,
COLUMN2 TYPE I,
COLUMN3 TYPE I,
END OF LINE.
DATA ITAB TYPE HASHED TABLE OF SPFLI
WITH UNIQUE KEY CARRID CONNID.
with regards,
B.Sowjanya,
reward points if helpful.

Difference between Field symbols and work area for Internal tables

Hi,
In ECC versions we all know that we need to declare the internal tables without headerline, and for handling the internal tables we need to use exclusive work areas.
Currently i have an issue that we have been asked to use field symbols instead of work areas...can any one help me how to use the field symbols and also let me know how it will improve the performance of the program..
Thanks and Regards,
Kathir

Hi
DATA: WA TYPE ITAB.
LOOP AT ITAB INTO WA.
IF WA-FIELD = .....
ENDIF.
ENDLOOP.[(code]
FIELD-SYMBOLS <WA> TYPE ANY.
LOOP AT ITAB ASSIGNING <WA>.
ENDLOOP.
Now the problem is you can't know the name of the fields of the table at runtime, so you can't write:
IF <WA>-FIELD = .....
ENDIF.
Anyway you can create a field-symbols strcturated like the table:
[code]FIELD-SYMBOLS <WA> TYPE ITAB.
LOOP AT ITAB ASSIGNING <WA>.
IF <WA>-FIELD = .....
ENDIF.
ENDLOOP.
I don't know which are the differences for the performance between to use a field-symbol and to use a structure as work-area.
The differnce between the field-symbols and work-area is the field-symbol is assigned directly to the record, so u don't need to do a MODIFY statament to change something:
LOOP AT ITAB INTO WA.
WA-FIELD =
MODIFY ITAB FROM WA.
ENDLOOP.
LOOP AT ITAB ASSIGNING <WA>.
<WA>-FIELD =
ENDLOOP.
These two pieces of abap code do the same action, so probably the field-symbol improve the performance because it do an access directly to the record without to use an external structure as workarea.
Max

Structure of table and work area are not compatible - table control wizard

Structure of table and work area are not compatible is the error i am getting when specifying my internal table and work area in my table control? What am I doing wrong?

hii
this error comes when you have different structure of work area then internal table..so work area will not work here and you will not be able to append records in internal table.
check strucure of internal table and work area.it should be like below.
TYPES:
BEGIN OF type_s_kna1,
     kunnr LIKE kna1-kunnr,            " Customer Number
     name1 LIKE kna1-name1,            " Name
     vbeln LIKE vbap-vbeln,            " Sales Document
END OF type_s_kna1.
* Internal Table And Work Area Declarations For Customer Details      *
DATA : t_kna1 TYPE STANDARD TABLE OF type_s_kna1,
         fs_kna1 TYPE type_s_kna1.
regards
twinkal

Source and Target Table in the Same schema........will that work in ODI

Hi ,
Is it possible to have my source and target tables in the Same achema.......will it have any performance issues or some other issues in our ODI.......
I would like to know whether it works well or not .........
( To my understanding it wont have any issues ......But I am not 100 % sure on my judgement)
Thanks
AK

Yes, you're correct.
Just be sure about you load strategy, it means, if you need only to insert use the KM Control Append, but if need update too, try the IKM Oracle Incremental Update... I believe that will work better for millions of lines.
Anyway be sure that your database has the necessary tablespaces to manage huge data volume.

Number of SNP tables created during master and work repository creation

Hi All,
I would like to know how many SNP tables are created during Master and work repository creation in
10.1.3.5 v as I remember it was around 147 in earlier version .
Any help will be appreciated
regards,
Palash Chatterjee

Hi Palash ,
ODI master repository have 58 SNP tables
where as work repository have 88 SNP tables
So in total 146 SNP tables are created during Master and work repository creation in
10.1.3.5 .
Thanks,
Sutirtha

Difference between work area and internal tables.

Hi I wanna know the difference between work area and internal tables.
what happend if i give with out header line in internal table.
also how to assosiate work area to internal table in that scenario.

Hi Balaji..
The internal table is an ABAP runtime object which has two parts the Body and the header.
Whereas a work area cannot have a body.. It is mere a field or group of fields which can hold values at runtime..
In the SAP higher versions mySAP ERP, the use of tables with header line is made obsolete.. But there is absolutely no problem with the same..
Just think that when you define an internal table with occurs or with header line statement, the system automatically creates a workarea with this table, using which you can access the contents in the bosy of tyhe table.. You can read a record from the table body to this header or add a record in the header to the internal table body..
When you work with a table ITAB without a header line, you can not use statements like READ TABLE, APPEND, INSERT etc without giving an explicit work area..
Suppose i have an internal table like:
DATA : itab TYPE STANDARD TABLE OF t001.
This table will not have a header with it.
If you will use APPEND itab. The compilor will give error.
Here i will create a work area with same structure of the table.
DATA : e_wa TYPE t001.
Now i will write:
APPEND e_wa TO itab.
READ TABLE itab INTO e_wa WITH KEY xxxxxx
LOOP AT itab INTO e_wa... etc..
In a better approach we use Field symbols with such tables, instead of structures
FIELD-SYMBOLS: <fs_itab> TYPE t001.
So,
LOOP AT itab ASSIGNING <fs_itab>
READ TABLE itab ASSIGNING <fs_itab> etc.. However we can not use field symbols in few cases..
I hope this will help you..
Thanks and Best Regards,
Vikas Bittera.
**Points for usefull answers**

In Answers am seeing "Folder is Empty" for Logical Fact and Dimension Table

Hi All,
Am working on OBIEE Answers, on of sudden when i clicked on Logical Fact table it showed me as "folder is empty". I restarted all the services and then tried still showing same for Logical Fact and Dimension tables but am able to see all my reports in Shared Folders. I restarted the machine too but no change. Please help me out to resolve this issue.
Thanks in Advance.
Regards,
Rajkumar.

First of all, follow the forum etiquette :
http://forums.oracle.com/forums/ann.jspa?annID=939
React or mark as anwser the post that the user gave.
And for your question, you must check the log for a possible corrupt catalog :
OracleBIData_Home\web\log\sawlog0.log

Best practice when FACT and DIMENSION table are the same

Hi,
In my physical model I have some tables that are both fact and dimension table, i.e. in the BMM they are of course separated into Fact and Dim source (2 different units) and it works fine. But I can see that there will be trouble when having more fact tables and I e.g. have a Period dimension pointing to all the different fact tables (different sources).
Seems like the best solution to this is to have an alias of the fact/transaction table and have 2 "copies" of the transaction table (one for fact and one for dimension table) in the physical layer. Only bad thing is that there will then allways be 2 lookups in the same table when fetching data from the dimension and the fact table.
This is not built on a datawarehouse - so the architecture is thereby more complex. Hope this was understandable (trying to make a short story of it).
Any best practice on this? Or other suggestions.

Id recommend creation of a view in the database. if its an oracle DB, materialised views would be a huge performance benefit. you just need to make sure that the MVs are updated when the source is updated.
-Domnic

Problem with Master and Child table

Hi,
Working in jdev 11.1.1.2.0. I have one strange issue. i have master and child tables, the model is working fine with the view link. but when drag drop the same into my jsff. when i query the result 1st time 2 tables are refershing properly and data is coming. but the when i trying to select another row in the 1st table my 2nd table(child table) is not refreshing.
i put partial trigger of the 2nd table as 1st table id.
can any one help wht is issue here.
Edited by: user5802014 on Jul 15, 2010 3:44 PM

Check this post might help you
http://baigsorcl.blogspot.com/2010/03/creating-master-detail-form-in-adf.html

Relation b/w PRPS and RPSCO tables

Hi PS Experts,
What is the Relation b/w PRPS and RPSCO tables
PRPS : WBS (Work Breakdown Structure) Element Master Data
RPSCO : Project info database: Costs, revenues, finances
Thanks in Advance,
Regards,
sudharsan.

Hello Sasikanth Thank u for ur information,
and i need some more information, am working on abap, now i got a requirement in PS,
i want 2 calculate the values like Planned Revenue, Planned Cost, Actuall Rev, Actuall Cost, Actuall Billing, Revenue Taken, Cost Taken, BNS and SNB.
based on i/p parameters: Company Code, Fiscal year and month.
pls let me know how to calculate the above values, its very urgent for me.
Thanks in advance,
sudharsan.

How can I get data in flat file from Pool table and cluster table ?

Hi,
I am working in one Achiving project. My requirement is to get data into flat file from Cluster table and pool table.
Is there any tool avilable to download data into flat file from pool table and cluster table ?
if table name given in the selection screen then data will be downloaded into flat file.
waiting for quick response.
Best Regards,
Bansidhar

Data cannot be retrived directly form the cluster table
as the Cluster results are stored in Cluster Key say for example PCLkey
and form that Key we need to fetch the data
these clustes are not the part of PNP or PNPCE tables
for ur info kindly check

NLS_LENGTH_SEMANTICS and work tables in KMs

Similar Messages

Maybe you are looking for