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.

Similar Messages

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

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

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

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

Time out error 1.6 million internal table fields are computed using FMs

Hi , All ...
The Report running fine in server with less 300 record but ...production server which has 1.6 million record it gives error as time-out error and takes hell amount of time.
Please suggest ugently ..
I have tried few things
Internal table having 1.6 lacs ... fields to compute .. i have token in a batch
loop at i_cinfo into s_cinfo from 1 to 100000.
and so on ...also applied all the performace related .. like indexs, work areas , deleting adjacent duplicates , for all entries ..wherever applicable.
Please Suggest .
Report is as below
REPORT ZUSOTCBD_CREDIT_REPORT .
TABLES : KNA1, " General Data Customer Master
 KNB1, " Customer Master (Company Code)
 KNC1, " Customer master (transaction figures)
 KNKK, " Customer master credit management: Control area data
 T009, " Fiscal Year Variants P
 T009Y, " Shortened fiscal years in Asset Accounting P
 T001, " Co. Codes
 T001CM, " Permitted Credit Control Areas per Company Code
 RF42B, " Structure to hold credit data.
 RF035, " Structure to hold credit managment fields
 RF02L, " Structure to hold credit data.
 TRAS, " Interval for Days in Arrears P
 T000CM. " Data for DSO calculation.
Types
TYPES:
BEGIN OF type_final,
 string(50) TYPE c, " String Value for Title
END OF type_final.
data:wa_final TYPE type_final. " Work Area to hold Title Data
DATA: RASID TYPE RF035-RASID value 'R03N'. " For Days in interval
DATA: MONAT(2) TYPE N.
DATA: GJAHR TYPE KNC1-GJAHR.
DATA: LD_PERIODS(32) TYPE N
 VALUE '01020304050607080910111213141516'.
DATA sytabix type sy-tabix.
DATA LAND TYPE KNA1-LAND1 VALUE 'US'. " Country Key
DATA: LD_PERIOD TYPE BSID-MONAT, " Fiscal Year Variant
 LD_GJAHR TYPE KNC1-GJAHR,
 LD_COUNTER TYPE SY-TABIX.
Internal Tables
Internal table to hold Title Data *
DATA:
i_final TYPE STANDARD TABLE OF type_final.
**Internal Table Permitted Credit Control Areas per Company Code
DATA: BEGIN OF TCMTAB OCCURS 10.
 INCLUDE STRUCTURE T001CM.
DATA: END OF TCMTAB.
*Internal table to store Customer no.
DATA : BEGIN OF ICUST OCCURS 0,
 KUNNR TYPE KNA1-KUNNR, " Customer No.
 END OF ICUST.
DATA: BEGIN OF BUKTAB OCCURS 20,
 KKBER LIKE T001-KKBER, " Credit Control Area
 BUKRS LIKE T001-BUKRS, " Co. Code
 WAERS LIKE T001-WAERS, " Currency
 PERIV LIKE T001-PERIV, " Fiscal Year Variant
 BUTXT LIKE T001-BUTXT,
 END OF BUKTAB.
Internal Table to store Fiscal year Data .
DATA: BEGIN OF GJATAB OCCURS 5,
 PERIV LIKE T001-PERIV, " Fiscal Year Variant
 GJAHR LIKE KNC1-GJAHR, " Fiscal Year
 MONAT LIKE T009-ANZBP, "
 ANZBP LIKE T009-ANZBP, " Number of posting periods
 END OF GJATAB.
*Main Output internal table to be used to store credit history Information
DATA : BEGIN OF I_CINFO occurs 0,
 KUNNR TYPE KNB1-KUNNR, " Customer
 KNKLI TYPE KNKK-KNKLI, " Customer's account number with credit limit reference
 KKBER TYPE KNKK-KKBER, " Credit Control Area
 CTLPC TYPE KNKK-CTLPC, " Risk Category
 KLIMK TYPE KNKK-KLIMK, " Credit Limit
 SBGRP TYPE KNKK-SBGRP, " Credit representative group for credit management
 ERDAT TYPE KNKK-ERDAT, " Created On
 DTREV TYPE KNKK-DTREV, " Last Internal Review
 REVDB TYPE KNKK-REVDB, " Last External Review
 SALDO TYPE RF42B-SALDO, " Balance
 DSOIN TYPE RF02L-DSOIN, " DSO
 H06SA TYPE RF035-H06SA, " Highest Balance at the end of 6 Months
 H06JA TYPE RF035-H06JA, " Year highest Balance 6 Months
 H06MO TYPE RF035-H06MO, " Month OF hihest Balance 6 Months
 H12SA TYPE RF035-H12SA, " Highest Balance at the end of 12 Months
 H12JA TYPE RF035-H12JA, " Year highest Balance 12 Months
 H12MO TYPE RF035-H12MO, " Month OF hihest Balance 12 Months
 UMP2U TYPE RF42B-UMP2U, " Sales from the current Year
 UMP1U TYPE RF42B-UMP1U, " Sales from the Previous Year
 SFAEL TYPE RF035-SFAEL, " Total Past Due Open Item
 SFAE1 TYPE RF035-SFAE1, " Aging buckets 0-15
 SFAE2 TYPE RF035-SFAE2, " Aging buckets 16-30
 SFAE3 TYPE RF035-SFAE3, " Aging buckets 31-60
 SFAE4 TYPE RF035-SFAE4, " Aging buckets 60-90
 SFAE5 TYPE RF035-SFAE5, " Aging buckets Over 90
 END Of I_CINFO.
DATA : BEGIN OF S_CINFO ,
 KUNNR TYPE KNB1-KUNNR, " Customer
 KNKLI TYPE KNKK-KNKLI, " Customer's account number with credit limit reference
 KKBER TYPE KNKK-KKBER, " Credit Control Area
 CTLPC TYPE KNKK-CTLPC, " Risk Category
 KLIMK TYPE KNKK-KLIMK, " Credit Limit
 SBGRP TYPE KNKK-SBGRP, " Credit representative group for credit management
 ERDAT TYPE KNKK-ERDAT, " Created On
 DTREV TYPE KNKK-DTREV, " Last Internal Review
 REVDB TYPE KNKK-REVDB, " Last External Review
 SALDO TYPE RF42B-SALDO, " Balance
 DSOIN TYPE RF02L-DSOIN, " DSO
 H06SA TYPE RF035-H06SA, " Highest Balance at the end of 6 Months
 H06JA TYPE RF035-H06JA, " Year highest Balance 6 Months
 H06MO TYPE RF035-H06MO, " Month OF hihest Balance 6 Months
 H12SA TYPE RF035-H12SA, " Highest Balance at the end of 12 Months
 H12JA TYPE RF035-H12JA, " Year highest Balance 12 Months
 H12MO TYPE RF035-H12MO, " Month OF hihest Balance 12 Months
 UMP2U TYPE RF42B-UMP2U, " Sales from the current Year
 UMP1U TYPE RF42B-UMP1U, " Sales from the Previous Year
 SFAEL TYPE RF035-SFAEL, " Total Past Due Open Item
 SFAE1 TYPE RF035-SFAE1, " Aging buckets 0-15
 SFAE2 TYPE RF035-SFAE2, " Aging buckets 16-30
 SFAE3 TYPE RF035-SFAE3, " Aging buckets 31-60
 SFAE4 TYPE RF035-SFAE4, " Aging buckets 60-90
 SFAE5 TYPE RF035-SFAE5, " Aging buckets Over 90
 END Of s_cinfo.
*Internal table to hold month-wise balance.
DATA: BEGIN OF SALTAB OCCURS 12,
 LNUMM(2) TYPE N, " Month
 SALDO LIKE RF42B-SALDO, " Balance
 END OF SALTAB.
*Internal table used for computing the Balance fields
DATA: BEGIN OF SALDO,
 UML01 LIKE KNC1-UM01S,
 UML02 LIKE KNC1-UM01S,
 UML03 LIKE KNC1-UM01S,
 UML04 LIKE KNC1-UM01S,
 UML05 LIKE KNC1-UM01S,
 UML06 LIKE KNC1-UM01S,
 UML07 LIKE KNC1-UM01S,
 UML08 LIKE KNC1-UM01S,
 UML09 LIKE KNC1-UM01S,
 UML10 LIKE KNC1-UM01S,
 UML11 LIKE KNC1-UM01S,
 UML12 LIKE KNC1-UM01S,
 END OF SALDO.
Structure to hold Bal fields ------ -------
DATA: BEGIN OF SKNKK,
 KUNNR LIKE KNA1-KUNNR, " Customer Number 1: Debitor
 KONTO LIKE KNKK-KUNNR,
 SFAE1 LIKE RF035-SFAE1, " Aging buckets 0-15
 SFAE2 LIKE RF035-SFAE2, " Aging buckets 16-30
 SFAE3 LIKE RF035-SFAE3, " Aging buckets 30-60
 SFAE4 LIKE RF035-SFAE4, " Aging buckets 60-90
 SFAE5 LIKE RF035-SFAE5, " Aging buckets Over 90
 SFAEL LIKE RF035-SFAEL, " Total Due of Items
 UML01 LIKE KNC1-UM01S,
 UML02 LIKE KNC1-UM01S,
 UML03 LIKE KNC1-UM01S,
 UML04 LIKE KNC1-UM01S,
 UML05 LIKE KNC1-UM01S,
 UML06 LIKE KNC1-UM01S,
 UML07 LIKE KNC1-UM01S,
 UML08 LIKE KNC1-UM01S,
 UML09 LIKE KNC1-UM01S,
 UML10 LIKE KNC1-UM01S,
 UML11 LIKE KNC1-UM01S,
 UML12 LIKE KNC1-UM01S,
 UMP1U LIKE RF42B-UMP1U, " Sales from the Previous Year
 UMP2U LIKE RF42B-UMP2U, " Sales from the current Year
 SALDO LIKE RF42B-SALDO, " Balance
 END OF SKNKK.
DATA : BEGIN OF ICUST1 OCCURS 0,
 KUNNR TYPE KNA1-KUNNR, "For Customer Filter.
 END OF ICUST1.
**Internal table to hold fiscal varriants
DATA: BEGIN OF LT_PERIODS OCCURS 12,
 PERIOD LIKE BSID-MONAT,
 GJAHR LIKE KNC1-GJAHR,
 END OF LT_PERIODS.
**Constants
constants : BUKRS1 TYPE KNB1-BUKRS VALUE '1000',
 BUKRS2 TYPE KNB1-BUKRS VALUE '1031',
 Recs Type i value '200',
 B_count type i value '2'.
 INITIALIZATION
INITIALIZATION.
IF RASID IS INITIAL.
 SELECT * FROM TRAS.
 EXIT.
 ENDSELECT.
 IF SY-SUBRC = 0.
 RASID = TRAS-RASID.
 ENDIF.
ENDIF.
SELECTION-SCREEN
parameters : p_path type rlgrap-filename default 'C:\Documents and Settings\C890971\Desktop\Credit_history.XLS'.
Start of selection processing
START-OF-SELECTION.
**Get Customers for Co. Code 1000 & 1031.
PERFORM GET_CUST.
Get / Compute Credit Information data for Company Codes 1000 & 1031.
PERFORM GET_CREDIT_DATA.
End of selection processing
*END-OF-SELECTION.
Listing Credit History Data
PERFORM DOWNLOAD_CREDIT_DATA.
S U B R O U T I N E S
*& Form GET_CUST
 text
--> p1 text
<-- p2 text
FORM GET_CUST .
Get US only Customers.
Refresh icust.
Select kunnr from kna1 appending table icust
 where Land1 = land.
**Delete duplicate records
Delete Adjacent duplicates from icust comparing kunnr.
if icust[] is not initial.
 Limit the selection some more to Co. Code 1000 & 1031
As join will cost overhead as compared.
Select kunnr from knb1 into table icust1
 for all entries in icust
 where kunnr = icust-kunnr
 and bukrs = bukrs1
 OR bukrs = bukrs2.
**Delete duplicate records
Delete Adjacent duplicates from icust1 comparing kunnr.
 endif.
**Free memory.
Free icust.
Credit Control Area
select * from T001CM into table TCMTAB
 where bukrs = bukrs1 OR
 bukrs = bukrs2.
ENDFORM. " GET_CUST
*& Form GET_CREDIT_DATA
 text
--> p1 text
<-- p2 text
FORM GET_CREDIT_DATA .
DATA : L_TEXT(60) TYPE C ,
 Ltext1(50) type C value 'Computing Credit-History Data For',
 Ltext2(10) type C value 'Customers',
 L_PCT type i value '10',
 L_recs type i,
 l_batch_recs type i,
 l_s_rec type i value 1,
 l_recs1(7) type N.
***Fetch data from KNKK table
PERFORM GET_KNKK_DATA .
***Computing Crredit Fields
**Number of Customers For whom Deatils needed.
Describe table I_CINFO lines l_recs.
l_recs1 = l_recs.
Concatenate Ltext1 l_recs1 Ltext2 into l_text separated by ' '.
PERFORM GET_PGRESS_INDICATOR USING l_text l_pct.
***If records are more than 200000, should be processed batch-wise
If l_recs > recs.
 l_batch_recs = abs( l_recs / b_count ).
 Do b_count times.
 loop at i_cinfo INTO S_CINFO from l_S_REC to l_batch_recs.
**Remember the row
 sytabix = sy-tabix.
**Compute DSO
 PERFORM GET_DSO_FIELD .
Compute rest credit history data.
 PERFORM COMPUTE_SFIELDS.
 endloop.
 l_S_REC = l_S_REC + l_batch_recs.
 l_batch_recs = l_batch_recs + l_batch_recs.
 IF l_batch_recs ge l_recs.
 l_batch_recs = l_recs.
 eNDIF.
Commit up to here to release the DB locks.
 Commit work.
 enddo.
else.
 loop at i_cinfo INTO S_CINFO.
**Remember the row
 sytabix = sy-tabix.
**Compute DSO
 PERFORM GET_DSO_FIELD .
Compute rest credit history data.
 PERFORM COMPUTE_SFIELDS.
 endloop.
Endif.
ENDFORM. " GET_CREDIT_DATA
*& Form GET_KNKK_DATA
 text
 -->P_ICUST_KUNNR text
FORM GET_KNKK_DATA .
if icust1[] is not initial.
SELECT KUNNR KNKLI KKBER CTLPC KLIMK
 SBGRP ERDAT DTREV REVDB
 from KNKK into corresponding fields of table I_Cinfo
 for all entries in icust1
 where kunnr = icust1-kunnr.
Delete Adjacent duplicates from i_cinfo comparing kunnr.
endif.
**Free Memory for internal table icust1.
Free icust1.
ENDFORM. " GET_KNKK_DATA
**& Form GET_DSO_FIELD
 text
--> p1 text
<-- p2 text
FORM GET_DSO_FIELD .
***Determine DSO Parameter
PERFORM DSO_PARAMETER.
***Compute DSO
CALL FUNCTION 'CUSTOMER_DSO_CALCULATION'
 EXPORTING
 I_KKBER = s_cinfo-kkber
 I_KUNNR = s_cinfo-kunnr
 I_ANZBUPER = T000CM-DSOPP
 I_XCHILDS = T000CM-DSOCH
 I_ACTBALANCE = T000CM-DSOAB
 IMPORTING
 E_DSOIN = RF02L-DSOIN
 EXCEPTIONS
 ERROR_MESSAGE = 1.
ENDFORM. " GET_DSO_FIELD
*& Form DSO_PARAMETER
 text
--> p1 text
<-- p2 text
FORM DSO_PARAMETER.
IF T000CM-DSOPP IS INITIAL.
 SELECT SINGLE * FROM T000CM.
 IF SY-SUBRC EQ 0.
 IF T000CM-DSOPP IS INITIAL.
 T000CM-DSOPP = '003'.
 ENDIF.
 ELSE.
 T000CM-DSOPP = '003'.
 T000CM-DSOCH = ' '.
 T000CM-DSOAB = 'X'.
 ENDIF.
ENDIF.
ENDFORM. " DSO_PARAMETER
--> p1 text
<-- p2 text
FORM PERIODE_ERMITTELN_EXC USING
 P03_BUDAT LIKE SYST-DATUM
 P03_GJAHR LIKE KNC1-GJAHR
 P03_MONAT LIKE MONAT.
CALL FUNCTION 'FI_PERIOD_DETERMINE'
 EXPORTING
 I_BUDAT = P03_BUDAT
 I_PERIV = T001-PERIV
 I_BUKRS = T001-BUKRS
 I_GJAHR = P03_GJAHR
 I_MONAT = P03_MONAT
 IMPORTING
 E_GJAHR = P03_GJAHR
 E_MONAT = P03_MONAT
 EXCEPTIONS
 ERROR_MESSAGE = 1.
ENDFORM. "PERIODE_ERMITTELN_EXC
*& Form COMPUTE_SFIELDS
 text
--> p1 text
<-- p2 text
FORM COMPUTE_SFIELDS .
**Compute Balance
PERFORM GET_SFIELDS .
S_CINFO-DSOIN = RF02L-DSOIN.
S_CINFO-SALDO = RF035-SALDO.
S_CINFO-H06SA = RF035-H06SA.
S_CINFO-H06JA = RF035-H06JA.
S_CINFO-H06MO = RF035-H06MO.
S_CINFO-H12SA = RF035-H12SA.
S_CINFO-H12JA = RF035-H12JA.
S_CINFO-H12MO = RF035-H12MO.
S_CINFO-UMP2U = RF42B-UMP2U.
S_CINFO-UMP1U = RF42B-UMP1U.
S_CINFO-SFAEL = RF035-SFAEL.
S_CINFO-SFAE1 = RF035-SFAE1.
S_CINFO-SFAE2 = RF035-SFAE2.
S_CINFO-SFAE3 = RF035-SFAE3.
S_CINFO-SFAE4 = RF035-SFAE4.
S_CINFO-SFAE5 = RF035-SFAE5.
modify..
MODIFY I_CINFO FROM S_CINFO INDEX sytabix.
CLEAR: S_CINFO,RF035,RF02L, RF42B.
ENDFORM. " COMPUTE_SFIELDS
 text
 -->P_C_INFO_KUNNR text
FORM GET_CUST_BAL_INFO.
LOOP AT TCMTAB.
 CALL FUNCTION 'FI_COMPANY_CODE_DATA'
 EXPORTING
 I_BUKRS = TCMTAB-BUKRS
 IMPORTING
 E_T001 = T001
 EXCEPTIONS
 ERROR_MESSAGE = 1.
 IF SY-SUBRC = 0.
 MOVE-CORRESPONDING T001 TO BUKTAB.
 BUKTAB-KKBER = TCMTAB-KKBER.
 COLLECT BUKTAB.
 ENDIF.
ENDLOOP.
LOOP AT BUKTAB WHERE PERIV NE SPACE.
 GJATAB-PERIV = BUKTAB-PERIV.
 COLLECT GJATAB.
ENDLOOP.
CLEAR: MONAT.
LOOP AT GJATAB.
 T001-PERIV = GJATAB-PERIV.
 CLEAR: GJAHR, MONAT.
 PERFORM PERIODE_ERMITTELN_EXC USING SY-DATLO GJAHR MONAT.
 CHECK SY-SUBRC = 0.
 GJATAB-GJAHR = GJAHR.
 GJATAB-MONAT = MONAT.
 SELECT SINGLE * FROM T009 WHERE PERIV = GJATAB-PERIV.
 IF SY-SUBRC = 0.
 GJATAB-ANZBP = T009-ANZBP.
 ENDIF.
 MODIFY GJATAB.
ENDLOOP.
LOOP AT BUKTAB.
 CHECK NOT ( BUKTAB-PERIV IS INITIAL ).
 READ TABLE GJATAB WITH KEY BUKTAB-PERIV.
 CHECK SY-SUBRC = 0
 AND NOT ( GJATAB-GJAHR IS INITIAL ).
 CALL FUNCTION 'CUSTOMER_BALANCE'
 EXPORTING
 KUNNR = S_cinfo-kunnr
 BUKRS = BUKTAB-BUKRS
 GJAHR = GJATAB-GJAHR
 MONAT = GJATAB-MONAT
 PERIV = GJATAB-PERIV
 ANZBP = GJATAB-ANZBP
 XH6MON = 'X'
 XH12MON = 'X'
 IMPORTING
 UMP2U = RF42B-UMP2U
 VMP2U = RF42B-UMP1U
 SALDO = RF035-SALDO
 UML01 = SALDO-UML01
 UML02 = SALDO-UML02
 UML03 = SALDO-UML03
 UML04 = SALDO-UML04
 UML05 = SALDO-UML05
 UML06 = SALDO-UML06
 UML07 = SALDO-UML07
 UML08 = SALDO-UML08
 UML09 = SALDO-UML09
 UML10 = SALDO-UML10
 UML11 = SALDO-UML11
 UML12 = SALDO-UML12
 EXCEPTIONS
 NO_BALANCE = 4.
 IF SY-SUBRC = 0.
 SKNKK-UMP1U = SKNKK-UMP1U + RF42B-UMP1U.
 SKNKK-UMP2U = SKNKK-UMP2U + RF42B-UMP2U.
 SKNKK-SALDO = SKNKK-SALDO + RF035-SALDO.
 SKNKK-UML01 = SKNKK-UML01 + SALDO-UML01.
 SKNKK-UML02 = SKNKK-UML02 + SALDO-UML02.
 SKNKK-UML03 = SKNKK-UML03 + SALDO-UML03.
 SKNKK-UML04 = SKNKK-UML04 + SALDO-UML04.
 SKNKK-UML05 = SKNKK-UML05 + SALDO-UML05.
 SKNKK-UML06 = SKNKK-UML06 + SALDO-UML06.
 SKNKK-UML07 = SKNKK-UML07 + SALDO-UML07.
 SKNKK-UML08 = SKNKK-UML08 + SALDO-UML08.
 SKNKK-UML09 = SKNKK-UML09 + SALDO-UML09.
 SKNKK-UML10 = SKNKK-UML10 + SALDO-UML10.
 SKNKK-UML11 = SKNKK-UML11 + SALDO-UML11.
 SKNKK-UML12 = SKNKK-UML12 + SALDO-UML12.
 ENDIF.
ENDLOOP.
ENDFORM. "
*& Form GET_SFIELDS
 text
--> p1 text
<-- p2 text
FORM GET_SFIELDS .
sknkk-kunnr = S_CINFO-KUNNR.
**Clear target to store computed values
CLEAR: RF035.
**Compute Balance fields
PERFORM GET_CUST_BAL_INFO.
REFRESH: SALTAB.
SALTAB-LNUMM = '01'. SALTAB-SALDO = SKNKK-UML01. APPEND SALTAB.
SALTAB-LNUMM = '02'. SALTAB-SALDO = SKNKK-UML02. APPEND SALTAB.
SALTAB-LNUMM = '03'. SALTAB-SALDO = SKNKK-UML03. APPEND SALTAB.
SALTAB-LNUMM = '04'. SALTAB-SALDO = SKNKK-UML04. APPEND SALTAB.
SALTAB-LNUMM = '05'. SALTAB-SALDO = SKNKK-UML05. APPEND SALTAB.
SALTAB-LNUMM = '06'. SALTAB-SALDO = SKNKK-UML06. APPEND SALTAB.
SALTAB-LNUMM = '07'. SALTAB-SALDO = SKNKK-UML07. APPEND SALTAB.
SALTAB-LNUMM = '08'. SALTAB-SALDO = SKNKK-UML08. APPEND SALTAB.
SALTAB-LNUMM = '09'. SALTAB-SALDO = SKNKK-UML09. APPEND SALTAB.
SALTAB-LNUMM = '10'. SALTAB-SALDO = SKNKK-UML10. APPEND SALTAB.
SALTAB-LNUMM = '11'. SALTAB-SALDO = SKNKK-UML11. APPEND SALTAB.
SALTAB-LNUMM = '12'. SALTAB-SALDO = SKNKK-UML12. APPEND SALTAB.
READ TABLE SALTAB INDEX 1.
RF035-H06SA = SALTAB-SALDO.
RF035-H06MO = SALTAB-LNUMM.
RF035-H12SA = SALTAB-SALDO.
RF035-H12MO = SALTAB-LNUMM.
------ SALTAB ---------------------------------------------
LOOP AT SALTAB.
 IF SALTAB-SALDO > RF035-H06SA
 AND SY-TABIX < 7.
 RF035-H06SA = SALTAB-SALDO.
 RF035-H06MO = SALTAB-LNUMM.
 ENDIF.
 IF SALTAB-SALDO > RF035-H12SA
 AND SY-TABIX < 13.
 RF035-H12SA = SALTAB-SALDO.
 RF035-H12MO = SALTAB-LNUMM.
 ENDIF.
ENDLOOP.
------ Period--------------------
REFRESH LT_PERIODS.
CLEAR LD_COUNTER.
READ TABLE BUKTAB INDEX 1.
IF SY-SUBRC = 0.
 READ TABLE GJATAB WITH KEY BUKTAB-PERIV.
 DO GJATAB-MONAT TIMES
 VARYING LD_PERIOD FROM LD_PERIODS(2) NEXT LD_PERIODS+2(2)
 RANGE LD_PERIODS.
 LT_PERIODS-GJAHR = GJATAB-GJAHR.
 LT_PERIODS-PERIOD = LD_PERIOD.
 LD_COUNTER = LD_COUNTER + 1.
 APPEND LT_PERIODS.
 ENDDO.
 IF LD_COUNTER LT 12.
 LD_GJAHR = GJATAB-GJAHR - 1.
 CLEAR T009Y.
 SELECT SINGLE * FROM T009Y WHERE PERIV = GJATAB-PERIV
 AND GJAHR = LD_GJAHR.
 DO GJATAB-ANZBP TIMES
 VARYING LD_PERIOD FROM LD_PERIODS(2) NEXT LD_PERIODS+2(2)
 RANGE LD_PERIODS.
 IF T009Y-ANZBP > 0.
 CHECK SY-INDEX <= T009Y-ANZBP.
 ENDIF.
 LD_COUNTER = LD_COUNTER + 1.
 LT_PERIODS-GJAHR = LD_GJAHR.
 LT_PERIODS-PERIOD = LD_PERIOD.
 APPEND LT_PERIODS.
 ENDDO.
 ENDIF.
 IF LD_COUNTER LT 12.
 LD_GJAHR = LD_GJAHR - 1.
 DO GJATAB-ANZBP TIMES
 VARYING LD_PERIOD FROM LD_PERIODS(2) NEXT LD_PERIODS+2(2)
 RANGE LD_PERIODS.
 LD_COUNTER = LD_COUNTER + 1.
 LT_PERIODS-GJAHR = LD_GJAHR.
 LT_PERIODS-PERIOD = LD_PERIOD.
 APPEND LT_PERIODS.
 ENDDO.
 ENDIF.
 SORT LT_PERIODS BY GJAHR ASCENDING PERIOD ASCENDING.
 LD_COUNTER = LD_COUNTER - 12.
 DO LD_COUNTER TIMES.
 DELETE LT_PERIODS INDEX 1.
 ENDDO.
 SORT LT_PERIODS BY GJAHR DESCENDING PERIOD DESCENDING.
 READ TABLE LT_PERIODS INDEX RF035-H06MO.
 RF035-H06MO = LT_PERIODS-PERIOD.
 RF035-H06JA = LT_PERIODS-GJAHR.
 READ TABLE LT_PERIODS INDEX RF035-H12MO.
 RF035-H12MO = LT_PERIODS-PERIOD.
 RF035-H12JA = LT_PERIODS-GJAHR.
ENDIF.
**Compute Due Dates fields
PERFORM GET_AGING_BUCKETS .
RF035-SFAE1 = SKNKK-SFAE1.
RF035-SFAE2 = SKNKK-SFAE2.
RF035-SFAE3 = SKNKK-SFAE3.
RF035-SFAE4 = SKNKK-SFAE4 .
RF035-SFAE5 = SKNKK-SFAE5.
ENDLOOP.
ENDFORM. " GET_BALANCE_SFIELDS
*& Form GET_AGING_BUCKETS
 text
--> p1 text
<-- p2 text
FORM GET_AGING_BUCKETS .
DATA: BEGIN OF LT_BUKRS OCCURS 0,
 BUKRS LIKE T001-BUKRS,
 END OF LT_BUKRS.
DATA: BEGIN OF LT_BUKTAB OCCURS 0,
 BUKRS LIKE T001-BUKRS,
 WAERS LIKE T001-WAERS,
 KKBER LIKE T014-KKBER,
 END OF LT_BUKTAB.
DATA: LD_LINES LIKE SY-TABIX.
*...performance optimization: for more than one company codes check....*
*...if balances exist and avoid selection of open items, if they don't.*
*...exist..............................................................*
REFRESH LT_BUKRS.
REFRESH LT_BUKTAB.
DESCRIBE TABLE BUKTAB LINES LD_LINES.
IF LD_LINES GT 1.
 SELECT DISTINCT BUKRS APPENDING CORRESPONDING FIELDS
 OF TABLE LT_BUKRS
 FROM KNC1 FOR ALL ENTRIES IN BUKTAB
 WHERE BUKRS = BUKTAB-BUKRS AND
 KUNNR = Sknkk-KUNNR.
 SELECT DISTINCT BUKRS APPENDING CORRESPONDING FIELDS
 OF TABLE LT_BUKRS
 FROM KNC3 FOR ALL ENTRIES IN BUKTAB
 WHERE BUKRS = BUKTAB-BUKRS AND
 KUNNR = Sknkk-KUNNR.
 SORT LT_BUKRS.
 DELETE ADJACENT DUPLICATES FROM LT_BUKRS.
 LOOP AT LT_BUKRS.
 LOOP AT BUKTAB WHERE BUKRS = LT_BUKRS-BUKRS.
 MOVE-CORRESPONDING BUKTAB TO LT_BUKTAB.
 APPEND LT_BUKTAB.
 ENDLOOP.
 ENDLOOP.
ELSE.
 READ TABLE BUKTAB INDEX 1.
 MOVE-CORRESPONDING BUKTAB TO LT_BUKTAB.
 APPEND LT_BUKTAB.
ENDIF.
*...process company codes for customer given by interface..........*
LOOP AT LT_BUKTAB WHERE KKBER = s_cinfo-KKBER.
 CALL FUNCTION 'CUSTOMER_DUE_DATE_ANALYSIS'
 EXPORTING BUKRS = LT_BUKTAB-BUKRS
 KKBER = ' '
 KKBER = s_cinfo-KKBER
 KUNNR = Sknkk-KUNNR
 RASID = RASID
 IMPORTING SFAE1 = RF035-SFAE1
 SFAE2 = RF035-SFAE2
 SFAE3 = RF035-SFAE3
 SFAE4 = RF035-SFAE4
 SFAE5 = RF035-SFAE5
 SFAEL = RF035-SFAEL
 EXCEPTIONS NO_OPEN_ITEMS = 4.
 IF SY-SUBRC = 0.
*-- RF035 -
 SKNKK-SFAE1 = SKNKK-SFAE1 + RF035-SFAE1.
 SKNKK-SFAE2 = SKNKK-SFAE2 + RF035-SFAE2.
 SKNKK-SFAE3 = SKNKK-SFAE3 + RF035-SFAE3.
 SKNKK-SFAE4 = SKNKK-SFAE4 + RF035-SFAE4.
 SKNKK-SFAE5 = SKNKK-SFAE5 + RF035-SFAE5.
 SKNKK-SFAE5 = SKNKK-SFAE5 + RF035-SFAE5.
 SKNKK-SFAEL = SKNKK-SFAEL + RF035-SFAEL.
 ENDIF.
ENDLOOP.
ENDFORM. " GET_AGING_BUCKETS
*& Form header
This Subroutine gets data for displaying title *
There are no interface parameters to be passed to this subroutine. *
FORM header .
wa_final-string = text-000. APPEND wa_final TO i_final.
wa_final-string = text-001. APPEND wa_final TO i_final.
wa_final-string = text-002. APPEND wa_final TO i_final.
wa_final-string = text-003. APPEND wa_final TO i_final.
wa_final-string = text-004. APPEND wa_final TO i_final.
wa_final-string = text-005. APPEND wa_final TO i_final.
wa_final-string = text-006. APPEND wa_final TO i_final.
wa_final-string = text-007. APPEND wa_final TO i_final.
wa_final-string = text-008. APPEND wa_final TO i_final.
wa_final-string = text-009. APPEND wa_final TO i_final.
wa_final-string = text-010. APPEND wa_final TO i_final.
wa_final-string = text-011. APPEND wa_final TO i_final.
wa_final-string = text-012. APPEND wa_final TO i_final.
wa_final-string = text-013. APPEND wa_final TO i_final.
wa_final-string = text-014. APPEND wa_final TO i_final.
wa_final-string = text-015. APPEND wa_final TO i_final.
wa_final-string = text-016. APPEND wa_final TO i_final.
wa_final-string = text-017. APPEND wa_final TO i_final.
wa_final-string = text-018. APPEND wa_final TO i_final.
wa_final-string = text-019. APPEND wa_final TO i_final.
wa_final-string = text-020. APPEND wa_final TO i_final.
wa_final-string = text-021. APPEND wa_final TO i_final.
wa_final-string = text-022. APPEND wa_final TO i_final.
wa_final-string = text-023. APPEND wa_final TO i_final.
wa_final-string = text-024. APPEND wa_final TO i_final.
ENDFORM. " header
*& Form DOWNLOADCREDITDATA
 text
 -->P_P_PATH text
FORM DOWNLOADCREDITDATA USING P_PATH.
DATA:
 lw_file2 TYPE string . " File Path
lw_file2 = p_PATH.
CALL FUNCTION 'GUI_DOWNLOAD'
 EXPORTING
BIN_FILESIZE = BIN_FILESIZE
 filename = lw_file2
 filetype = 'DBF'
APPEND = ' '
 write_field_separator = ' '
HEADER = '00'
TRUNC_TRAILING_BLANKS = 'X'
WRITE_LF = 'X'
 COL_SELECT = 'X'
COL_SELECT_MASK = ' '
DAT_MODE = 'X'
CONFIRM_OVERWRITE = ' '
NO_AUTH_CHECK = ' '
CODEPAGE = ' '
IGNORE_CERR = ABAP_TRUE
REPLACEMENT = '#'
WRITE_BOM = ' '
TRUNC_TRAILING_BLANKS_EOL = 'X'
WK1_N_FORMAT = '0'
WK1_N_SIZE = ' '
WK1_T_FORMAT = ' '
WK1_T_SIZE = ' '
IMPORTING
FILELENGTH = FILELENGTH
 TABLES
 data_tab = I_CINFO
 fieldnames = i_final
 EXCEPTIONS
 file_write_error = 1
 no_batch = 2
 gui_refuse_filetransfer = 3
 invalid_type = 4
 no_authority = 5
 unknown_error = 6
 header_not_allowed = 7
 separator_not_allowed = 8
 filesize_not_allowed = 9
 header_too_long = 10
 dp_error_create = 11
 dp_error_send = 12
 dp_error_write = 13
 unknown_dp_error = 14
 access_denied = 15
 dp_out_of_memory = 16
 disk_full = 17
 dp_timeout = 18
 file_not_found = 19
 dataprovider_exception = 20
 control_flush_error = 21
IF sy-subrc <> 0.
Messege
ENDIF. " IF sy-subrc EQ 0
ENDFORM. " DOWNLOADCREDITDATA
*& Form DOWNLOAD_CREDIT_DATA
 text
--> p1 text
<-- p2 text
FORM DOWNLOAD_CREDIT_DATA .
PERFORM HEADER.
PERFORM DOWNLOADCREDITDATA USING P_PATH.
ENDFORM. " DOWNLOAD_CREDIT_DATA
*& Form GET_PGRESS_INDICATOR
 text
 -->P_L_TEXT text
 -->P_L_PCT text
FORM GET_PGRESS_INDICATOR USING L_TEXT
 L_PCT.
CALL FUNCTION 'SAPGUI_PROGRESS_INDICATOR'
 EXPORTING
 PERCENTAGE = l_pct
 TEXT = l_TEXT.
ENDFORM. " GET_PGRESS_INDICATOR

If you are just Downloading to a Flat file then why dont you have logic in place for the program to dump the data read into the file to that point depending on any criteria like accounts or customer then clear the internal table and run it in the back ground.
try to use cursor to read the records from the table which will make it a bit more efficient than plain select stement.

Downloding Internal Table to Excel Issue

Hi guys,
I want to know how can i download an internal table to excel, in which i have only one field declare as string. The values in the string are delimiter by # and i want to separated it in the excel in columns.
Ej.
DATA: BEGIN OF t_asc_file OCCURS 100,
        string TYPE string,
      END OF t_asc_file,
      it_asc_file LIKE t_asc_file OCCURS 0,
      wa_asc_file like line of it_asc_file.
CONCATENATE wa_asc_file-string '#Importe#Mon.Soc.PA#Base Emisora %' INTO wa_asc_file-string.
APPEND wa_asc_file TO it_asc_file.
CALL METHOD cl_gui_frontend_services=>gui_download
    EXPORTING
*      BIN_FILESIZE              = BIN_FILESIZE
      filename                = fullpath
      filetype                = 'ASC'
*      APPEND                    = APPEND
      WRITE_FIELD_SEPARATOR = 'X' "CL_ABAP_CHAR_UTILITIES=>HORIZONTAL_TAB
*      HEADER                    = HEADER
*      TRUNC_TRAILING_BLANKS     = TRUNC_TRAILING_BLANKS
*      WRITE_LF                  = WRITE_LF
*      COL_SELECT                = COL_SELECT
*      COL_SELECT_MASK           = COL_SELECT_MASK
*      DAT_MODE                  = DAT_MODE
*      CONFIRM_OVERWRITE         = CONFIRM_OVERWRITE
*      NO_AUTH_CHECK             = NO_AUTH_CHECK
*      CODEPAGE                  = '1160' "CODEPAGE
*      IGNORE_CERR               = IGNORE_CERR
*      REPLACEMENT               = '#'
*      WRITE_BOM                 = WRITE_BOM
*      TRUNC_TRAILING_BLANKS_EOL = TRUNC_TRAILING_BLANKS_EOL
    IMPORTING
      filelength              = wa_filelength
    CHANGING
      data_tab                = it_asc_file
    EXCEPTIONS
      file_write_error        = 1
      no_batch                = 2
      gui_refuse_filetransfer = 3
      invalid_type            = 4
      no_authority            = 5
      unknown_error           = 6
      header_not_allowed      = 7
      separator_not_allowed   = 8
      filesize_not_allowed    = 9
      header_too_long         = 10
      dp_error_create         = 11
      dp_error_send           = 12
      dp_error_write          = 13
      unknown_dp_error        = 14
      access_denied           = 15
      dp_out_of_memory        = 16
      disk_full               = 17
      dp_timeout              = 18
      file_not_found          = 19
      dataprovider_exception = 20
      control_flush_error     = 21
      not_supported_by_gui    = 22
      error_no_gui            = 23
      OTHERS                  = 24.
This code only downloads all the information into the first column of excel.
Thanks in advance.
Eric

Hi Guys,
I know that the GUI_DOWNLOAD automatically creates the fields in separated columns when you have the internal table already separated by the fields you need.
In this case the fields that i need to download will vary from time to time, so i thought it was better to declare my internal table with one field as string. I debug the download option that has SAP in transaction KEU5, and it does work. This transaction has an internal table with one field declare as string, and each field is separated by "#".
I don't see the reason why it works in the standard and not for me, but in order to save time, i will create generic fields to my internal table.
Regards,
Eric
PD. If somebody knows how to resolve this problem would be highly apreciated.

Internal Table ! Accessing Issue!

Hello Guys!
 Internal table
 Sorted, Hashed, Standard
For accesing itab uses,
 Standard---> uses Linear Search
 Sorted ---> Binary Search
 Hashed-----> Hash Algorithm
 Can u pls tell me what is linear search, binary search, hash algorithm?
 And also,
 Why we mostly go for standard table?
PLs give ur suggestions,
Thanks for your answers
<REMOVED BY MODERATOR>
 Thanks
 Rahul.
Message was edited by:
 Alvaro Tejada Galindo

TABKIND - Internal Table Types
Alternatives:
1. STANDARD TABLE
2. SORTED TABLE
3. HASHED TABLE
4. INDEX TABLE
5. ANY TABLE
Effect
The table type - set in the DATA, TYPES, orCREATE DATA statement, specifies how the system accesses entries in the internal table in generic key operations.
(READ TABLE itab, DELETE TABLE itab, INSERT TABLE itab, MODIFY TABLE itab, COLLECT itab). As a general rule, the runtime required for key operations depends on the total length of the key.
The various table types have the following hierarchy:
 ANY TABLE
 |
 | |
 INDEX TABLE HASHED TABLE
 |
 | |
 STANDARD TABLE SORTED TABLE
Alternative 1
STANDARD TABLE
Effect
Defines the table as a standard table. Key access to a standard table uses a linear search. This means that the timne required for a search is in linear relation to the number of table entries.
You should use index operations to access standard tables.
For the sake of compatibility, you can use TABLE as a synonym of STANDARD TABLE.
Alternative 2
SORTED TABLE
Effect
Defines the table as one that is always saved correctly sorted. Key access to a sorted table uses a binary key. If the key is not unique, the system takes the entry with the lowest index. The runtime required for key access is logarithmically related to the number of table entries.
You can also access sorted tables by index operations. When you insert using an index, the system checks to ensure that the sort sequence has been correctly maintained. For this reason, it takes longer than inserting entries in a standard table. As a rule, you should only access sorted tables using their key.
Alternative 3
HASHED TABLE
Effect
Defines the table as one that is managed with an internal hash procedure. You can imagine a hashed table as a set, whose elements you can address using their unique key. Unlike standard and sorted tables, you cannot access hash tables using an index. All entries in the table must have a unique key. Access time using the key is constant, regardless of the number of table entries.
You can only access a hashed table using the generic key operations or other generic operations ( SORT, LOOP, and so on). Explicit or implicit index operations (such as LOOP ... FROM oe INSERT itab within a LOOP) are not allowed.
Alternative 4
INDEX TABLE
Effect
Standard and sorted tables belong to the generic class index tables. An index table is one that you can access using an index. You can currently only use the table type INDEX TABLE to specify the type of generic parameters in a FORM or a FUNCTION. Hashed tables are not index tables, and cannot therefore be passed to parameters defined as INDEX TABLE.
Alternative 5
ANY TABLE
Effect
Like INDEX TABLE, you use ANY TABLE to specify the type of any generic table parameter. The set of permitted operations for a table with type ANY TABLE consists of the intersection of all permitted operations for STANDARD, SORTED and HASHED TABLEs, and so is identical to the set of operations permitted for hashed tables.
Note in particular that you cannot use index access for tables with this type.

Rows missing in ALV output compared to internal table (was "ALV issue")

Hi guys,
I am getting an ALV for 70 rows whereas the internal table I am passing has 120 rows.
Any idea why I could be facing this issue.Has anyone ever faced something similar?
Thanks,
Chirantan
Moderator message: please use more descriptive subject lines for your posts.
Edited by: Thomas Zloch on May 9, 2011 9:51 AM

BY default, maximum number of coulmns displayed in ALV is 90.
You can increase it by setting the parameter NO_OUT as initial for the remaining fields in their field catalog.
Please check below sample code:
"Build Field catalog using structure of QALS
CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE'
    EXPORTING
      i_program_name         = sy-repid
      i_structure_name       = 'QALS'
    CHANGING
      ct_fieldcat            = g_t_fcat   " Internal table contains more than 90 fields
    EXCEPTIONS
      inconsistent_interface = 1
      program_error          = 2
      OTHERS                 = 3.
"Only first 90 fields will be displayed in output. So, set NO_OUT as initial for remaining fields.
LOOP AT g_t_fcat INTO g_r_fcat WHERE no_out = 'X'.
g_r_fcat-no_out = ''.   " Set NO_OUT as initial
MODIFY g_t_fcat FROM g_r_fcat INDEX sy-tabix TRANSPORTING no_out.
ENDLOOP.

Comapare internal tables which are in tree format

Hi guys,
Consider internal table
 level | material-no.|quantity
 1 | mat-1 | 10
 2 | mat-5 | 1
 3 | mat-2 | 1
 3 | mat-4 | 12
 2 | mat-12 | 11
 3 | mat-15 | 12
................................>mat1 ends here..it contains mat5 and mat 12 which in turn contain
.......................mat2 & 4 and mat 15 respectively.
 1 | mat-8 | 1
 2 | mat-6 | 3
 2 | mat-100 | 5
......................................>mat 8 ends here
 1 | mat -6 | 13
.......................................>mat 6 ends here
This data is in one internal table, here there are 3 main materials (1,8,6) which are in-turn made of other materials.
material at level 1 is made of materials at level 2
and in-turn materials at level2 are made up of materials at level3 .
Now same material can exist at different levels ...
What would be the efficient way to compare two such internal tables and comparisons are done wrt quantity but level and hierarchy at which material exits matters and
comparison shuld be done at each level .
if both materials are in same hierarchy in both tables but diff in quantity then they are unequal .
if both materials are in same hierarchy in both tables and equal in quantity then they are equal .
if that material exist in one but doesnot exist in other table in similar hierarchy then its rendered as
not found.
many thanks in advance.

Hi Anurag,
Thanks for the reply but the number of levels is not always 3(it completely depends on data) .I came up with one solution --what I have done is , created one more column HPATH in the internal table and kept hierarchy relationship ..i.e
level| material| qty | HPATH(hierarchy path)
1 | mat-1 | 10 | mat-1
2 | mat-5 | 1 | mat-1 2 mat-5
3 | mat-2 | 1 | mat-1 2 mat-5 3 mat-2
3 | mat-4 | 12 | mat-1 2 mat-5 3 mat-4
2 | mat-12 | 11 | mat-1 2 mat-12
3 | mat-15 | 12 | mat-1 2 mat-12 3 mat-15
1 | mat-8 | 1 | mat-8
2 | mat-6 | 3 | mat-8 2 mat-6
2 | mat-100 | 5 | mat-8 2 mat-100
2 and 3 are the path seperates..which indicate the level..
Thus I get key as unique for each material depending on its position in heirarchy ..
Then I looped wrt one table and read data form other table with HPATH as key and compared it .
This solved it...
The number of levels doesnot matter in this solution...
Thanks once again for replying to my post. I would be to happy to put up the code if u want..

Excel to internal table upload 'ALSM_EXCEL_TO_INTERNAL_TABLE' issue

I am using ALSM_EXCEL_TO_INTERNAL_TABLE function module to upload the excel into an internal table. In case there is a column with no data. This function module is still populating the previous row data into the internal table
Ex. if the Excel has data like the below 3 rows and 3 columns
1                   10                5.0
                     20
2                                       6.0
The internal table is posting data like this
1                  10               5.0
1                  20               5.0
2                  20               6.0
Please tell me if i am missing something to be added in the below snip of code
CALL FUNCTION 'ALSM_EXCEL_TO_INTERNAL_TABLE'
    EXPORTING
      FILENAME                = p_file
      I_BEGIN_COL             = B1
      I_BEGIN_ROW             = C1
      I_END_COL               = B2
      I_END_ROW               = C2
    TABLES
      INTERN                  = IT_upload
    EXCEPTIONS
      INCONSISTENT_PARAMETERS = 1
      UPLOAD_OLE              = 2
      OTHERS                  = 3.
IF SY-SUBRC = 0.
ENDIF.
LOOP AT IT_upload.
    CASE IT_Upload-COL.
      WHEN 1.
        IT_Excel-BILLCO = IT_Upload-VALUE.
      WHEN 2.
        IT_Excel-PONUM = IT_Upload-VALUE.
      WHEN 3.
        CLEAR v_upload.
        CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
          EXPORTING
            INPUT = IT_upload-value
          IMPORTING
            OUTPUT = v_upload.
        IT_Excel-STORENUM = v_upload.
      WHEN 4.
        IT_Excel-VINVNUM = IT_Upload-VALUE.
      WHEN 5.
        IT_Excel-LINEITNUM = IT_Upload-VALUE.
      WHEN 6.
        IT_Excel-LINEITAMT = IT_upload-VALUE.
      WHEN 7.
        IT_Excel-TAXAMT = IT_upload-VALUE.
      WHEN 8.
        IT_Excel-TOTAL = IT_upload-VALUE.
    ENDCASE.
    AT END OF ROW.
      APPEND IT_Excel.
    ENDAT.
ENDLOOP.

Hi,
Please check below link. surely it will help u.
http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=60655105
Thanks
Jitendra

Why using workarea for internal table is better in performance

Please tell me
why using workarea for internal table is better in performance

Hi Vineet ,
Why would we choose to use an internal table without a header line when it is easier to code one with a header line?
it has following reason.
1)Separate Internal Table Work Area:
The work area (staging area) defined for the internal table is not limited to use with just one internal table.
take ex-
Suppose you want two internal tables for EMPLOYEE one to contain all records and one to contain only those records where country = USA. You could create both of these internal tables without header lines and use only one work area to load data into both of them. You would append all records from the work area into the first internal table. You would conditionally append the USA records from the same work area into the second internal table.
2) Performance Issues: Using an internal table without a header line is more efficient than one with a header line
3) Nested Internal Tables: If you want to include an internal table within a structure or another internal table, you must use one without a header line.
If this one is helpful ,then rewards me
Regards
Shambhu

How to find list of internal tables while debugging

Hi Experts,
I am debugging a block of an ABAP program( User Exit ). Is there any facility to see what are the internal tables, work areas are available for that particular block? Can I see it new debugger? Because I don't know from which internal table I can take a particular value, which I need to populate in an user exit.
Thanks and regards,
Venkat.

hi,
you can find the exact answer here :
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/840ad679-0601-0010-cd8e-9989fd650822#q-6
under heading List of internal tables while debugging
regards
rahul

How to Convert internal table data into text output and send mail in ABAP

Hi All,
Good Morning.
Taking a glance at a code that converts internal table data to an Excel file in ABAP. also checked how to send this excel to mailing list as attachment.
But thought of doing it without excel.
I mean, I have an internal table which contains fields of all types (character,integer,date,time). Since it is only around 4 to 5 rows in it (output),why to convert it to excel. not required!!. Instead I want to send this output to User's mails as Normal mail body with No attachments.
Could anybody please suggest me a way as to how to send internal table data as a mail ( not as an excel or PDF etc).
as of now my findings are, it is quite complex to convert internal table data to email (Text) format. but i believe if there is some way of doing it.
Best Regards
Dileep VT

here's something I have used in the past where we send out information about failed precalculation settings (which are stored in internal table gt_fail)
notice we use gt_text as "mail body"
TRY.
* -------- create persistent send request ------------------------
 gv_send_request = cl_bcs=>create_persistent( ).
* -------- create and set document -------------------------------
* create text to be sent
 wa_line = text-001.
 APPEND wa_line TO gt_text.
 CLEAR wa_line.
 APPEND wa_line TO gt_text.
 LOOP AT gt_fail ASSIGNING <fs_fail>.
 MOVE <fs_fail>-retry_count TO gv_count.
 CONCATENATE text-002
 <fs_fail>-setting_id
 text-003
 gv_count
 INTO wa_line SEPARATED BY space.
 APPEND wa_line TO gt_text.
 CLEAR wa_line.
 ENDLOOP.
 APPEND wa_line TO gt_text.
 wa_line = text-007.
 APPEND wa_line TO gt_text.
* create actual document
 gv_document = cl_document_bcs=>create_document(
 i_type = 'RAW'
 i_text = gt_text
 i_length = '12'
 i_subject = 'Failed Precalculation Settings!' ).
* add document to send request
 CALL METHOD gv_send_request->set_document( gv_document ).
* --------- set sender -------------------------------------------
 gv_sender = cl_sapuser_bcs=>create( sy-uname ).
 CALL METHOD gv_send_request->set_sender
 EXPORTING
 i_sender = gv_sender.
* --------- add recipient (e-mail address) -----------------------
 LOOP AT s_email INTO wa_email.
 MOVE wa_email-low TO gv_email.
 gv_recipient = cl_cam_address_bcs=>create_internet_address(
 gv_email ).
 CALL METHOD gv_send_request->add_recipient
 EXPORTING
 i_recipient = gv_recipient
 i_express = 'X'.
 ENDLOOP.
* ---------- set to send immediately -----------------------------
 CALL METHOD gv_send_request->set_send_immediately( 'X' ).
* ---------- send document ---------------------------------------
 CALL METHOD gv_send_request->send(
 EXPORTING
 i_with_error_screen = 'X'
 RECEIVING
 result = gv_sent_to_all ).
 IF gv_sent_to_all = 'X'.
 WRITE text-004.
 ENDIF.
 COMMIT WORK.
* exception handling
 CATCH cx_bcs INTO gv_bcs_exception.
 WRITE: text-005.
 WRITE: text-006, gv_bcs_exception->error_type.
 EXIT.
 ENDTRY.
with the following declarations
* TABLES *
TABLES:
 adr6,
 rsr_prec_sett.
* INTERNAL TABLES & WORK AREAS *
DATA:
 gt_fail TYPE SORTED TABLE OF rsr_prec_sett
 WITH UNIQUE KEY setting_id run_date,
 gt_text TYPE bcsy_text,
 wa_fail LIKE LINE OF gt_fail,
 wa_line(90) TYPE c.
FIELD-SYMBOLS:
 <fs_fail> LIKE LINE OF gt_fail.
* VARIABLES *
DATA:
 gv_count(4) TYPE n,
 gv_send_request TYPE REF TO cl_bcs,
 gv_document TYPE REF TO cl_document_bcs,
 gv_sender TYPE REF TO cl_sapuser_bcs,
 gv_recipient TYPE REF TO if_recipient_bcs,
 gv_email TYPE adr6-smtp_addr,
 gv_bcs_exception TYPE REF TO cx_bcs,
 gv_sent_to_all TYPE os_boolean.
* SELECTION-SCREEN *
SELECT-OPTIONS:
 s_email FOR adr6-smtp_addr NO INTERVALS MODIF ID sel.
DATA:
 wa_email LIKE LINE OF s_email.

Internal Table - Work Area issue

Similar Messages

Maybe you are looking for