Internal table - work area not long enough

Subject changed by moderator. Please try to use a more meaningful subject in future
The work area "ITAB" is not long enough. how to solve this problem.
Edited by: Matt on Nov 14, 2008 10:20 AM

please check the order of the fields you are passing to your internal table.
Their can be many possible cases .
a)
internal table has less number of fields and u are passing more fields.
b)
suppose Itab has field Vbeln and it`s length is 10 and u are passing filed having length
12.
Please check that.
Regards
Neha

Similar Messages

ERROR: work area not long enough

Hello experts,
I have a submit event in which I was declaring one work area named "ls_data".
I have a DDIC structure ZNEWEMP999_S.
I wrote,
DATA ls_data type ZNEWEMP999_S.
It's giving an error "The work area "LS_DATA" is not long enough.long enough".
Can any one suggest me how to resolve it.
Regards,
JAVED.

Try this....
SELECT *
 INTO CORRESPONDING FIELDS OF
 TABLE itaBTWO
 FROM ZDOLTARC03
 WHERE SEARCHFLD EQ WAONE-SEARCHFLD
 ORDER BY SEARCHFLD.
Regards,
Rich Heilman

I am getting problem with internal table & work area declaration.

I am working with 'makt' table ..with the table makt i need to work with styles attributes ..so i declared like this
TYPES : BEGIN OF ty_makt,
         matnr TYPE makt-matnr,
         spras TYPE makt-spras,
         maktx TYPE makt-maktx,
         maktg TYPE makt-maktg,
         celltab TYPE lvc_t_styl,
       END OF ty_makt.
DATA : i_makt TYPE TABLE OF ty_makt.
DATA : wa_makt TYPE ty_makt .
    But end of program i need to update dbtable "makt"...i am getting problem with internal table & work area declaration.
i think makt table fields mapping and internal table/work area mapping is not correct. so please help me to get out from this.

Hi Nagasankar,
TYPES : BEGIN OF TY_MATNR,
              MATNR TYPE MAKT-MATNR,
              SPRAS TYPE MAKT-SPRAS,
              MAKTX TYPE MAKT-MAKTX,
              MAKTX TYPE MAKT-MAKTG,
              CELLTAB TYPE LVC_T_STYL, " Its Working perfectly fine..
             END OF TY_MAKT.
DATA: IT_MAKT TYPE STANDARD TABLE OF TY_MAKT,
          WA_MAKT TYPE TY_MAKT.
Its working perfectly fine. if still you are facing any issue post your complete code.
Thanks,
Sandeep

Internal table & Work area

Hi Experts,
I am a novice to ABAP. Can anyone tell me whats the difference b/w internal table and work area. In writing function modules how these will be utilized and in what way.
Regards
ss

HI,
Internal tables are a standard data type object which exists only during the runtime of the program. They are used to perform table calculations on subsets of database tables and for re-organising the contents of database tables according to users need.
http://help.sap.com/saphelp_nw04/helpdata/en/fc/eb35de358411d1829f0000e829fbfe/content.htm
Difference between Work Area and Header Line
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.
The header line is a field string with the same structure as a row of the body, but it can only hold a single row.
It is a buffer used to hold each record before it is added or each record as it is retrieved from the internal table. It is the default work area for the internal table
1) The difference between
whih header line and with out heater line of internal table.
ex:-
a) Data : itab like mara occurs 0 with header line.
b) Data: itab like mara occurs 0.
-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.
a) Data : itab like mara occurs 0 with header line.
table is with header line
b) Data: itab like mara occurs 0.
table is without header line
2)work area / field string and internal table
which one is prefarable for good performance any why ?
-The header line is a field string with the same structure as a row of the body, but it can only hold a single row , whereas internal table can have more than one record.
In short u can define a workarea of an internal table which means that area must have the same structure as that of internal table and can have one record only.
Example code:
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.
http://www.allsaplinks.com/faq_abap_internaltables.html
Do reward if it helps,
Regards,
Laxmi

Internal Table - Work Area issue

Guru's:
I am selecting the mentioned fields from TVAKT into t_itt1 (internal table) - I however an encountering "you canot use an internal table as a work area" as an error.
DATA: s_bezei LIKE tvakt-bezei,
s_auart LIKE tvakt-auart.
DATA t_itt1 LIKE tvakt OCCURS 0.
DATA z_itt LIKE tvakt.
its at this stage of the code that I am facing this problem
SELECT spras auart bezei FROM tvakt
INTO t_itt1
WHERE bezei IN s_bezei
AND auart IN s_auart.
would appreciate your help.

Hello,
You need to change the declaration of the s_spras to use the IN clause:
See these for more informations: http://help.sap.com/saphelp_nw04/helpdata/en/18/a1f251e28b11d295f500a0c929b3c3/frameset.htm and Create a Ranges Table Type.
Regards.

Moving internal table work area data to string

Hi, I am running a program with unicode enable.I am moving data from work area to string where i am getting a error like String & work area are not mutually convertable in Uni code program.
Can any one help me how to resolve this problem.
Thanks & Regards,
Pratap.

Hi Pratap kumar,
sorry, need to do some redesign:
You could poiibly concatenate the components of the structure into a string - if they are all character-like. And you will loose leading and trailing spaces.
Non-character-componets must be converted (WRITE TO) into character-like fields.
If you need the exact position in your string, you have to place all values at calculatzed offset in a (big enough) character field like CHAR1024.
Altogether it might be easier to re-think and re-build according to results required. As you did not mention where you have this question, I have no special idea on how to solve.
Regards,
Clemens

Work area "itab" is not long enough

Hi All,
Here am facing a trouble with internal tables.
I need an internal table for processing. I declared a table type refering to an structure. The program is throwing me an error "Work area "itab" is not long enough. "
Can anyone telme what's wrong with the code?
Thanks,
Anjum.

Hi Nasarat,
if you look at carefully you definitions of tables
TYPES: BEGIN OF tbl,
rc_n TYPE c,
rec_n(2) TYPE n,
END OF tbl.
DATA: itab_org type tbl1 occurs 0 with header line,
itab_rc type tbl1.
your DATA statement referes ITAB_ORG to a Type tbl1 which does not exist in your TYPES statement.
your DATA statement refers to ITAB_ORG is not a internal table but a WORK Area as you have declared it as ITAB_ORG type tbl1.
If you want to declare and internal table ITAB_ORG - decalre it as
Data:ITAB_Org type standard table of tbl.
and define a explicit work area
DATA: wa_org type tbl.
Never use Occurs 0 and Header line as it coccupies lots of memories and your programs may dump in future . So please avoid occurs 0 and header line and instead decalre an explicit WORK AREA.
Similary declaration for internal table ITAB_RC it should be
DATA: ITAB_RC type standard table of tbl,
WA_RC type tbl.
then after these declarations when you do a SELECT statement it should be
SELECT rc_n rec_n into ITAB_ORG from<DB table>.
The fields as declared in types should be called in the same sequence as you have defined above OR use INTO CORRESPONDING-FIELDS OF ITAB_ORG.
Hope this reolves your query and was useful.
if yes please do reward suitably
Thanks
Venugopal

The work area "IT_ITAB" is not long enough

I created a interna table IT_ITAB with OCCURS 0, But it's giving error as
The work area "IT_ITAB" is not long enough.
So pls send the correct syntax to solve the error....

data : it_data like standard table of mara occurs 0 with header line.
Above syntax is not working...its giving error as "OCCURS 0 is not expected".
I have one more dought...In the report I am providing some of the fields from my own database table.
1. Can I provide the fields when using the WITH HEADER LINE concept.?
2.Can I avoid BEGIN OF after "DATA :"?
3.Pls tell me the exact use of STANDARD key word.
4.What is the memory sys assigning dynamically when using OCCURS 0?
5.What is the syntax to increase the memory?

Work area it_input is not long enough

Hi,
when am trying to check this one it is saying that it_input is not long enough.
tables: lfa1.
types: begin of t_input,
lifnr type lifnr,
end of t_input.
data: it_input type standard table of t_input.
data: wa_input type t_input.
select * from lfa1 into table it_input where lifnr = lfa1-lifnr.
write:/ lfa1-lifnr.

hi,
As you are using statement in which select * wil get all the fields in the lfa1 table into your internal table, but you are taking wa_input sturcture type t_input which is having only one field so u are getting error work are is no longer enough.
so u use like this
select lifnr from lfa1 into table it_input where lifnr = lfa1-lifnr.
loop at it_input into wa_input.
write : / wa_input-lifnr.
endloop.
hope this helpful
regards
dilip

The work area (or internal table) "IT_ZLE_LAGERPLANUNG" is not flat,

***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,
         occupied TYPE zle_lagerplanung-text30,
         free TYPE zle_lagerplanung-text30,
           lgpla TYPE zle_lagerplanung-lgpla,
           lgtyp TYPE zle_lagerplanung-lgtyp,
           art TYPE zle_lagerplanung-art,
           anzhoehe TYPE zle_lagerplanung-anzle,
         zindicator TYPE zle_lagerplanung-text30,
           fa TYPE zle_lagerplanung-fa,
           field_style TYPE lvc_t_styl, "FOR DISABLE
END OF t_zle_lagerplanung.
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 = p_kdpos
      AND KDPOS IN s_kdpos
     AND werk = p_werks.
But while updating the particular field in ztable using this statement
      UPDATE zle_lagerplanung from table it_zle_lagerplanung.
it is giving syntax error
"The work area (or internal table) "IT_ZLE_LAGERPLANUNG" is not flat, or
contains reference or internal tables as components. components.
components. components. components."
Could any one help me out how to resolve this problem....
Thanks in advance

Hi Shyamal,
lvc_s_styl is a structure so you will get the same error.
for your select and update statement you dont need field "field_style".
regards
rea

Err: workarea is not long enough...

Hi all,
Please solve this problem.......
Used this Statement in FM....
INSERT zdsd_hh_rahd FROM TABLE lt_rahd_delete.
Where 'zdsd_hh_rahd' is a Transp. Table with 25 fields.
'lt_rahd_delete' is declared as:
DATA: lt_rahd_delete TYPE /dsd/hh_rahd_s_tt.
'/dsd/hh_rahd_s_tt' is a Table Type.
Has Line Type as: '/DSD/HH_RAHD_S',
Key Defination as: Key component.
'/DSD/HH_RAHD_S' is a Structure refering to Table '/DSD/HH_RAHD'.
'/DSD/HH_RAHD' and 'zdsd_hh_rahd' hase the same fields.
But i am with an Error saying that:
Workarea 'lt_rahd_delete' is not long enough...
Edited by: CHELIKANI KUMAR on Dec 20, 2007 5:50 PM

Use INSERT zdsd_hh_rahd FROM TABLE lt_rahd_delete ACCEPTING DUPLICATE KEYS.
Work area wa should always be declared in the ABAP Dictionary with respect to the database table or the view so Declare
Data:lt_rahd_delete type zdsd_hh_rahd occurs 0.
Pls Let me know the Status.
Kanagaraja L
Edited by: Kanagaraja Lokanathan on Dec 20, 2007 1:07 PM

Apple A/V cable not long enough

it seems to me I can't connect the two audio jacks to my Stereo when I have the yellow Video one in the TV - - NOT LONG ENOUGH! (the 3-cable part) - i would'nt mind but my stereo is directly under my TV
the video cable needs to be longer I think - - or the two audio ones - or maybe all 3 then.....also, when those two audio L/R are to stereo, there is no more to feed to TV, so sound from the stereo only, none from TV
- so what to do about this? - if anyone knows about splitters or cable extensions, show me jah light

You can go to Radio Shack, Best Buy, etc. and get a generic camcorder A/V-to-RCA cable. The cable will have the longer head phone jack like the Apple A/V cable but may come in longer lengths. One note though, the normal color outputs using the camcorder cable are not correct when using it with an iPod.
Plug the red RCA plug into your TV's yellow RCA jack.
Plug the yellow RCA plug into your TV's white RCA jack.
Plug the white RCA plug into your TV's red RCA jack.
See for details:
http://www.macdevcenter.com/pub/a/mac/2005/11/18/video-ipod.html
<Added> - After I posted a reply I noticed you're in Dublin, so the stores I listed may not make sense. Go to any electronics store and ask for the camcorder cable I mentioned. If they don't have a cable long enough for you, ask for a RCA jack extension cable. That will work too.

Regarding tables work area,events in reporting,LSMW

Hai to All,
1. Sequence of events in classical & interactive reporting.
2. Why call transaction does not support LSMW
(Legasy System Migration Workbench)
3. We have to provide tables work area in the declaration when select-options logic is used but it is not mandatory in parameters selection screen logic why?
4. what is the reason for maintaining loop ... endloop logic under PAI in the case of table control
please provide answers for these quections
regards,
suryanarayana k.

Hi
1. Sequence of events in classical & interactive reporting.
Events in ABAP Programming
Classical Reporting:
INITIALIZATION
AT SELECTION-SCREEN OUTPUT
AT SELECTION-SCREEN
START-OFSELECTION.
TOP-OF-PAGE
END-OF-PAGE
END-OF-SELECTION.
Events in Interactive Report
TOP-OF-PAGE DURING LINE-SELECTION
AT USER-COMMAND.
AT LINE-SELECTION
AT PF-FUNCTION KEY
2. Why call transaction does not support LSMW
(Legasy System Migration Workbench)
http://www.sapbrain.com/TOOLS/LSMW/SAP_LSMW_steps_introduction.html
http://esnips.com/doc/8e732760-5548-44cc-a0bb-5982c9424f17/lsmw_sp.ppt
http://esnips.com/doc/f55fef40-fb82-4e89-9000-88316699c323/Data-Transfer-Using-LSMW.zip
http://esnips.com/doc/1cd73c19-4263-42a4-9d6f-ac5487b0ebcb/LSMW-with-Idocs.ppt
http://esnips.com/doc/ef04c89f-f3a2-473c-beee-6db5bb3dbb0e/LSMW-with-BAPI.ppt
http://esnips.com/doc/7582d072-6663-4388-803b-4b2b94d7f85e/LSMW.pdf
for Long texts Upload
Please take a look at this..
http://help.sap.com/saphelp_erp2005/helpdata/en/e1/c6d30210e6cf4eac7b054a73f8fb1d/frameset.htm
3. We have to provide tables work area in the declaration when select-options logic is used but it is not mandatory in parameters selection screen logic why?
When youd eclarae select-options by default it creates a selection table with 4 fields called SIGN,OPTIOn,LOW and HIGH fields
Paramters its' not like that
4. what is the reason for maintaining loop ... endloop logic under PAI in the case of table control
Table control means handling multiple records , so to process/handle them it is a must to use loop.endloop.
Reward points for useful Answers
Regards
Anji

DRQ: Field "Title" in OCPR not long enough

In the moment, the field Title in the table OCPR has max. 10 characters.
We have many customers were this field is not long enough. Especially academic contact persons wants to be called with the complete and correct title. Constructs like "Prof. Dr. Dr. med. mult." are not impossible.
Therefore, I request to expand the field Title to 50 characters.
Kind regards,
Jürgen Hansen
Computer im Büro Dr. Grüneberg GmbH
Berlin, Germany
Edited by: Jürgen Hansen on Apr 20, 2011 1:40 PM "DRQ: " added in Title

Hello Ludek,
                I have found that the issue is caused by the bold attributes of my field.
                You can try the following and you should encounter the same issue:
                                - Create a Report
                                - Create a formula with many characters
                                - Put you field in Times New Roman bold 8.
                The following Font Size in Times New Roman are in issue: 5 u2013 8 u2013 11- 14
                The following Font Size in Arial are in issue: 8 u2013 11 u2013 12 u2013 14
Thank you.
Charles
Edited by: Charles Gagnon on May 2, 2011 5:38 PM

E-Recruiting: ALE Status 51 Posting Error - "Password is not long enough"

Hi experts!
We are having problems occationally posting idocs in our nightly ALE transfer from SAP to E-Recruiting. The error for the segment with a status 51 is "Password is not long enough (minimum length: 6 characters)". The system is trying to post IT0105 Sty 1.
This only seems to happen when either a new user is created in our SAP system. We are running SAP ECC 6.0 and E-Recruiting 6.0 sp10. In both systems you are required to have a password length of at least six characters.
Users in our SAP system are needed in E-Recruiting for the purpose of identifying internal candidates.
If both systems currently require that you have a password length of at least six characters, why would we recieve this error message when attempting to post idocs?
The concern here, obviously, is that if one segment fails to post in the idoc, the entire idoc fails to post.
Any help would be appreciated!
Thanks!
Ryan

Hello,
We are still having a problem with failing iDocs everytime we pass over IT0105 Sty 1 records from our SAP system to E-Recruiting.
Would anyone happen to know where I should start looking to troubleshoot this error message?
"Password is not long enough (minimum length: 6 characters)"
Currently both systems require that your password be at least 6 characters long, which makes this message even more perplexing.
Having a better understanding of how RBDAPP01 processes inbound IDOCS in status 64 would help. We are using message type HRMD_ABA. Our data filter looks like....
Infotype: 1000
Object Type: C, O, S
Infotype: 1001
Object Type: C, O, S
Subtypes: A002, A007, A008, A012, B002, B007, B008, B012
Infotype: 1001
Object Type: O, S
Subtypes: A003, B003
Infotypes: 0000, 0001, 0002
Object Type: P
Infotype: 0006
Object Type: P
Subtype: 1
Infotype: 0105
Object Type: P
Subtypes: 0001, 0010
So the question is how is IT0105 Sty 1 being processed when RBDAPP01 runs?
Thank you for your help!
Ryan
Edited by: Ryan Hubbell on Mar 31, 2009 7:00 PM
Edited by: Ryan Hubbell on Mar 31, 2009 7:47 PM

Internal table - work area not long enough

Similar Messages

Maybe you are looking for