Dump Error in Z table

I have created a Z table for the Data Element 'A' with
Data Type - QUAN
Length - 13
Decimals - 3.
Previously it was,
Data Type - NUMC
Length - 8
Decimals - 0.
When i execute in 200 it is working well i can create entries from the table and also through Table maintenance transaction.
But, in Quality Server
I am getting a Dump Error. It is as follows:
Runtime Errors: DYNPRO_FIELD_CONVERSION
Short Text: Conversion Error
Screen Name: "SAPLZTEST"
Screen Number: 0001
Screen Field: "ZTEST-VALUE"
Error Text: "FX020 : Data Lost."

Hi VInnela,
As your variable length earlies was 8 and of type numc and now changed to type p of lenght 13 and decimals 3 it will not have any problem as you increased the lenght.
Please try adjusting the table using Tcode SE14
Here select activate and adjust the table by selecting the radio button SAVE DATA, otherwise you will your data. so please ensure you select the SAVE DATA radio button.
i hope this will meet your requirement.
Thanks and regards
Ramchander Rao.krishnamraju

Similar Messages

Dump error while filling the Setup table

Hi All,
I am trying to fill the setup table.While filling the stup table for 2lis_03_BF datasource, i got the Dump error after some time. I have checked the data in Setup table and found 9000 records.
Shall i proceed further by pulling the data from R/3 to BW.I have checked the data in RSA3 and got some data.
Shall i schedule the data from BW side.
Pls help on this issue.
Thanks,
Siva.

Thanks Reddy and JS.
I have checked the TCODE SM37 and found no jobs are available. I have checked the TCODE : NPRT and found some logs.In this, it is not showing any errors.
I have checked in SM21 and found some errors.
Time_______________Text
17:08:10____________Transaction Canceled M2 630 ( )
17:23:47____________Run-time error "TIME_OUT" occurred
17:23:47____________> Short dump "090302 172347 sand1_W2 2_00 " generated
17:30:08____________Status: 80% of IL00.DAT is in use
17:30:17____________Status: 90% of IL00.DAT is in use
17:30:18____________Overflow of Paging File (032768 Blocks)
17:30:18____________Run-time error "MEMORY_NO_MORE_PAGING" occurred
17:30:19____________> Short dump "090302 173018 sand1_W2 2_00 " generated
Shall i execute filling the setup table again. Do i need to give termination time More ( 2 Hrs difference)
Any issue on refilling the setup table again.
Pls suggest.
Thanks,
Siva.

Short dump error while filling setup tables for 2LIS_06_INV

Hi All,
I am trying to fill the setup table.While filling the stup table for 2lis_06_inv datasource, i got the Dump error after some time.
Error
Runtime Errors         DBIF_RSQL_SQL_ERROR
Exception              CX_SY_OPEN_SQL_DB
Short text
    SQL error in the database when accessing a table.
plz can anyone help me out...

Dear friends,
I tried it by giving the selection on fiscal year,but again same problem.If i give 1 0r 2 document numbers in selection then extractor works fine.
error:in detail.
Runtime Errors         DBIF_RSQL_SQL_ERROR
Exception              CX_SY_OPEN_SQL_DB
Short text
    SQL error in the database when accessing a table.
Information on where terminated
    Termination occurred in the ABAP program "SAPLMRMBW" - in "BW_RETRIEVE_DB_CO".
    The main program was "RMCENEUR ".
    In the source code you have the termination point in line 827
    of the (Include) program "LMRMBWF01".
    The program "SAPLMRMBW" was started as a background job.
    Job Name....... "RMCENEUR"
    Job Number..... 10524100
    The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
    procedure "BW_RETRIEVE_DB_CO" "(FORM)", but it was neither handled locally nor
     declared
    in the RAISING clause of its signature.
    The procedure is in program "SAPLMRMBW "; its source code begins in line
    806 of the (Include program "LMRMBWF01 ".
806 FORM bw_retrieve_db_co USING    t_mcrbkey_bv    TYPE mcrbkey_t
807                                  t_mcrbkey_nbv   TYPE mcrbkey_t
808                                  t_ekbe_acc      TYPE t_ekbe
809                         CHANGING t_mcrbco        TYPE mcrbco_t.
810
811   TYPES: BEGIN OF s_target.
812   TYPES: table_left LIKE rbco.
813   TYPES: table_right TYPE rbex.
814   TYPES: END OF s_target.
815   TYPES: t_target TYPE TABLE OF s_target.
816
817
818   DATA: t_rbco_nbv TYPE t_target,
819         t_rbco_bv   TYPE t_target,
820         s_rbco      TYPE s_target,
821         s_ekbe      LIKE ekbe,
822         s_mcrbco    TYPE mcrbco,
823         l_index     LIKE sy-tabix.
824
   825 * Data source: invoice item non-background
826   IF NOT t_mcrbkey_nbv[] IS INITIAL.
*>>>>>     SELECT * FROM rbco AS r LEFT OUTER JOIN rbex AS i*
828        ON   ( rmandt = imandt AND
829               rbelnr = ibelnr AND
830               rbuzei = ibuzei AND
831               rcobl_nr = icobl_nr )
832        INTO TABLE t_rbco_nbv
833        FOR ALL ENTRIES IN t_mcrbkey_nbv
834        WHERE r~gjahr = t_mcrbkey_nbv-gjahr AND
835              r~belnr = t_mcrbkey_nbv-belnr.
836   ENDIF.
837 * Data source: invoice item background
838   IF NOT t_mcrbkey_bv[] IS INITIAL.
839     SELECT * FROM rbco AS r LEFT OUTER JOIN rbex AS i
840        ON   ( rmandt = imandt AND
841               rbelnr = ibelnr AND
842               rbuzei = ibuzei AND
843               rcobl_nr = icobl_nr )
844        INTO TABLE t_rbco_bv
845        FOR ALL ENTRIES IN t_mcrbkey_bv
846        WHERE r~gjahr = t_mcrbkey_bv-gjahr AND
Thnks in advance

Error in creating Table Maintenance for TABLES: J_2IRG1BAL ,Dump error show

Dear Gurus
I have Created one Table Maintenance for TABLES: J_2IRG1BAL ,
1) I have take function group as same as table name like J_2IRG1BAL
3) Authorization Group &NC&
4) Authorization object S_TABU_DIS
5) Function group J_2IRG1BAL
6) Package J1I5
7) Maintenance type one step.
8) Maint. Screen No. Overview screen 2009.
9) Recording routine STD recording routines .
I have assign screen single screen 1 but it will not take the screen so ill put screen 2009 ,the system will not not accept the screen but I proposed to Save and activate the table maintenance generator and created and save the function group ,the table is ready to save the entries
We have to go to SM30 then put 4-5 entries ,after that a dump error shows
Which i have attachéd in this mail kindly help me out
Its effect in production server.
I have found that the error is given below I have mentioned all the details
Kindly read this
I have created function group J_2IRG1BAL and assign Package J1I5 and function group,J1I5 is already a Function group so problem occurs a dump error message displays
Kindly give me the right solution all the Clients are effected
110,100 150,250 these all are effected development clients
300 is prod client this is also affected because I have created a table maintenance generator and send the req to production .
*Dump Error Shows in Production*
Runtime Errors SYNTAX_ERROR
Date and Time 11.12.2008 09:26:30
What happened?
| Error in ABAP application program.
Error analysis
In program "SAPLJ1I5 ", the following syntax error occurred:
"The program "SAPLJ1I5" is not Unicode-compatible, according to its pro"
"gram attributes."
The current ABAP program "SAPLSVIM" had to be terminated because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
In program "SAPLJ1I5 ", the following syntax error occurred
in the Include "SAPLJ1I5 " in line 0:
"The program "SAPLJ1I5" is not Unicode-compatible, according to its pro"
"gram attributes."
rigger Location of Runtime Error |
Program SAPLSVIM
Include LSVIMU01
Row 107
Module type (FUNCTION)
| Module Name VIEW_MAINTENANCE
Author and last person to change the Include are:
Author "TTLABAP2 "
Last changed by "TTLABAP2 "
105
Initialisierung des Abgleichsmandanten zum View *
106
>>>>>
vim_default_upgr_clnt-viewname = x_header-viewname.
108
vim_default_upgr_clnt-client = client_for_upgrade.
109
PERFORM vim_set_global_field_value IN PROGRAM (fpool)
| 110| USING 'VIM_DEFAULT_UPGR_CLNT' 'C' vim_default_upgr_clnt rc.

I have send you all the details regarding the table maintenance generator
error is shown below
 I have Created one Table Maintenance for TABLES: J_2IRG1BAL ,
1) I have take function group as same as table name like J_2IRG1BAL
3) Authorization Group &NC&
4) Authorization object S_TABU_DIS
5) Function group J_2IRG1BAL
6) Package J1I5
7) Maintenance type one step.
8) Maint. Screen No. Overview screen 2009.
9) Recording routine STD recording routines .
I have assign screen single screen 1 but it will not take the screen so ill put screen 2009 ,the system will not not accept the screen but I proposed to Save and activate the table maintenance generator and created and save the function group ,the table is ready to save the entries
We have to go to SM30 then put 4-5 entries ,after that a dump error shows
Which i have attachéd in this mail kindly help me out
Its effect in production server.
I have found that the error is given below I have mentioned all the details
Kindly read this
I have created function group J_2IRG1BAL and assign Package J1I5 and function group,J1I5 is already a Function group so problem occurs a dump error message displays
Kindly give me the right solution all the Clients are effected
110,100 150,250 these all are effected development clients
300 is prod client this is also affected because I have created a table maintenance generator and send the req to production .
 Runtime Errors SYNTAX_ERROR
Date and Time 11.12.2008 09:26:30
ShrtText
Syntax error in program "SAPLJ1I5 ".
What happened?
Error in ABAP application program.
The current ABAP program "SAPLSVIM" had to be terminated because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
In program "SAPLJ1I5 ", the following syntax error occurred
in the Include "SAPLJ1I5 " in line 0:
"The program "SAPLJ1I5" is not Unicode-compatible, according to its pro"
"gram attributes."
Author and last person to change the Include are:
Author "TTLABAP2 "
Last changed by "TTLABAP2 "
Error analysis
In program "SAPLJ1I5 ", the following syntax error occurred:
"The program "SAPLJ1I5" is not Unicode-compatible, according to its pro"
"gram attributes."
Trigger Location of Runtime Error
Program SAPLSVIM
Include LSVIMU01
Row 107
Module type (FUNCTION)
Module Name VIEW_MAINTENANCE
Source Code Extract
Line
SourceCde
77
TRANSPORTING NO FIELDS.
78
IF sy-subrc NE 0.
79
SELECT SINGLE * FROM tfdir WHERE funcname EQ <function_name>.
80
IF sy-subrc NE 0.
81
RAISE no_editor_function.
82
ELSE.
83
length = strlen( function_name1 ).
84
ASSIGN function_name1(length) TO <function_name>.
85
SELECT SINGLE * FROM tfdir WHERE funcname EQ <function_name>.
86
IF sy-subrc NE 0.
87
RAISE no_database_function.
88
ENDIF.
89
ENDIF.
90
INSERT x_header-viewname INTO alr_checked_views INDEX sy-tabix.
91
ELSE.
92
length = strlen( function_name1 ).
93
ASSIGN function_name1(length) TO <function_name>.
94
ENDIF.
95
96
Initialisierung der RFC-Destination zum View *
97
98
FPOOL+4 = X_HEADER-AREA.
99
fpool = x_header-fpoolname.
100
vim_default_rfc_dest-viewname = x_header-viewname.
101
vim_default_rfc_dest-rfcdest = rfc_destination_for_upgrade.
102
PERFORM vim_set_global_field_value IN PROGRAM (fpool)
103
USING 'VIM_DEFAULT_RFC_DEST' 'C' vim_default_rfc_dest rc.
104
105
Initialisierung des Abgleichsmandanten zum View *
106
>>>>>
vim_default_upgr_clnt-viewname = x_header-viewname.
108
vim_default_upgr_clnt-client = client_for_upgrade.
109
PERFORM vim_set_global_field_value IN PROGRAM (fpool)
110
USING 'VIM_DEFAULT_UPGR_CLNT' 'C' vim_default_upgr_clnt rc.
111
112
set flag if complex selection conditions in sellist *
113
114
IF complex_selconds_used NE space.
115
READ TABLE dba_sellist INDEX 1.
116
IF sy-subrc EQ 0 AND dba_sellist-cond_kind EQ space.
117
dba_sellist-cond_kind = 'C'. MODIFY dba_sellist INDEX 1.
118
ENDIF.
119
ENDIF.
120
121
direkter Vergleich: Flagge setzen usw. *
122
123
IF view_action EQ vim_direct_upgrade.
124
view_action = aendern.
125
PERFORM vim_set_global_field_value IN PROGRAM (fpool)
126
USING 'VIM_SPECIAL_MODE' 'C' vim_direct_upgrade rc.

SAP HR Security_ Dump error after table maintenance (T77UA)

Hi,
In our project we have both general authorizations and structural authorizations. There are ESS, MSS and HR Roles maintained in PFCG transactions. Our approach of Role assignments (profiles) is for Users and not against positions.
Hence table T77UA is maintained with Authorization profile (created for HR) against users (who are HR). This authorization profile is used in HR Role and this Role is assigned to the users using SU01 transaction.
I have also used Evaluation path in the authorization profile, which will fetch all the employees under the HR, so that the HR will be authorized to access the data of those employees.
After maintaining the table (T77UA), when i try to test the HR Role in backend for eg: PA20 or PA30 to display any employee data under him, i am getting dump error.
Can someone guide me how i can resolve this!!
Thanks!

Hi Christine,
Please find below the error details:
The dump comes when i maintain the Table T77UA (authorization profile against the username).
Is the manual way of maintaining the table, a wrong method? Is there any other approach to go ahead with the structural authorization without maintaining this table? Please suggest.
Runtime Errors:         TSV_TNEW_PAGE_ALLOC_FAILED
Short text
    No more storage space available for extending an internal table.
What happened?
    You attempted to extend an internal table, but the required space was
    not available.
Error analysis
    The internal table "\FUNCTION-POOL=RHAC\DATA=OBJECT_TAB1[]" could not be
     further extended. To enable
    error handling, the table had to be delete before this log was written.
    As a result, the table is displayed further down or, if you branch to
    the ABAP Debugger, with 0 rows.
    At the time of the termination, the following data was determined for
    the relevant internal table:
    Memory location: "Session memory"
    Row width: 1388
    Number of rows: 1537109
    Allocated rows: 1537109
    Newly requested rows: 8 (in 1 blocks)
Trigger Location of Runtime Error
    Program                                 SAPLRHAC
    Include                                 LRHACF04
    Row                                     90
    Module type                             (FORM)
    Module Name                             FILL_SET_TAB
Source Code Extract
Line SourceCde
   60                   object_tab2-skipf = relat_tab-skipf.
   61                   object_tab2-pup   = rec_check_tab_index.
   62                   IF rhas-sflag EQ 'X'.
   63                     PERFORM build_sel_interval
   64                       USING t1001-begda       t1001-endda
   65                             object_tab-sbegd object_tab-sendd
   66                             object_tab2-sbegd object_tab2-sendd.
   67                   ELSE.
   68                     object_tab2-sbegd = object_tab-sbegd.
   69                     object_tab2-sendd = object_tab-sendd.
   70                   ENDIF.
   71                   APPEND object_tab2.
   72                   blatt = off.
   73                   object_tab2_count   = object_tab2_count + 1.
   74                 WHEN '2'.
   75                   CLEAR object_tab1.
   76                   MOVE-CORRESPONDING t1001 TO object_tab1.
   77                   object_tab1-otype   = t1001-sclas.
   78                   object_tab1-objid   = t1001-sobid.
   79                   object_tab1-skipf = relat_tab-skipf.
   80                   object_tab1-pup   = rec_check_tab_index.
   81                   IF rhas-sflag EQ 'X'.
   82                     PERFORM build_sel_interval
   83                       USING t1001-begda       t1001-endda
   84                             object_tab-sbegd object_tab-sendd
   85                             object_tab1-sbegd object_tab1-sendd.
   86                   ELSE.
   87                     object_tab1-sbegd = object_tab-sbegd.
   88                     object_tab1-sendd = object_tab-sendd.
   89                   ENDIF.
>>>>>                   APPEND object_tab1.
   91                   blatt = off.
   92                   object_tab1_count   = object_tab1_count + 1.
   93               ENDCASE.
   94             ELSE.
   95               exit_sw = on.
   96               EXIT.
   97             ENDIF.
   98
   99           ENDIF.
100           ADD 1 TO t1001_index.
101         ENDDO.
102       ELSE.
103         LOOP AT eo_1001 WHERE plvar      EQ rhas-plvar
104                          AND   otype      EQ object_tab-otype
105                          AND   objid      EQ object_tab-objid
106                          AND   infty      EQ rela_infty
107                          AND   rsign      EQ relat_tab-rsign
108                          AND   relat      EQ relat_tab-relat
109                          AND   priox      BETWEEN min_priox
Thanks!

Short dump while accessing the table

There is a report ppioa0000, when executing the report it is going for short dump, error analysis showing that
when accessing the attributes of dictionary table IOSOPER meaningless values are found.
and ABAP run time error showing that DDIC_FIELD_ACCESS_ERROR
suggest me,
thanks and regards
krishna

The database is damaged, links between SAP dictionary and actual database seems to be broken. Try to use SE14 to adjust database.
Regards

Short dump error report

What is the purpose of short dump error report generated by the system? What r the major parts/section of this report?

hi please look through this:
Whenever any transaction or any process is executed it hits an ABAP code.
If there is any issue in executing the code the situation is called "ABAP DUMP" or 'Short Dump'
Transaction ST22 is used to check any ABAP Dump within a given duration.
U can also fix the issue with the help of ABAP editor (Transaction Code SE38) if u r good with ABAP.
you can select back to the last 14 days if you are
running the SAP_REORG_ABAPDUMPS job (program RSSNAPDL) which deletes te
old ABAP dumps every day, possibly further if you run it weekly or
monthly.
sap-basis sap-basisAll Groups Ignore this text box. It is used to detect spammers.If you enter anything into this text box, no search results will be displayed.
SAP Groups > Technical-functional > sap-basis > Message
About This Group | Invite peers to join this group
<< Prev thread < Prev msg Next msg > Next thread >>
short dump----urgent
Reply from Keith Lewis on 5/2/2003 3:22:00 AM
Good explanation Joy, but it is not only limited to the current day and
yesterday. If you click on the Selection button you can select previous
days as well. In fact you can select back to the last 14 days if you are
running the SAP_REORG_ABAPDUMPS job (program RSSNAPDL) which deletes te
old ABAP dumps every day, possibly further if you run it weekly or
monthly.
Cheers
Keith
SAP R/3 Support Specialist
Information Services International
Tel +44 1664 41 6178 Mobile +44 7887 627818
E-mail email@removed
Archive Page - http://www.ittoolbox.com//I/sap-r3-basis.asp
Dear sreenivas
If you receive an error message in the R/3 System log (SM21), or if you
see
a terminated update in the update service analysis transaction (SM13), or
DB
realated error ,check for dumps using the dump analysis transaction
(transaction ST22), or choose Tools -> Administration -> Monitoring ->
Dump
analysis.
Transaction ST22 enables you to analyze short dumps from the current and
previous day.
The dump analysis function shows you:
What happened
What you can do
How to correct the error
The dump analysis function also provides an error ID and keywords that you
can use to search in SAPNet, as well as information about:
The system environment
Users and transactions
Transaction ST22 enables you to analyze the following data:
Date, time, user, client
Contents of system and data fields
Contents of internal tables and application tables
ST22 is a very nice feature in SAP. This is where all the system errors
and users mistakes showed up. If there is a problem that you cannot
solve and you contact SAP support, they look at this area to analyze it.
This gives us lead where to handle the problems.
Error analysis
How to correct the error
System environment
User, transaction...
Information on where termination occurred
Contents of system fields
Chosen variables
Active calls / events
Internal notes
Active calls in SAP kernel
List of ABAP programs affected
List of internal tables
Directory of application tables (contents)
Directory of data areas (administration information)
Directory of data areas (contents)
ABAP control blocks CONT
End of runtime analysis
i think this would be helpful
regards
sravani

Short dump error when using count(*)

Hi Experts
I am getting a short dump error when selecting the records >= current date - 30 see the coding and comment please correct the coding I want to know the ztable records it is important for command interface.
I have 1402345 records available after deleting the records but as the memory is not enough it is giving short dump error
select count(*) from ZINT_TABLE
select count(*) from ZINT_MSGS
 select * from zint_data
 nto table izint_d2 . "PACKAGE SIZE 20000
 where STATUS = 'OK' AND CREATED_ON >= w_date1. " VALUE
endselect.**
report z_eslp_command_records.
data: cnt type i.
data: cnt2 type i.
data: cnt3 type i.
data: cnt4 type i.
DATA:
 w_date1 like sy-datum .
DATA:
 w_date2 like sy-datum.
data: izint_msgs type table of zint_msgs.
data: izint_data type table of zint_data.
data: izint_m2 type table of zint_msgs.
data: izint_d2 type table of zint_data.
INITIALIZATION.
w_date1 = sy-datum - 30.
w_date2 = sy-datum - 30.
select * from zint_data
 into table izint_data PACKAGE SIZE 3000
 where STATUS = 'OK' AND CREATED_ON <= w_date1. " ZERO
endselect.
select * from zint_msgs
 into table izint_msgs PACKAGE SIZE 3000
 where CREATED_ON <= w_date2. " ZERO
endselect.
select * from zint_data
 into table izint_d2 PACKAGE SIZE 20000
 where STATUS = 'OK' AND CREATED_ON >= w_date1. " VALUE
endselect.
select * from zint_msgs
 into table izint_m2 PACKAGE SIZE 20000
where CREATED_ON >= w_date2. " VALUE
endselect.
select * from zint_data
 into table izint_data2
where STATUS = 'OK' AND CREATED_ON >= CONVERT(CHAR(8), GETDATE() - 30, 112)).
ENDSELECT.
select * from zint_msgs
 into table izint_msgs2
where CREATED_ON >= CONVERT(CHAR(8), GETDATE() - 30, 112)).
ENDSELECT.
sort izint_data by created_on ascending.
sort izint_msgs by created_on ascending.
sort izint_d2 by created_on ascending.
sort izint_m2 by created_on ascending.
describe table izint_data lines cnt.
describe table izint_msgs lines cnt2.
describe table izint_d2 lines cnt3.
describe table izint_m2 lines cnt4.
write:/ ' Note: THE RECORDS COUNTED SHOULD SHOW ZERO ELSE THE SCRIPT FAILED TO RUN' color 3.
skip.
write:/ '1. Records counted in ZINT_DATA <=current date - 30 :' color 2, cnt color 4.
write:/ '2. Records available in ZINT_DATA >=current date - 30 'color 4, cnt3 color 4 .
skip.
write:/ '2. Records counted in ZINT_MSGS <=current date - 30 :' color 2 , cnt2 color 4.
write:/ '4. Records available in ZINT_MSGS >=current date - 30 'color 4 , cnt4 color 4 .
TOP-OF-PAGE.
WRITE:/55(60) ' WAGNERS INVESTMENT LIMITED '.
WRITE:/50(40) ' Command Interface Data' CENTERED .
WRITE:/50(40) '----
' CENTERED .
FORMAT INTENSIFIED ON.
SKIP.
"FORMAT COLOR COL_HEADING.
ULINE.
FORMAT COLOR 1.
END-OF-PAGE.

Answer

Getting a program Dump Error in Herarchial ALV

Hello All,
I am getting a dump error when I am executing the below program. Kindly help as I am not getting the output. However all the subroutines are getting properly populated with data. Getting a dump error while calling the function : REUSE_ALV_HIERSEQ_LIST_DISPLAY
Pasted below are both the question and solution. Copy the solution in SE38 and execute it to check out the dump error.
Kindly help.
Thanks,
Vinod.
QUESTION :-
Objective
 Hierarchical ALV for displaying Sales documents per customer
Design
 Create a program that will allow the user to display all customers that have placed Sales Orders in the given date range. The user will have an ability to drill-down to see the sales order items per customer.
 Selection screen fields
 Sales order creation date (range)
 Customer number (range)
 Output
 Header
 Customer Number
 Customer Name
 Total Order value (sum of order values from items below)
 Details
Sales order number
Material number
Order quantity
Order value
Reference
 Tables: KNA1, VBAK, VBAP
 Transaction VA03 (Sales order)
SOLUTION :-
*& Report Z_HALV_32722 *
REPORT Z_HALV_32722 .
TYPE-POOLS: slis.
TABLES : kna1,
 vbak.
SELECT-OPTIONS: s_cst_no FOR kna1-kunnr.
SELECT-OPTIONS: s_cr_dt FOR vbak-erdat.
DATA : BEGIN of ty_hdr,
 kunnr TYPE vbak-kunnr,
 name1 TYPE kna1-name1,
 netwr TYPE vbak-netwr,
 END of ty_hdr,
 gt_hdr LIKE TABLE OF ty_hdr,
 gs_hdr LIKE LINE OF gt_hdr.
DATA : BEGIN of ty_ln,
 kunnr TYPE vbak-kunnr,
 vbeln TYPE vbap-vbeln,
 matnr TYPE vbap-matnr,
 kwmeng TYPE vbap-kwmeng,
 netwr TYPE vbap-netwr,
 END of ty_ln,
 gt_ln LIKE TABLE OF ty_ln,
 gs_ln LIKE LINE OF gt_ln.
DATA : BEGIN of ty_hdr1,
 kunnr TYPE vbak-kunnr,
 END of ty_hdr1,
 gt_hdr1 LIKE TABLE OF ty_hdr1,
 gs_hdr1 LIKE LINE OF gt_hdr1.
DATA : gt_fc TYPE slis_t_fieldcat_alv,
 gs_fc LIKE LINE OF gt_fc,
 gs_k_fld TYPE slis_keyinfo_alv,
 gt_layout TYPE slis_layout_alv,
 gv_repid TYPE sy-repid.
START-OF-SELECTION.
gv_repid = sy-repid.
perform fetch_data.
perform prepare_fc.
perform prepare_layout.
perform show_output.
*& Form fetch_data
 text
--> p1 text
<-- p2 text
form fetch_data .
SELECT kunnr
INTO CORRESPONDING FIELDS OF TABLE gt_hdr1
FROM vbak
WHERE vbak~kunnr IN s_cst_no
AND vbak~erdat IN s_cr_dt.
DELETE ADJACENT DUPLICATES FROM gt_hdr1 COMPARING kunnr.
LOOP AT gt_hdr1 INTO gs_hdr1.
SELECT SINGLE vbakkunnr kna1name1 SUM( vbak~netwr )
INTO (gs_hdr-kunnr, gs_hdr-name1, gs_hdr-netwr)
FROM vbak INNER JOIN kna1
ON vbakkunnr = kna1kunnr
WHERE vbak~kunnr = gs_hdr1-kunnr
GROUP BY vbakkunnr kna1name1.
APPEND gs_hdr TO gt_hdr.
SELECT vbakkunnr vbapvbeln vbapmatnr vbapkwmeng vbap~netwr
INTO CORRESPONDING FIELDS OF TABLE gt_ln
FROM vbap INNER JOIN vbak
ON vbapvbeln = vbakvbeln
WHERE vbak~kunnr = gs_hdr1-kunnr.
ENDLOOP.
endform. " fetch_data
*& Form prepare_fc
 text
--> p1 text
<-- p2 text
form prepare_fc .
CLEAR gs_k_fld.
gs_k_fld-header01 = 'KUNNR'.
gs_k_fld-item01 = 'KUNNR'.
CLEAR gs_fc.
gs_fc-fieldname = 'KUNNR'.
gs_fc-tabname = 'GT_HDR'.
gs_fc-seltext_l = text-001.
APPEND gs_fc TO gt_fc.
CLEAR gs_fc.
gs_fc-fieldname = 'NAME1'.
gs_fc-tabname = 'GT_HDR'.
gs_fc-seltext_l = text-002.
APPEND gs_fc TO gt_fc.
CLEAR gs_fc.
gs_fc-fieldname = 'NETWR'.
gs_fc-tabname = 'GT_HDR'.
gs_fc-seltext_l = text-003.
APPEND gs_fc TO gt_fc.
CLEAR gs_fc.
gs_fc-fieldname = 'VBELN'.
gs_fc-tabname = 'GT_LN'.
gs_fc-seltext_l = text-004.
APPEND gs_fc TO gt_fc.
CLEAR gs_fc.
gs_fc-fieldname = 'MATNR'.
gs_fc-tabname = 'GT_LN'.
gs_fc-seltext_l = text-005.
APPEND gs_fc TO gt_fc.
CLEAR gs_fc.
gs_fc-fieldname = 'KWMENG'.
gs_fc-tabname = 'GT_LN'.
gs_fc-seltext_l = text-006.
APPEND gs_fc TO gt_fc.
CLEAR gs_fc.
gs_fc-fieldname = 'NETWR'.
gs_fc-tabname = 'GT_LN'.
gs_fc-seltext_l = text-007.
APPEND gs_fc TO gt_fc.
endform. " prepare_fc
*& Form prepare_layout
 text
--> p1 text
<-- p2 text
form prepare_layout .
gt_layout-colwidth_optimize = 'X'.
gt_layout-expand_fieldname = 'TST'.
endform. " prepare_layout
*& Form show_output
 text
--> p1 text
<-- p2 text
form show_output .
CALL FUNCTION 'REUSE_ALV_HIERSEQ_LIST_DISPLAY'
EXPORTING
I_INTERFACE_CHECK = ' '
 I_CALLBACK_PROGRAM = gv_repid
I_CALLBACK_PF_STATUS_SET = ' '
I_CALLBACK_USER_COMMAND = ' '
 IS_LAYOUT = gt_layout
 IT_FIELDCAT = gt_fc
IT_EXCLUDING =
IT_SPECIAL_GROUPS =
IT_SORT =
IT_FILTER =
IS_SEL_HIDE =
I_SCREEN_START_COLUMN = 0
I_SCREEN_START_LINE = 0
I_SCREEN_END_COLUMN = 0
I_SCREEN_END_LINE = 0
I_DEFAULT = 'X'
I_SAVE = ' '
IS_VARIANT =
IT_EVENTS =
IT_EVENT_EXIT =
 i_tabname_header = 'GT_HDR'
 i_tabname_item = 'GT_LN'
I_STRUCTURE_NAME_HEADER =
I_STRUCTURE_NAME_ITEM =
 is_keyinfo = gs_k_fld
IS_PRINT =
IS_REPREP_ID =
I_BYPASSING_BUFFER =
I_BUFFER_ACTIVE =
IMPORTING
E_EXIT_CAUSED_BY_CALLER =
ES_EXIT_CAUSED_BY_USER =
tables
 t_outtab_header = GT_HDR[]
 t_outtab_item = GT_LN[]
EXCEPTIONS
PROGRAM_ERROR = 1
OTHERS = 2
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
endform. " show_output

Everything looks fine with the gt_layout, it is not an internal table, so no need to append to it, it is simply a structure, but you do tell it that TST is the expand field, but there is no field of this name in your internal for the header, so add it like this.
DATA : BEGIN of ty_hdr,
kunnr TYPE vbak-kunnr,
name1 TYPE kna1-name1,
netwr TYPE vbak-netwr,
TST type c,
END of ty_hdr,
Doing so should make you program work correctly.
Regards,
Rich Heilman
Message was edited by:
 Rich Heilman

I am getting dump error while running one report in one select query

Hi,
While running a report program, I am getting a dump error in one select query. So could you please correct the select query so that I can't face the dump error.
SELECT vbeln parvw kunnr INTO CORRESPONDING FIELDS OF TABLE l_t_vbpa
FROM vbpa
FOR ALL ENTRIES IN l_t_backorder_item
WHERE vbeln = l_t_backorder_item-vbeln AND
( ( parvw = c_we AND kunnr IN rng_shipto ) OR ( parvw = c_ag AND
kunnr IN rng_soldto ) ) .
<removed by moderator>
Best Regards,
BDP
Edited by: Thomas Zloch on Apr 30, 2010 12:31 PM

Hi Bansidhar,
It would be helpful if you could tell what type of dump it is.
If it is a timeout you should check whether l_t_backorder_item is empty - in this case ALL document numbers are selected. f you get the timeout with a populated table consider converting the l_t_backorder_item table into one ore more ranges tables - the select with ranges tables is way quicker than 'for all entries'. But take care the ranges table has not to many entries - the SAP SQL converter puts this into one huge SQL statement and this might become too big to be handled by the database (depends on the actual underlying database).
I would also consider splitting the SELECT into two (2nd one with 'appending into table') to make the code easier to understand It also helps the database system determining a strategy for the select.
Regards,
Gerd Rother

Dump error while creating or double click the info package

Hello experts,
I have actived infocube 0FIAR_C03 in BI content. Ago, The creation infopackage have been deleted in the past , today, I created a infopackage, while I update mode selected u2018initialize delta processu2019, then click save button , the system prompt u2018Deltas already loaded for request REQU_D64R47LDUSZHY9CBIB86WMLFJ init.selection; no 2. initu2019, I canoti save it for my setting. Why is this?
Then I have search cause in SDN, and I have reference OSS Note 852443 to do .
Note 852443 have mention some table: RSSELDONE、RSSDLINIT、RSSDLINITSEL、ROOSPRMSC、ROOSPRMSF.
I have to delete that request of record using se16 in these tables: RSSELDONE、RSSDLINIT、RSSDLINITSEL.
in my BI 7.0 system, ROOSPRMSC、ROOSPRMSF is no any data.
I was no found delta queue in RSA7.
Now . Dump error while creating or double click the info package, how can I change this?
Please let me know the solution.
Thanks for your help.
Best Regards
Steve

Here are some links which deals with same issue.
Re: Dump In Infopackage
Re: Getting into Short dump at the time of selecting InfoPackage to execute for
Short dump while performing init in infopackage
Re: Infopackage going into short dump
Thanks.

Html error while downloading table entries to Excel.

Hi,
I am getting an error while downloading table entries from webdynpro to excel. After some entries below error script comes and this is not comming all the times.
Is this because of large size?Can anyone please suggest me on this?
Here is the dump:
[code]<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
 <title>Error Report</title>
<style>
td {font-family : Arial, Tahoma, Helvetica, sans-serif; font-size : 14px;}
A:link
A:visited
A:active
</style>
</head>
<body marginwidth="0" marginheight="0" leftmargin="0" topmargin="0" rightmargin="0">
<table width="100%" cellspacing="0" cellpadding="0" border="0" align="left" height="75">
<tr bgcolor="#FFFFFF">
 <td align="left" colspan="2" height="48"> 500 Internal Server Error</td>
</tr>
<tr bgcolor="#3F73A3">
 <td height="23" width="84"><img width=1 height=1 border=0 alt=""></td>
 <td height="23"><img width=1 height=1 border=0 alt=""></td>
 <td align="right" height="23">SAP J2EE Engine/6.40 </td>
</tr>
<tr bgcolor="#9DCDFD">
 <td height="4" colspan="3"><img width=1 height=1 border=0 alt=""></td>
</tr>
</table>
 
 Application error occurs during processing the request.
<table><tr><td valign="top"> Details:</td><td valign="top"><PRE><pre>com.sap.engine.services.servlets_jsp.server.exceptions.WebIllegalStateException: The stream has already been committed.
 at com.sap.engine.services.servlets_jsp.server.runtime.client.HttpServletResponseFacade.sendError(HttpServletResponseFacade.java:792)
 at com.sap.engine.services.servlets_jsp.server.runtime.client.HttpServletResponseFacade.sendError(HttpServletResponseFacade.java:780)
 at com.sap.engine.services.servlets_jsp.server.runtime.client.HttpServletResponseFacade.sendError(HttpServletResponseFacade.java:768)
 at com.sap.tc.webdynpro.serverimpl.core.url.WebDynproExchangeHandler.responseCachedWebResource(WebDynproExchangeHandler.java:98)
 at com.sap.tc.webdynpro.serverimpl.core.url.WebDynproExchangeHandler.doExchange(WebDynproExchangeHandler.java:189)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doExchangeProcessing(DispatcherServlet.java:164)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:119)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:48)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:391)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:265)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:345)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:323)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:865)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:240)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
 at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
</pre></PRE></td></tr></table>
</body>
</html>[/code]
Thanks,
Sanjeev

Hallo Sanjeev,
How do you exactly "download the table entries from Web Dynpro to Excel?"
I wrote a new Wiki Code Tutorial which demonstrates how to download an Excel file from a Web Dynpro Table UI element on-demand. In this scenario the resource gets re-created on every request. The solution is based on re-initializing the context with a new 0-byte resource object within the calculated context attribute getter method.
See <a href="https://wiki.sdn.sap.com/wiki/display/Snippets/ExportingTableDatainWebDynproJava-SAPNetWeaver04s">Exporting Table Data in Web Dynpro Java - SAP NetWeaver 04s</a>
Regards, Bertram

Dump While filling setup table

Hi Frineds,
We have moved some fields from Cimmunication structute to Extract structure at LBWE.
We deleted data at setup table and also at RSA7.
While filling the setup tables it is giving the below Dump.
Please provide me solution.
Runtime Errors         COMPUTE_BCD_OVERFLOW
Except.                CX_SY_ARITHMETIC_OVERFLOW
Date and Time          02.12.2010 12:41:24
Short text
     Overflow during the arithmetical operation (type P) in program "SAPLMCEX".
What happened?
     Error in the ABAP Application Program
     The current ABAP program "SAPLMCEX" had to be terminated because it has
     come across a statement that unfortunately cannot be executed.
Error analysis
     An exception occurred that is explained in detail below.
     The exception, which is assigned to class 'CX_SY_ARITHMETIC_OVERFLOW', was not
      caught in
     procedure "MAPPING_VA_MC11VA0ITM" "(FORM)", nor was it propagated by a RAISING
      clause.
     Since the caller of the procedure could not have anticipated that the
     exception would occur, the current program is terminated.
     The reason for the exception is:
     An overflow was discovered in an ongoing arithmetical operation with
     operands of type P. Possible causes are:
     1. The result field of type P is too small for the result.
    2. The result or a intermediate result has more than 31 decimal places.
Missing RAISING Clause in Interface
    Program                                 SAPLMCEX
    Include                                 LMCEXM03
    Row                                     53
    Module type                             (FORM)
    Module Name                             MAPPING_VA_MC11VA0ITM
Trigger Location of Exception
    Program                                 SAPLMCEX
    Include                                 LMCEXM03
    Row                                     105
    Module type                             (FORM)
    Module Name                             MAPPING_VA_MC11VA0ITM
Source Code Extract
Line SourceCde
   75   MOVE-CORRESPONDING MC11VA2ITM_STR TO MC11VA0ITM_TAB.
   76   MOVE-CORRESPONDING MC11VA4ITM_STR TO MC11VA0ITM_TAB.
   77   MOVE-CORRESPONDING MC11VA5ITM_STR TO MC11VA0ITM_TAB.
   78   MOVE-CORRESPONDING MC11VA6ITM_STR TO MC11VA0ITM_TAB.
   79
   80 * Felder Mit Sonderbehandlungen
   81   MOVE P_XMCVBAK-SPART TO MC11VA0ITM_TAB-SPARA.
   82   MOVE P_XMCVBAK-WAERK TO MC11VA0ITM_TAB-WAERK_VBAK.
   83   MOVE P_XMCVBAK-VGTYP TO MC11VA0ITM_TAB-VGTYP_AK.
   84   PERFORM CONVERT_PROJ_NUM USING    P_XMCVBAP-PS_PSP_PNR
   85                            CHANGING MC11VA0ITM_TAB-PS_POSID.
   86
   87   MOVE 1 TO MC11VA0ITM_TAB-ANZAUPO.
   88
   89   PERFORM READ_T001 USING P_XMCVBAK-BUKRS.
   90   MC11VA0ITM_TAB-PERIV = T001-PERIV.
   91
   92   MOVE P_XMCVBKD-CAMPAIGN TO MC11VA0ITM_TAB-MCEX_APCAMPAIGN.
   93   PERFORM get_apoplanned_va
   94     USING p_xmcvbak p_xmcvbap
   95     CHANGING MC11VA0ITM_TAB-APOPLANNED.
   96
   97   IF P_XMCVBAK-ABDIS NE SPACE.
   98     MC11VA0ITM_TAB-MCBW_NETPR_AVKM = P_XMCVBAP-NETPR.
   99     IF P_XMCVBAP-KPEIN NE 0.
100       MC11VA0ITM_TAB-MCBW_NETPR_AVKM =
101                    MC11VA0ITM_TAB-MCBW_NETPR_AVKM / P_XMCVBAP-KPEIN.
102     ENDIF.
103   ELSE.
104     IF P_XMCVBAP-KWMENG NE 0.
>>>>>       MC11VA0ITM_TAB-MCBW_NETPR_AVKM =
106                         P_XMCVBAP-NETWR / P_XMCVBAP-KWMENG.
107     ENDIF.
108   ENDIF.
109
110 * ROCANCEL ermitteln
111   PERFORM ROCANCEL_SETZEN
112           USING P_XMCVBAK-SUPKZ MC11VA0ITM_TAB-ROCANCEL.
113
114   APPEND MC11VA0ITM_TAB.
115
116 ENDFORM.                               " MAPPING_VA_MC11VA0ITM
117 &----
118 *&      Form MAPPING_VA_MC11V_0ITM
119 &----
120 *       text
121 ----
122 *      -->P_XMCVBAK text                                              *
123 *      -->P_XMCVBUK text                                              *
124 *      -->P_XMCVBAP text                                              *
Thanks &Regards,
Anand.

Hello friend,
I have got the same dump error. Do you have the solution. How was it done.
Please respond soon. Thanks.

Dump error while running termination action

I'm facing a dump error while running termination action, please, if some one wud help me out of this error. here when im termination action the system is opening action infotype when given the date of termination and try to save, system shows a warning message that "Record valid from 08.08.1995 to 31.12.9999 delimited at end" then I press enter and system is asking me to save. when I do so, rather than it taking me to another screen its throwing a dump error.
Runtime Errors         SYNTAX_ERROR
Date and Time          21.10.2008 18:54:05
Short dump has not been completely stored (too big)
Short text
     Syntax error in program "SAPLCACS_BU_PARTNER ".
What happened?
     Error in the ABAP Application Program
     The current ABAP program "SAPLBUD_CHECK" had to be terminated because it has
     come across a statement that unfortunately cannot be executed.
     The following syntax error occurred in program "SAPLCACS_BU_PARTNER " in
      include "LCACS_BU_PARTNERU44 " in
     line 19:
     "The key of internal table "LT_BUT0BK" contains components of type "X" "
     "or "XSTRING". The "READ TABLE LT_BUT0BK" statement is not permitted fo"
     "r such tables in a Unicode context."
     The include has been created and last changed by:
     Created by: "SAP "
     Last changed by: "SAP "
     Error in the ABAP Application Program
     The current ABAP program "SAPLBUD_CHECK" had to be terminated because it has
     come across a statement that unfortunately cannot be executed.
Error analysis
     The following syntax error was found in the program SAPLCACS_BU_PARTNER :
     "The key of internal table "LT_BUT0BK" contains components of type "X" "
     "or "XSTRING". The "READ TABLE LT_BUT0BK" statement is not permitted for
"r such tables in a Unicode context."
ger Location of Runtime Error
Program                                 SAPLBUD_CHECK
Include                                 LBUD_CHECKF01
Row                                     1.129
Module type                             (FORM)
Module Name                             RLDEL_CHECK
ce Code Extract
SourceCde
9
0 *------ ... Funktionsbausteine ermitteln -
1   CALL FUNCTION 'BDT_TBZ1F_GET'
2     EXPORTING
3       iv_objcn = gc_objcn_bupa
4       iv_objap = gc_objap_bupa
5     TABLES
6       et_tbz1f = lt_tbz1f
7     EXCEPTIONS
8       not_found = 1
9       OTHERS    = 2.
0   READ TABLE lt_tbz1f INDEX 1.
1   IF sy-subrc = 0.
2     CALL FUNCTION 'BUP_PARTNER_GET'
3       EXPORTING
4         i_partner    = is_but100-partner
5         i_cp_exclude = gc_x
i_is_exclude = gc_x
PORTING
e_but000_int = ls_but000_int
CEPTIONS
OTHERS       = 1.
... Funktionsbausteine aufrufen -
T lt_tbz1f WHERE     ztpkt = 'RLDEL'
             AND NOT fname IS INITIAL.
Datümer alt = neu = SPACE => Löschung, sonst Update -
(Einschränkung der Gültigkeit)
FUNCTION lt_tbz1f-fname
PORTING
i_partner        = is_but100-partner
i_partnerguid    = ls_but000_int-partner_guid
i_role           = is_but100-rltyp
i_dfval          = is_but100-dfval
i_calltp         = iv_calltp
i_valid_from     = is_but100-valid_from_dats
i_valid_from_old = iv_valid_from_old
i_valid_to       = is_but100-valid_to_dats
i_valid_to_old   = iv_valid_to_old
PORTING
e_result         = lv_result.
... Ergebnis merken, wenn höher als bisheriges Zwischenergebnis-
v_result > gv_wu_result.                          "#EC PORTABLE
wuresult = lv_result.
F.
... Ergebnis ist 'Nicht löschen': Zeitpunkt abbrechen -

HI Mallik,
for termination action the operation that i've set is
lis9 0001
cop 0002
lis9 0007
cop 0008
lis9 0014
lis9 0015
lis9 0587
so just want to know if the set format for termination action is right
and other option is that if there is some change to settings of infotype charateristics in table v_t582A this may cause change in the date that is cause of error.
can u please suggest the above alignment of operations and infotype is right and provide me the idle settings for infotype characteristics which may solve my query.
thanks mallik.

At the time of RFQ creation dump error

Dear All,
                    At the time of RFQ creation one Dump error is coiming... please advise to solve this issue...
the error message is :
Runtime errors         SYNTAX_ERROR
       Occurred on     09.09.2009 at   12:10:27
Syntax error in program "SAPLV61A ".
What happened?
The following syntax error occurred in the program SAPLV61A :
"Incorrect logical expression: Instead of "X" a field, a function or "("
Error in ABAP application program.
The current ABAP program "SAPLMEVA" had to be terminated because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
What can you do?
Please eliminate the error by performing a syntax check
(or an extended program check) on the program "SAPLV61A ".
You can also perform the syntax check from the ABAP/4 Editor.
If the problem persists, proceed as follows:
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
Error analysis
The following syntax error was found in the program SAPLV61A :
"Incorrect logical expression: Instead of "X" a field, a function or "("
How to correct the error
Probably the only way to eliminate the error is to correct the program.
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
   To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
   To obtain this, call the system log with Transaction SM21
   and select the "Print" function to print out the relevant
   part.
3. If the programs are your own programs or modified SAP programs,
   supply the source code.
   To do this, you can either use the "PRINT" command in the editor or
   print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
   or which actions and input led to the error.
System environment
SAP Release.............. "620"
Application server....... "ARCHIVAL"
Network address.......... "172.26.2.145"
Operating system......... "Windows NT"
Release.................. "5.2"
Hardware type............ "4x Intel 80686"
Character length......... 8 Bits
Pointer length........... 32 Bits
Work process number...... 0
Short dump setting....... "full"
Database server.......... "ARCHIVAL"
Database type............ "MSSQL"
Database name............ "EDP"
Database owner........... "dbo"
Terminal................. "cheeid92corit"
Character set............ "English_United State"
SAP kernel............... "640"
Created on............... "Mar 9 2009 22:54:07"
Created in............... "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
Database version......... "SQL_Server_9.00 "
Patch level.............. "274"
Patch text............... " "
Supported environment....
Database................. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
SAP database version..... "640"
Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2,
Windows NT 6.0"
User, transaction...
Client.............. 777
User................ "MMCORE"
Language key........ "E"
Transaction......... "ME47 "
Program............. "SAPLMEVA"
Screen.............. "SAPMM06E 0311"
Screen line......... 54
Information on where terminated
The termination occurred in the ABAP program "SAPLMEVA" in
"ME_LOAD_VARIANTS_PRICING".
The main program was "SAPMM06E ".
The termination occurred in line 55 of the source code of the (Include)
program "LMEVAU08"
of the source code of program "LMEVAU08" (when calling the editor 550).
Source code extract
000250       ENDIF.
000260   *--> Initialisieren
000270   *--> not necessary anymore (Raimond Buchholz)
000280   *   CALL FUNCTION 'CUD0_CONFIGURATION_INITIALIZER'.
000290   *--> Preisteile der Varianten besorgen
000300       CALL FUNCTION 'CEI0_GET_CONDITIONS'
000310            EXPORTING
000320                 INSTANCE    = I_CUOBJ
000330                 APPLICATION = 'MM'
000340            TABLES
000350   *              CONDITIONS = T_VCKEY.                 "del 194053
000360                 CONDITIONS = T_VCKEY                   "ins 194053
000370            exceptions                                   "ins 194053
000380                 error_message = 01                     "ins 194053
000390                 others         = 02.                    "ins 194053
000400   *--> Preisteile der Varianten mit Belegnummer versorgen
000410       LOOP AT T_VCKEY.
000420         T_VCKEY-KAPPL = 'M '.
000430         T_VCKEY-VBELN = I_EBELN.
000440         T_VCKEY-POSNR = I_EBELP.
000450         MODIFY T_VCKEY.
000460       ENDLOOP.
000470     ENDIF.
000480
000490   *--> Preisteile der Varianten an Preisfindung übergeben
000500   *- pricing_load_variant_key muß auch bei Positionen ohne Konfiguration
000510   *- laufen, da die Logik im PRICING zu 4.0 umgestellt wurde
000520     IF I_NO_LOAD IS INITIAL.
000530       DATA: I_POSNR LIKE VBAP-POSNR.
000540       I_POSNR = I_EBELP.
      CALL FUNCTION 'PRICING_LOAD_VARIANT_KEYS'
000560            EXPORTING
000570                 APPLICATION = 'M '
000580                 VBELN       = I_EBELN
000590                 POSNR       = I_POSNR
000600            TABLES
000610                 TVCKEY      = T_VCKEY
000620            EXCEPTIONS
000630                 OTHERS      = 1.
000640     ENDIF.
000650
000660   ENDFUNCTION.
Contents of system fields
SY field contents..................... SY field contents.....................
SY-SUBRC 0                             SY-INDEX 0
SY-TABIX 1                             SY-DBCNT 1
SY-FDPOS 1                             SY-LSIND 0
SY-PAGNO 0                             SY-LINNO 1
SY-COLNO 1                             SY-PFKEY GVP
SY-UCOMM
SY-TITLE Maintain Quotation : Item 00001
SY-MSGTY E                             SY-MSGID AIPLOC
SY-MSGNO 002                           SY-MSGV1 303632
SY-MSGV2                               SY-MSGV3
SY-MSGV4
Kind regards
P.Anandhakumar

Hi Anandhakumar,
Debugg the transaction with help of ABAPER.
System will show you the reason for the above error.
Hope this should solve your problem.
Thanks and regards
Gitesh

Dump Error in Z table

Similar Messages

Maybe you are looking for