Type ref to a table

Hi Experts,
I have an FM returning a variable which is :
abc type ref to data.
This actually returns a table at runtime.
However since its declaration is such, I capture the reference in another variable
xyz type ref to data.
Now I need to know whether the xyz table has one row or more.
How can I do that?
Thanks and Regards,
Ravi Bhatnagar

Try something like this. Assign the data ref to a field symbol, then use the LINES operator to find out the number of lines.
DATA: lo_ref TYPE REF TO data.
DATA: lv_lines TYPE i.
FIELD-SYMBOLS: <fs_tab> TYPE table.
ASSIGN lo_ref->* TO <fs_tab>.
lv_lines = LINES( <fs_tab> ).
Regards,
Rich Heilman

Similar Messages

Error while determining ref.mov.type for WM via Table 156S: 647/ / / /L/ /

Guyz,
Firstly despite the plant+storage location + warehouse no. assignments are done , my replenishment delivery (delivery for stock transport order between plants under same company code) is not picking up storage location and warehouse no and thus stopping me from doing picking and PGI (post goods issue).
However in VL02N when i'm trying to change storage location for line item, i'm getting following weird error
*Error while determining ref.mov.type for WM via Table 156S: 647/ / / /L/ /*
I found a SAP Note(133223) regarding this error and VL02 transaction but that note was specific to older versions. I'm on ECC 6.0
Any suggestions please ?
Thanks

Warehouse managment has its own movement types, most identical to inventory management movement types.
These WM movement types are determined via reference movement types.
the error you have just looks like your customizing is not complete.
IMG > LE > WM > Interfaces > IM > define movement types.

Error messag -'Error while determining ref.mov.type for WM via Table 156S:'

Hi Guys,
I am currently facing some issues with respect to the deliver creation.
The scenario is somthing like this.
I have assigned a FOC Item category to an Consignment Issue order type.
The system is able to determine the Item category successfully.
However when the delivery is created it throws an error message
'Error while determining ref.mov.type for WM via Table 156S: 903/X/X/W/L/X/'
Not sure why this occurs.
All the settings seem to be set.
If any one of you can help me out it would be great.
Thanks.
Regards,
Pandi

Dear Pandiraj
The standard process is that consignment issue order should be created with reference to Proforma invoice. Having said that I dont understand why you have assigned a FOC item category to issue order. Not sure, whether this will work. Also I feel that you should explain in detail the process for which you are configuring this.
thanks
G. Lakshmipathi

Error while determining ref.mov.type for WM via table 156S:601///

Hi SAP gurus
while doing delivery i am getting error like
Error while determining ref.mov.type for WM via table 156S:601///
please give me needful solution
regards
Sarvesh

Chk via
SPRO>LE>WM>Interfaces>IM>Define mvt>Assign MVt reference...and then LE-WM interface...
maintina the correspoding entries..
BR,
Krishna

Add line to type ref to data field - type table

HI All,
I have field that is defined as type ref to data ,and the type of it is table with data inside of it lr_data.
I have the also the table type of lr_data and I want to add additional line to the type ref to data field.
How can i do that ?
For example
TYPES: BEGIN OF bank_list,
         country_key type string,
         bank_key    type string ,
         bank_name   type string,
         bank_city type string    ,
       END OF bank_list.
data lt_bank type table of bank_list.
data lr_data data ref to data.
Now lr_datae is type lt_bank " in _Runtine
and contain 4 entries .
I get the lr_data with 4 entries and I want to add new entry to the table.
How can I do that?
Thanks,
Joy
Edited by: Joy Stpr on Feb 8, 2012 10:05 PM

Hello Joy,
You can check this code snippet to get an idea on how to proceed with your requirement:
CLASS lcl_add_data DEFINITION.
PUBLIC SECTION.
    CLASS-METHODS add_data CHANGING ch_data TYPE REF TO data
                           EXCEPTIONS err_invalid_type.
ENDCLASS.                    "lcl_add_data DEFINITION
*       CLASS lcl_add_data IMPLEMENTATION
CLASS lcl_add_data IMPLEMENTATION.
METHOD add_data.
    DATA: lo_tabdescr   TYPE REF TO cl_abap_tabledescr,
          lo_strucdescr TYPE REF TO cl_abap_structdescr,
          ls_component TYPE abap_compdescr.
    FIELD-SYMBOLS: <lt_data>      TYPE STANDARD TABLE,
                   <ls_data>      TYPE any,
                   <lv_fieldval> TYPE any.
    IF ch_data IS BOUND.
*     Get the runtime type object
      lo_tabdescr ?= cl_abap_typedescr=>describe_by_data_ref( ch_data ).
*     Check if supplied param is table
      IF lo_tabdescr->type_kind NE cl_abap_typedescr=>typekind_table.
        RAISE err_invalid_type.
      ENDIF.
    ELSE.
      RETURN.
    ENDIF.
    ASSIGN ch_data->* TO <lt_data>. "Dereferencing the data reference
*   Get the line type of table
    lo_strucdescr ?= lo_tabdescr->get_table_line_type( ).
    DO 2 TIMES.
*     Add initial line to the table
      APPEND INITIAL LINE TO <lt_data> ASSIGNING <ls_data>.
      CLEAR <ls_data>.
*     Loop on the fields of the structure & populate them
      LOOP AT lo_strucdescr->components INTO ls_component.
        ASSIGN COMPONENT ls_component-name OF STRUCTURE <ls_data> TO <lv_fieldval>.
        CASE ls_component-name.
          WHen 'COUNTRY_KEY'.
            <lv_fieldval> = `My Country`.
          WHEN 'BANK_KEY'.
            <lv_fieldval> = `123`.
          WHEN 'BANK_NAME'.
            <lv_fieldval> = `My Bank`.
          WHEN 'BANK_CITY'.
            <lv_fieldval> = `My City`.
        ENDCASE.
      ENDLOOP.
    ENDDO.
ENDMETHOD.                    "add_data
ENDCLASS.                    "lcl_add_data IMPLEMENTATION
TYPES:
BEGIN OF bank_list,
country_key TYPE string,
bank_key    TYPE string,
bank_name   TYPE string,
bank_city   TYPE string,
END OF bank_list.
DATA: lt_bank TYPE STANDARD TABLE OF bank_list,
      lr_data TYPE REF TO data.
START-OF-SELECTION.
GET REFERENCE OF lt_bank INTO lr_data. "Get reference
* Add the data to the data reference
lcl_add_data=>add_data( CHANGING    ch_data = lr_data
                          EXCEPTIONS err_invalid_type = 1 ).
BR,
Suhas

Using REF with object table in SQL Developer

When i create object tables and fill them with data, then in SQL Developer de REF value isn't displayed.
I did the following:
CREATE TYPE adres_type AS OBJECT
(straat VARCHAR2(20)
,nummer VARCHAR2(10)
,postcode VARCHAR2(6)
,plaats VARCHAR2(50));
CREATE TABLE adressen of adres_type;
CREATE TYPE locatie_type AS OBJECT
(nr NUMBER
,naam VARCHAR2(20)
,adres REF adres_type);
CREATE TABLE locaties OF locatie_type;
CREATE TABLE locaties OF locatie_type
(SCOPE FOR (adres) IS adressen);
insert into adressen values (adres_type('Arnhemsestraatweg', '33','6881ND','Velp'));
insert into locaties values (1,'Directie', (select ref (a) from adressen a where a.plaats = 'Velp'))
Then in SQL Developer de REF(A) column is empty, while in SQL*Plus it displays the REF value:
In SQL Developer: SELECT a.*, REF(a) FROM adressen a;
STRAAT NUMMER POSTCODE PLAATS REF(A)
Arnhemsestraatweg 33 6881ND Velp
In SQLPLUS: SELECT a.*, REF(a) FROM adressen a;
STRAAT NUMMER POSTCODE PLAATS REF(A)
Arnhemsestraatweg 33 6881ND Velp 0000280209C70341FBB96B4F77813B27B50E53BB4332382E22ADD64AD9B755F651D416B6DA010134
Is this a bug or is there another reason why the ID doesnt display in SQL Developer.
(this didnt work in all the previous SQL Developer releases and still not in de 2.1 E.A. version)

Hi <not sure of your first name>,
I have replicated the issues and logged a bug against this
Bug 9102579 - FORUM: REF FUNCTION NOT RETURNING CORRECT RESULT
Regards,
Dermot O'Neill
SQL Developer Team

Add column to user defined type based on existing table

Hello guys,
I am trying to compile my function which returns a user defined type based on existing table. Throughout the initializing process though my query returns one additional column - SCORE(1). Here is my package:
create or replace
PACKAGE STAFF_AGENCY_PKG AS
TYPE TYPE_SEEKER_TABLE IS TABLE OF TOSS.SEEKER%ROWTYPE;
FUNCTION GET_SEEKERS(IN_KEYWORD IN VARCHAR2)
RETURN TYPE_SEEKER_TABLE PIPELINED;
END STAFF_AGENCY_PKG;
create or replace
PACKAGE BODY STAFF_AGENCY_PKG
AS
FUNCTION GET_SEEKERS(IN_KEYWORD IN VARCHAR2)
RETURN TYPE_SEEKER_TABLE PIPELINED
IS
R_TBL TYPE_SEEKER_TABLE; -- to be returned
BEGIN
FOR R IN(
SELECT Seeker.SEEKER_ID,
Seeker.FIRSTNAME,
Seeker.LASTNAME,
Seeker.NATIONALITY,
Seeker.ISELIGIBLE,
Seeker.BIRTHDATE,
Seeker.ISRECIEVEEMAILS,
Seeker.HIGHESTDEGREE,
Seeker.ETHNICITY,
Seeker.GENDER,
Seeker.ISDISABILITY,
Seeker.DISABILITY,
Seeker.CV,
Seeker.PASSWORD,
Seeker.PREFFERED_CITY,
SEEKER.EMAIL,
SEEKER.JOB_PREFERENCES_ID,
SCORE(1)
FROM SEEKER Seeker
WHERE CONTAINS(CV, '<query>
<textquery lang="ENGLISH" grammar="context">' ||
GET_RELATED_CATEGORIES(IN_KEYWORD) ||
'</textquery>
<score datatype="INTEGER"/>
</query>', 1) > 0
LOOP
PIPE ROW(R); --Error(38,10): PLS-00382: expression is of wrong type
END LOOP;
RETURN;
END GET_SEEKERS;
END STAFF_AGENCY_PKG;
How do I need to amend my user type in order to suffice?
Oracle Release 11.2.0.1.0
Many thanks in advance!

>
How do I need to amend my user type in order to suffice?
>
You will need to create two new TYPEs. One that has all of the columns of the TOSS.SEEKER table and the new SCORE column and then a TYPE that is a table of the first type.
See the Example 12-22 Using a Pipelined Table Function For a Transformation in the PL/SQl language reference
http://docs.oracle.com/cd/B28359_01/appdev.111/b28370/tuning.htm#i53120
Here is the first part
-- Define the ref cursor types and function
CREATE OR REPLACE PACKAGE refcur_pkg IS
TYPE refcur_t IS REF CURSOR RETURN employees%ROWTYPE;
TYPE outrec_typ IS RECORD (
    var_num    NUMBER(6),
    var_char1 VARCHAR2(30),
    var_char2 VARCHAR2(30));
TYPE outrecset IS TABLE OF outrec_typ;
FUNCTION f_trans(p refcur_t)
      RETURN outrecset PIPELINED;
END refcur_pkg;
CREATE OR REPLACE PACKAGE BODY refcur_pkg IS
FUNCTION f_trans(p refcur_t)
   RETURN outrecset PIPELINED IS
    out_rec outrec_typ;
    in_rec p%ROWTYPE;
BEGINModify
TYPE outrec_typ IS RECORD (
    var_num    NUMBER(6),
    var_char1 VARCHAR2(30),
    var_char2 VARCHAR2(30));
TYPE outrecset IS TABLE OF outrec_typ;to include all of the columns you need. Unfortunately you will have to manually list all of the columns of the TOSS.SEEKER table. If you expect to need this same structure in other places you should create them as SQL types instead of PL/SQL types.
This example should be enough to show you how to change your code to do something similar.

Matrix with LinkButton refer to different Table

how to build something like SBO Incoming Payments Matrix?
means:
1. it display Docnum but it can refer to DocEntry
2. it can refer to different table (if Document Type is IN it refer to A/R Invoice, CN refer to A/R Credit Notes)
thanks

yes, it work..but strange if it open new A/R Invoice for different row
i need to manage the Count property at .GetForm method
something like this
Dim oForm As SAPbouiCOM.Form
                oSBO.Menus.Item("2053").Activate()
                Try
                    oBGMatrix.GetLineData(pVal.Row)
                    oForm = oSBO.Forms.GetForm(133, 1)
                    oForm.Mode = SAPbouiCOM.BoFormMode.fm_FIND_MODE
                    Dim oItem As SAPbouiCOM.Item
                    Dim oEdit As SAPbouiCOM.EditText
                    oItem = oForm.Items.Item("8")
                    oEdit = oItem.Specific
                    oEdit.Value = ColInvNo_UDS.Value
                    'oItem = oForm.Items.Item(NameTb_UID)
                    'oNameTb = oItem.Specific
                    'oNameTb.DataBind.SetBound(True, "", NameTb_UID)
                    oForm.Items.Item("1").Click(SAPbouiCOM.BoCellClickType.ct_Regular)
                    BubbleEvent = False
                Catch ex As Exception
                    oSBO.StatusBar.SetText(ex.Message, SAPbouiCOM.BoMessageTime.bmt_Short)
                End Try
thanks Petr

Passing value from field symbol / variable type ref to data to variable

hey ,
DATA: NODE_FLIGHTS TYPE REF TO IF_WD_CONTEXT_NODE.
DATA: RT_CARRID TYPE REF TO DATA.
FIELD-SYMBOLS: <FS_CARRID> TYPE TABLE
.* Retrieve the data from the select option
RT_CARRID = WD_THIS->M_HANDLER->GET_RANGE_TABLE_OF_SEL_FIELD( I_ID = 'S_WEIGHT).
Assign it to a field symbol
ASSIGN RT_CARRID->* TO <FS_CARRID>.
how can i pass RT_CARRID or <FS_CARRID> to a varible with type vbap-netgrw ( net weight ) ?
thanks
ASA

>
ASA MOKED wrote:
> hey ,
>
>
> DATA: NODE_FLIGHTS TYPE REF TO IF_WD_CONTEXT_NODE.
>   DATA: RT_CARRID TYPE REF TO DATA.
>   FIELD-SYMBOLS: <FS_CARRID> TYPE TABLE
>
> .* Retrieve the data from the select option
>   RT_CARRID = WD_THIS->M_HANDLER->GET_RANGE_TABLE_OF_SEL_FIELD( I_ID = 'S_WEIGHT).
> * Assign it to a field symbol
>   ASSIGN RT_CARRID->* TO <FS_CARRID>.
create a work area of type <FS_CARRID>.
field-symbol: <fs_wa> type line of <FS_CARRID>.
loop at <FS_CARRID> into <fs_wa>.
lv_netgr = <fs_wa>-netgr.

Data: stru_tab type ref to data? what data refers to?

Dear friends,
                     Relatively iam new to WDA. can u please explain me below statement.
data: stru_tab type ref to data.

Actually there are not really any Web Dynpro sepecific data types. The ones mentioned are simply data dictionary data types that are defined for use with WD, but can be used in any ABAP applications. You should start your research with just ABAP data types. Look in the ABAPDOCU transaction or search the keyword documentation for DATA. There is lots of documentation on the ABAP native data types.
Here is a little bit of it:
Predefined ABAP Types
The table below shows the predefined ABAP types. Additional attributes can be found under value ranges and initial values.
Type Length Standard length Description
b 1 Byte   1 byte integer (internal)
c 1 to 65,535 characters 1 character Text field
cursor as i as i Database cursor
d 8 characters   Date field
f 8 bytes   Floating point number
i 4 bytes   4 byte integer
n 1 to 65,535 characters 1 character Numeric text
p 1 to 16 bytes 8 bytes Packed number
string variable   Text string
s 2 bytes   2 byte integer (internal)
t 6 characters   Time field
x 1 to 65,535 bytes 1 byte Byte field
xstring variable   Byte string
These types are predefined in every ABAP program.
All predefined ABAP types in this table are elementary.
Apart from the types b and s, the predefined ABAP types can also be used to define your own data types and data objects and for typing. The types b and s cannot be specified directly in ABAP statements. Self-defined data types and data objects in ABAP programs are of the data type b and s if they are defined with reference to data elements to the ABAP Dictionary which are of the external data types INT1 or INT2.
The predefined data types string and xstring describe data objects of variable length (dynamic data objects). While the length of data objects in all other elementary data types is determined for its whole lifetime, the length of text and byte strings varies according to their content (the maximum size of a string is determined by profile parameter ztta/max_memreq_MB, see Maximum size of dynamic data objects).
The program-globally predefined data type cursor is currently synonymous with the predefined ABAP type i. This is required for the declaration of a cursor variable for database cursor handling.
All predefined ABAP types for which a length interval is specified in second column in the table are generic, which means that the length is not part of the type description. For the type p, the fractional portion is indefinite as well as the length.
The entries in the standard length column specify the length that is used for the corresponding generic data type when declaring data objects, if no explicit length is specified in the relevant statement.
In Unicode systems, the length must either be specified in characters and bytes. In non-Unicode systems, the length of a character is one byte, but in Unicode systems the length of a character depends on which Unicode character representation is used.
Generic ABAP Types
The following table shows the predefined generic ABAP types. A generic data type is an incomplete type specification that includes several complete type specifications. The generic types can be used for the typing of field symbols and formal parameters. The only generic type that can be used for typing of data references is the predefined type data. The predefined generic type for object references is object. When a data object is assigned to generically typed field symbols using the statement ASSIGN, or to a formal parameter in procedure calls, the system checks whether its concrete data type is a of the generic type, or is compatible with it.
Type Description
any Any data type (suitable for any type)
any table Internal table of any table type
c Text field of generic length
clike Character-type (c, d, n, t, string and character-type flat structures); in non- Unicode programs also x, xstring and any flat structures
csequence Text-type (c, string)
data Any data type
hashed table Hashed table
index table Index table
n numeric text of generic length
numeric Numeric (b, i, p, f, s)
object Any object type (root class of the inheritance hierarchy)
p Packed number of generic length and generic number of decimal places
simple Elementary data type including structured types with exclusively character-type flat components
sorted table Sorted table
Standard table Standard table
table Standard table
x Byte field of generic length
xsequence byte-type (x, xstring)
The genric types clike, csequence, numeric,simple, and xsequence are available as of release 6.10.
Notes
The generic type any currently has the same effect in typing as the generic type data. When declaring references, any cannot yest be specified after REF TO. Generic data references (REF TO data) or generic object references (REF TO object) are possible. The generic type object can currently only be specified after REF TO.
Except for the built-in generic types illustrated in the table above, there are at the moment no self-defined generic types in ABAP with only one exception: A table type defined with TYPES - TABLE OF or defined in the ABAP Dictionary without completely specifying the table key, is also generic.
Predefined Types in the ABAP Dictionary
The following table lists the predefined types in the ABAP Dictionary. These types cannot be used directly in ABAP programs, and are therefore known as external data types. Instead, they are used in the ABAP Dictionary for the definition of data types to which ABAP programs can refer. The predefined data types of the ABAP Dictionary must also be taken into account in Open SQL statements and when working with screens: Open SQL statements work with database tables defined in the ABAP Dictionary whose colums have external data types. Screen fields are also declared in the Screen Painter with reference to external data types.
Type Permitted Places m Meaning ABAP Type
ACCP 6 Accounting period n(6)
CHAR 1-255 Character string c(m)
CLNT 3 Client c(3)
CUKY 5 Currency key c(5)
CURR 1-31 Currency field p((m+1)/2)
DATS 8 Date d
DEC 1-31 Calculation/amount field p((m+1)/2)
FLTP 16 Floating point number f(8)
INT1 3 1 byte integer b
INT2 5 2 byte integer s
INT4 10 4 byte integer i
LANG 1 Language c(1)
LCHR 256-... Long character string c(m)
LRAW 256-... Long byte string x(m)
NUMC 1-255 numerischer Text n(m)
PREC 2 Accuracy of a quantity field s
QUAN 1-31 Quantity field p((m+1)/2)
RAW 1-255 Byte sequence x(m)
RAWSTRING 256-... Byte sequence xstring
SSTRING 1-255 Character string string
STRING 256-... Character string string
TIMS 6 Time t
UNIT 2-3 Unit key c(m)
For types LCHR and LRAW, the maximum number of places in a transparent database table is the value of the preceding INT2 field.
The types RAWSTRING and STRING have a variable length. A maximum length for these types can be specified, but has no upper limit.
The type SSTRING is available as of release 6.10 and it has a variable length. Its maximum length must be specified and is limited to 255. The advantage of this type compared with CHAR, is that it is assigned to the ABAP type string.
The table below shows the data types of the ABAP Dictionary that are based on the predefined types in the above table, and that can be addressed in an ABAP program. The elementary components of these data types are converted to predefined ABAP data types according to the final column in the above table, whereby the number of places m of each type is converted to lengths.
Data types in the ABAP Dictionary Data types in ABAP
Data element Elementary data type, Reference type
Structure, Database table, View Structured data type
Table type Table type
Note
As of release 6.20, a component of structures or database tables that has the type LANG can be identified as a text language. The text language is used for the conversion of character-type components of the structure when importing data from data clusters and for RFC between MDMP systems and Unicode systems.

Cancel button on form of type form on a table or view

I am a newbie for apex. I am using 10g. I have created form on table emp(empno , name , salary ) . Form is of type Form on a Table or View.
Cancel & Save(Apply changes) button are not working at all. so I copied process reset page and execute on condition save button click. But still cancel button is not working. applcation has some other forms of type Form with a Report and are working properly. I have wasted 2 days on this problem.

Hi,
You can do that. If you have the branch to in the same form what you have to do use clear cache for that page. Click on the edit page, click on the cancel button in the left button section. scroll down to bottom and type the page 32 in the Clear cache field. However it is better to have branch to the report page (different page from the form).
Hope this will help.
M Tajuddin
http://tajuddin.whitepagesbd.com

How to refer to Excel tables (ListObjects) in PowerPivot

I am trying to figure out how to import ListObjects in PP.
As far as I can tell PP does not seem to "see" range names that refer to entire ListObjects i.e. =T_DTL[#All], while it "sees" ranges that refer to direct cells i.e. =Dtl!$O$3:$V$46.
Is that correct and is there a way to work around it?
The reason I am asking is that the tables I want to work with do not necessarily start on line 1 and PP references entire worksheets i.e. Dtl$, as per my example above.I tried different approaches with dynamic ranges but PP refuses to present them as choices
while Selecting Tables and Views. The only way to achieve what I need is by creating named ranges with hardcoded start and end, which is a bit odd since Tables (ListObjects) are a powerful tool since Excel 2007 and I would expect a stronger integration with
other powerful tools such as PowerPivot.Apart from the overhead of having to go through each workbook and define a range for every Table I wish to use.
Am I missing something here?

My PowerPivot attempt was abruptly broken about a month ago, hence my very late reply.
Peter is quoting VBA statements on how to refer to a Table (ListObject), which is familiar to me as I am also writing VBA code. Unfortunately my problem is in interactive mode, not in code execution.
When we open a file's PowerPivot window from within Excel we are prompted to select the tables we want to work with. That is where I cannot see my ListObjects / Tables. I am presented with all ranges that PowerPivot sees as declared in the file that I am
opening (as in Formulas / Names Manager) EXCEPT for the ListObjects. Those are missing.
Try it if you will and let me know if this behavior is relevant only to my installation or to yours as well.
George Thalassinos

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

CO-PA: Can we activate Movement Types in the summary table of CO-PA

Hi SAP Financials experts,
Are we able to activate Movement Types in the summary table of CO-PA when we extract into BW? At the moment, I understand that we are only pulling in YTD
Thanks

Hi
I dont think Mvt Types can be activated in COPA summary table.. Have never heard of this
Br, Ajay M

Type ref to a table

Similar Messages

Maybe you are looking for