Dump error of t.codes MR51(top urgent)
hello,
please help me, i am having the problem of findout the error of dump.
t.codes is MR51 while execute getting the error of dump, how to find out the error, i can tried ST22 there also i couldnot understand the error, please let me know the procedure to find out the error in step by step plese.
thanks
suja
in ST22... firts check <b>Short text</b>
if you can get some idea out of it then good..
if still error is not clear check <b>What happened?</b>
check the source code extract in order to see where exactly you are getting dump...
at the time of MR51 execution when you get dump... click on debugger.. there you can check if desired values are getting passed...
Similar Messages
-
hello,
I am getting the dump error of t.codes MR51, kindly let me know the errors and how to solve the same and oblige.
thanks
sujathaFinding the Invoice Number - URGENT
Subcontracting
posting date line items
Posting of Price change document on release of Cost estimate.
help me in functional
Inventory Management - transactions
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/25c1f5d1-0901-0010-d495-e96d02a0cb01
Please reward points if helpful. -
Dump error in smartforms , please help me urgent
Hi,
i have created a smartform with two pages in it , i was not able to create the window in the second page it was showing me a dump error but i manage to copy the main window of first page in to second page it was working fine but if i delete anything in it , it was reflecting in first page , then i managed to reduce the size of the main window and add a secondayry window , as the content of the second page must flow to pages . i need to create a main window , it is aagin throwing a dump error , plsease help me in sloving in this , thanks
sriharHi,
create folder in main area in main wondow and keep all the rows of table in folder.
the go to output options of folder and tick check box Page protection.
Now u can reduce the size of main window in second page .it will not get any short dump.
regards,
Sunil.K -
Dump error while going for a change mode in MIR4 for parked document
Hi All,
After doing some GR and MIRO for one PO, there was some GR qty was left and I have parked new invoice document in MIRA. If I go for change mode MIR4 for the same parked document it is going to dump error as message type unknown, saying entry is not maintained table TTXD for Tax procedure. This table indicates that Tax jurisdiction, but we are not maintaining the Tax at Jurisdiction level. I found that user has activated calculate tax in MIRA and posted with some amount, here system will not calculate the tax in Tax field because base amount is not there to calculate, so that field shows "zero". For the same parked document in MIR4 I can see some lines which has value 0 in amount & quantity(already cleared GR's for the same PO) and also GR lines.
Can anyone tell me how can I solve this dump error, I want to delete the parked document in legal way.
Regards
ShanuHi Shanu,
Please extract complete dump error by T code ST22 and take a help of your ABAP Team for an analyse the possible cause of dump and also check the relevant note for resolving this dump error.
Regards,
Santosh -
Dump error while creating a new page in smartforms URGENT pls!!!
while creating a new page it is showing me a dump error , that the superior program execption was not intercepted , i have even given the next page field also correctly, i have attached a mainwindow to that page and a text element to that . .
thanks
sridharHi Deena,
This error:
"[2012-07-10T14:50:30.005+05:30] [wls_ods1] [ERROR] [] [oracle.adfinternal.view.faces.config.rich.RegistrationConfigurator] [tid: [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 0000JXkC9dU3FClqwsJb6G1FyhO000003D,0] [APP: odsm#11.1.1.2.0] Server Exception during PPR, #7[[
javax.servlet.ServletException: Could not initialize class com.octetstring.vde.admin.services.client.VDEAdminServiceSoapBindingStub"
is known issue
Go to metalink, article: Unable To Connect To OVD 11g Webinterface Using ODSM. [ID 1282757.1]
You need to apply that patch.
I hope this helps,
Thiago Leoncio. -
URGENT: Please Help (error in flash code)
I have a major deadline tomorrow and a problem has arisen. If anyone can take a look at my file and help me it would be greatly appreciated
I was converting artwork to components and assigning interactions. When I went to run the project, it gave me the following error: "Flash Catalyst cannot run the project because of an error in the code. To find the error, switch to the code workspace and look in the Problems Panel."
The error message read, specifically, "identifier 'group6' used more than once."
I wasn't confident enough to start tweaking the code, so I just deleted the interactions and converted the components back to artwork hoping to reverse the problem.
It didn't work.
Unfortunately, I was saving more often than I was "compiling" because FC has been crashing on me with this particular file. As a result, I was saving a file that wouldn't compile and can no longer go back.
HELP! I WILL EMAIL YOU MY FILE!
I think I figured out the problem. I opened up an older file and began the painful process of recreating my work. I reverted a component called "Option Button" to artwork and when I compiled, I got the same error: "identifier 'group6' used more than once" and "identifier 'group7' used more than once." Is this happening when I convert a component back to artwork and it makes mistakes identifying/naming its parts??
I tried reconverting the artwork to a component, thinking that might solve the problem, but it didn't...Hi Sponce,
This is a bug in FC: FC has assigned two different objects to be called "group6". Please email me the file so I can make sure we have this bug filed. To work around it, you just need to figure out which objects have the ID "group6" and delete one of them. This is pretty straightforward: in the problems panel, the errors will have a line #. Find that line # in the file - that tells you where the error is in the code. Now you need to figure out which object that is. You might be able to do this by looking at what it has inside it: if it's a tags inside it, well, then, it's the group with 3 rects. Otherwise, you can do it by position in the file: the code is in reverse z-order, so the last thing in the code is the topmost thing in the layers panel.
-Adam -
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 -
Error FF753 Tax code 01 not appear in any G/L account item with FM Active
Hi
We have fund management configured for one of the company code, while creating billing document through VF01/VF02 we are getting the Error FF753 Tax code 01 not appear in any G/L account item.
This error however does not appear when posting directly from FI with the same tax code.
I have tried to change the message control in which case i am getting a dump pointing to PSM-FM.
Please advise.
Regards
SandeepHi:
If you could please refer to the contents of OSS Note 112609 - How are tax codes transferred to conditions ?
"Symptom
If a billing document is transferred to accounting the system displays error messages. Transferring tax codes from tax conditions into the pricing conditions and discounts does not function as expected.
Other terms
FF805, FF747, FF753, MWSKZ, MWSK1, tax code
Reason and Prerequisites
The tax condition in the SD pricing procedure contains incorrect reference steps, there are several tax conditions in the pricing procedure of which the tax codes overwrite each other or a program error exists.
Solution
In the accounting document for a billing document, the different G/L account line items are provided with a tax code. The tax code of the G/L accounts is transferred from the tax condition(s) of the billing document. How are the tax codes of the tax conditions transferred into the other conditions of a billing document ?
Basically:
The conditions of a billing document are read from top to bottom. As soon as an active tax (inactive = ' ') is read, the system transfers the tax code of this tax into the non-tax conditions as follows:
1. The reference steps (From-step, To-step) are read (the reference steps are defined in the pricing procedure).
2. The tax code is transferred into all conditions, for which
the step number of the condition lies in the pricing procedure between "From-step" and "To-step",
the condition is not inactive (exactly: the inactive flag is not equal to A (Condition exclusion), M (Inactive due to manual entry), or X (Incorrect)),
the condition is not statistical (if it is no invoice list condition),
the condition is no tax condition.
After the transfer of the tax code the system searches for the next active tax. If further taxes are found, their tax code is again transferred according to the above procedure. If the reference steps of different taxes overlap, tax codes that have already been transferred are overwritten. To all non-tax conditions which in the pricing procedure stand after the last tax condition the tax code of the last active tax condition is transferred if they are not statistical.
Special features:
1. If the "From-step" of a tax condition refers to a subtotal of the pricing procedure, the tax code of the tax is not only transferred into the conditions with step number between From-step and To-step but into all non-tax conditions for which
the step number of the condition in the pricing procedure is lower than the "To-step" of the tax condition.
the condition is not statistical (if it is no invoice list condition).
the condition is not a tax condition.
2. If the "To-step" of the tax condition is smaller than the "From-step", then the system sets "To-step = From-step".
Notes:
1. As of Release 4.0 the tax code is no longer transferred in pricing but only when the billing document is released to accounting.
2. If you use several taxes and tax codes and Customizing is incorrect for the release of billing documents to accounting, among others the system may display error message FF747.
3. If there are several taxes in the pricing procedure refer to Notes 72173 and 82091 for Releases 3.0D - 3.1G. For Release 3.1H, only note 82091 is relevant.
4. For conditions which are transferred into accounting (thus not statistical, not inactive conditions) and do not contain a tax code, the system searches for a default tax code which in Accounting Customizing can be set depending on the company code (tax code for non-taxable transactions). This applies to releases up to and including Release 4.5B. For Release 4.6, refer to Note 385127."
Regards -
Hi Frds
While running my program in DEV,the output is coming perfectly .
But transporting the same program to QA and running im getting Dump Error .In our QA we 1 lakhs Records.
How to solve the problem ,i given the coding below .
Pls Correct my mistake and give some tips.
TYPE-POOLS:SLIS.
TABLES : EKPO,MARC,EBAN,MSEG,MARD,MARA,MAKT,MLGN.
DATA:BODY TYPE SLIS_T_FIELDCAT_ALV,
HEADER TYPE SLIS_FIELDCAT_ALV,
GD_LAYOUT TYPE SLIS_LAYOUT_ALV,
GD_REPID LIKE SY-REPID.
DATA : PO TYPE I,
TGR TYPE I.
CHECK TYPE I.
TGR = 0.
*CHECK = 0.
DATA : MATNR LIKE MARA-MATNR,
WERKS LIKE MARD-WERKS,
LGORT LIKE MARD-LGORT,
BUKRS LIKE EKPO-BUKRS.
DATA : BEGIN OF ITAB OCCURS 0,
MATNR LIKE MARA-MATNR,
MEINS LIKE MARA-MEINS,
MAKTX LIKE MAKT-MAKTX,
MINBE LIKE MARC-MINBE,
LGNUM LIKE MLGN-LGNUM,
LGORT LIKE MARD-LGORT,
EBELN LIKE EKPO-EBELN,
EBELP LIKE EKPO-EBELP,
MENGE LIKE EKPO-MENGE,
MENG1 LIKE MSEG-MENGE,
DQT LIKE MSEG-MENGE,
BANFN LIKE EBAN-BANFN,
MENG2 LIKE EBAN-MENGE,
END OF ITAB.
DATA : BEGIN OF IMAT OCCURS 0,
MATNR LIKE MARA-MATNR,
MEINS LIKE MARA-MEINS,
MAKTX LIKE MAKT-MAKTX,
MINBE LIKE MARC-MINBE,
WERKS LIKE MARD-WERKS,
LGORT LIKE MARD-LGORT,
END OF IMAT.
DATA : BEGIN OF IEKPO OCCURS 0,
EBELN LIKE EKPO-EBELN,
EBELP LIKE EKPO-EBELP,
MENGE LIKE EKPO-MENGE,
BUKRS LIKE EKPO-BUKRS,
MATNR LIKE EKPO-MATNR,
LOEKZ LIKE EKPO-LOEKZ,
WERKS LIKE EKPO-WERKS,
LGORT LIKE EKPO-LGORT,
END OF IEKPO.
DATA : BEGIN OF IMSEG OCCURS 0,
EBELN LIKE MSEG-EBELN,
EBELP LIKE MSEG-EBELP,
MENGE LIKE MSEG-MENGE,
MATNR LIKE MSEG-MATNR,
LGNUM LIKE MSEG-LGNUM,
BWART LIKE MSEG-BWART,
END OF IMSEG.
DATA : BEGIN OF IMLGN OCCURS 0,
MATNR LIKE MLGN-MATNR,
LGNUM LIKE MLGN-LGNUM,
END OF IMLGN.
DATA : BEGIN OF IEBAN OCCURS 0,
BANFN LIKE EBAN-BANFN,
STATU LIKE EBAN-STATU,
MATNR LIKE EBAN-MATNR,
MENGE LIKE EBAN-MENGE,
WERKS LIKE EBAN-WERKS,
LGORT LIKE EBAN-LGORT,
BADAT LIKE EBAN-BADAT,
LOEKZ LIKE EBAN-LOEKZ,
END OF IEBAN.
SELECTION-SCREEN: BEGIN OF BLOCK 01.
SELECTION-SCREEN: BEGIN OF BLOCK 02 WITH FRAME TITLE TEXT-001.
SELECT-OPTIONS MATERIAL FOR MATNR.
SELECT-OPTIONS COMPANY FOR BUKRS .
SELECT-OPTIONS PLANT FOR WERKS OBLIGATORY.
SELECT-OPTIONS STORAGE FOR LGORT OBLIGATORY.
SELECTION-SCREEN: END OF BLOCK 02.
SELECTION-SCREEN: END OF BLOCK 01.
AT SELECTION-SCREEN.
PERFORM MATERIAL. "GET MATERIAL
START-OF-SELECTION.
PERFORM POS. "GET POS
SORT IEKPO BY EBELN EBELP.
PERFORM GRS. "GET GR QTY
PERFORM PRS. "GET OPEN PR NUMBER
PERFORM READ.
PERFORM FIELDCATALOG.
PERFORM BUILD_LAYOUT.
GET ALV DISPLAY
PERFORM ALVDISPLAY.
*& FORM MATERIAL
TEXT
FORM MATERIAL.
SELECT MARAMATNR MARAMEINS
MAKT~MAKTX
MARC~MINBE
MARDWERKS MARDLGORT
INTO CORRESPONDING FIELDS OF TABLE IMAT
FROM MARA INNER JOIN MAKT ON MAKTMATNR = MARAMATNR
INNER JOIN MARC ON MARCMATNR = MARAMATNR
INNER JOIN MARD ON MARDMATNR = MARAMATNR
WHERE MARA~MATNR IN MATERIAL AND
MARD~WERKS IN PLANT AND
MARD~LGORT IN STORAGE.
IF SY-SUBRC <> 0.
MESSAGE 'NO DATA FOUND FOR THE SELECTION ' TYPE 'E'.
EXIT.
ENDIF.
ENDFORM. "MATERIAL
*& FORM POS
TEXT
FORM POS.
LOOP AT IMAT.
SELECT EBELN EBELP MENGE BUKRS MATNR LOEKZ WERKS LGORT
FROM ekpo APPENDING TABLE iekpo
WHERE MATNR = IMAT-MATNR AND
WERKS = IMAT-WERKS AND
LGORT = IMAT-LGORT AND
LOEKZ EQ SPACE.
ENDLOOP.
CLEAR : IMAT, IEKPO.
ENDFORM. "POS
*& FORM GRS
TEXT
FORM GRS.
LOOP AT IEKPO.
SELECT EBELN EBELP MENGE MATNR LGNUM BWART FROM MSEG APPENDING TABLE
IMSEG WHERE EBELN = IEKPO-EBELN AND
EBELP = IEKPO-EBELP AND
MATNR = IEKPO-MATNR AND
( BWART = '101' OR BWART = '105' ).
ENDLOOP.
ENDFORM. "GRS
*& FORM PRS
TEXT
FORM PRS.
LOOP AT IMAT.
SELECT BANFN STATU MATNR MENGE WERKS LGORT BADAT LOEKZ FROM EBAN
APPENDING TABLE IEBAN
WHERE MATNR = IMAT-MATNR AND
STATU EQ 'N' AND
LOEKZ EQ SPACE AND
WERKS IN PLANT AND
LGORT IN STORAGE.
ENDLOOP.
ENDFORM. "PRS
*& FORM READ
TEXT
FORM READ.
LOOP AT IMAT. " MAIN LOOP
ITAB-MATNR = IMAT-MATNR.
ITAB-MEINS = IMAT-MEINS.
ITAB-MAKTX = IMAT-MAKTX.
ITAB-MINBE = IMAT-MINBE.
ITAB-LGORT = IMAT-LGORT.
READ TABLE IMSEG WITH KEY MATNR = IMAT-MATNR.
ITAB-LGNUM = IMSEG-LGNUM.
PO & GR *************************
CHECK = 0.
LOOP AT IEKPO WHERE MATNR = IMAT-MATNR. " INNER LOOP
CHECK = 1.
ITAB-EBELN = IEKPO-EBELN.
ITAB-EBELP = IEKPO-EBELP.
ITAB-MENGE = IEKPO-MENGE.
LOOP AT IMSEG WHERE EBELN = IEKPO-EBELN AND EBELP = IEKPO-EBELP.
" INNER INNER LOOP.
TGR = TGR + IMSEG-MENGE.
ENDLOOP.
ITAB-DQT = IEKPO-MENGE - TGR.
IF ITAB-DQT > 0.
APPEND : ITAB.
CLEAR : ITAB-EBELN,ITAB-EBELP,IEKPO-MENGE,TGR,ITAB-DQT.
ENDIF.
CLEAR : ITAB-EBELN,ITAB-EBELP,IEKPO-MENGE,TGR,ITAB-DQT.
ENDLOOP.
CLEAR : ITAB-EBELN,ITAB-EBELP,IEKPO-MENGE,TGR,ITAB-DQT.
PR ********************
LOOP AT IEBAN WHERE MATNR = IMAT-MATNR.
CHECK = 1.
ITAB-BANFN = IEBAN-BANFN.
ITAB-MENG2 = IEBAN-MENGE.
APPEND ITAB.
CLEAR : ITAB-BANFN ,ITAB-MENG2.
ENDLOOP.
IF CHECK = 0.
APPEND ITAB.
ELSEIF check = 1.
ENDIF.
CLEAR : IEKPO,ITAB-EBELN,ITAB-EBELP,ITAB-MENGE,ITAB-DQT.
ENDLOOP.
CLEAR : ITAB,IEKPO,IMAT,IMLGN.
ENDFORM. "READ
*& FORM BUILD_LAYOUT
TEXT
FORM BUILD_LAYOUT.
GD_LAYOUT-NO_INPUT = 'X'.
GD_LAYOUT-COLWIDTH_OPTIMIZE = 'X'.
ENDFORM. " BUILD_LAYOUT
*& FORM FIELDCATALOG
TEXT
FORM FIELDCATALOG .
HEADER-COL_POS = '1'.
HEADER-SELTEXT_L = 'MATERIAL CODE'.
HEADER-TABNAME = 'ITAB'.
HEADER-FIELDNAME = 'MATNR'.
APPEND HEADER TO BODY.
CLEAR HEADER.
HEADER-COL_POS = '2'.
HEADER-SELTEXT_L = 'MATERIAL DESC'.
HEADER-TABNAME = 'ITAB'.
HEADER-FIELDNAME = 'MAKTX'.
APPEND HEADER TO BODY.
CLEAR HEADER.
HEADER-COL_POS = '3'.
HEADER-SELTEXT_L = 'UOM'.
HEADER-TABNAME = 'ITAB'.
HEADER-FIELDNAME = 'MEINS'.
APPEND HEADER TO BODY.
CLEAR HEADER.
HEADER-COL_POS = '4'.
HEADER-SELTEXT_L = 'ROL'.
HEADER-TABNAME = 'ITAB'.
HEADER-FIELDNAME = 'MINBE'.
APPEND HEADER TO BODY.
CLEAR HEADER.
HEADER-COL_POS = '5'.
HEADER-SELTEXT_L = 'STORAGE'.
HEADER-TABNAME = 'ITAB'.
HEADER-FIELDNAME = 'LGORT'.
APPEND HEADER TO BODY.
CLEAR HEADER.
HEADER-COL_POS = '6'.
HEADER-SELTEXT_L = 'WAREHOUSE'.
HEADER-TABNAME = 'ITAB'.
HEADER-FIELDNAME = 'LGNUM'.
APPEND HEADER TO BODY.
CLEAR HEADER.
HEADER-COL_POS = '7'.
HEADER-SELTEXT_L = 'PO NUMBER'.
HEADER-TABNAME = 'ITAB'.
HEADER-FIELDNAME = 'EBELN'.
APPEND HEADER TO BODY.
CLEAR HEADER.
HEADER-COL_POS = '8'.
HEADER-SELTEXT_L = 'PO LINE#'.
HEADER-TABNAME = 'ITAB'.
HEADER-FIELDNAME = 'EBELP'.
APPEND HEADER TO BODY.
CLEAR HEADER.
HEADER-COL_POS = '9'.
HEADER-SELTEXT_L = 'PO QUANTITY'.
HEADER-TABNAME = 'ITAB'.
HEADER-FIELDNAME = 'DQT'.
APPEND HEADER TO BODY.
CLEAR HEADER.
HEADER-COL_POS = '10'.
HEADER-SELTEXT_L = 'PR NUMBER'.
HEADER-TABNAME = 'ITAB'.
HEADER-FIELDNAME = 'BANFN'.
APPEND HEADER TO BODY.
CLEAR HEADER.
HEADER-COL_POS = '11'.
HEADER-SELTEXT_L = 'PR QUANTITY'.
HEADER-TABNAME = 'ITAB'.
HEADER-FIELDNAME = 'MENG2'.
APPEND HEADER TO BODY.
CLEAR HEADER.
ENDFORM. " FIELDCATALOG
*& FORM ALVDISPLAY
TEXT
FORM ALVDISPLAY.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
I_CALLBACK_PROGRAM = 'Z_R_CONSUMABLEROL1'
I_CALLBACK_TOP_OF_PAGE = 'TOP-OF-PAGE' "SEE FORM
I_CALLBACK_USER_COMMAND = 'USER_COMMAND'
I_GRID_TITLE = OUTTEXT
IS_LAYOUT = GD_LAYOUT
IT_FIELDCAT = BODY
IT_SPECIAL_GROUPS = GD_TABGROUP
IT_EVENTS = GT_XEVENTS
I_SAVE = 'X'
IS_VARIANT = Z_TEMPLATE
TABLES
T_OUTTAB = ITAB
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. "ALVDISPLAYENDLOOP.
Thanks
PariHi Hari,
I have a preference for one of the work-arounds. No conversion should be necessary. The reason for being so careful is that table conversion (t/code SE14) is bypassing the SAP BW application layer. Normally you create your data model (incl. InfoObjects) in BW and during activation BW requests the ABAP layer to create/change/delete the ABAP Data Dictionary objects. If something goes wrong or needs conversion using ABAP tools, it might lead to unexpected issues/inconsistencies in the future.
One issue I faced was that space occupation of an InfoCube was disrupted. It is too long ago to remember the details and it occurred in an SAP BW 2.0B system.
Anyway, if you read SAP Note 579342 - Changing key figures that are used in InfoProviders it should be possible to go ahead with your approach. Table conversion will have to place in every target system, Please note that according to SAP Note 1248769 - Inconsistency between database and ABAP Dictionary table conversion should be done using user-id DDIC.
Best regards,
Sander -
Dump Error in MAterial Consumption Report
Hi all Gurus
[1] I need help from your side i am doing one material consumption report in that i did all thing but it is giving me dump error while i was using sort in to ALV
so please any one help me out this .......
[2] I am Printing sum of quantity in Header area of smartform it is printing with using comma e.x 43,000 but in body area it is showing with decimal point
e.x 43.000
Following is my ALV reports code please check it it is giving me short dump while using sort ..............
I am very much in neeed
Thanx for your suggestion in advanc.....
and god bless you............
*& Report ZCONSUM
REPORT ZCONSUM.
*& Report ZCONSUMPTION
TYPE-POOLS : SLIS.
TABLES:marc,
mara,
makt,
mard,
mbew,
mseg,
mkpf.
TYPES:
BEGIN OF s_mseg,
mblnr LIKE mseg-mblnr,
mjahr LIKE mseg-mjahr,
zeile LIKE mseg-zeile,
bwart LIKE mseg-bwart,
matnr LIKE mseg-matnr,
werks LIKE mseg-werks,
menge LIKE mseg-menge,
budat LIKE mkpf-budat,
mtart LIKE mara-matnr,
matkl LIKE mara-matkl,
END OF s_mseg,
BEGIN OF s_t001w,
werks LIKE t001w-werks,
name1 LIKE t001w-name1,
END OF s_t001w,
BEGIN OF s_mara,
matnr LIKE mara-matnr,
mtart LIKE mara-mtart,
matkl LIKE mara-matkl,
END OF s_mara,
BEGIN OF s_makt,
matnr LIKE makt-matnr,
spras LIKE makt-spras,
maktx LIKE makt-maktx,
END OF s_makt,
BEGIN OF s_calc,
matnr LIKE mara-matnr,
mtart LIKE mara-mtart,
matkl LIKE mara-matkl,
maktx LIKE makt-maktx,
menge_t LIKE mseg-menge,
menge_t1 LIKE mseg-menge,
menge_con_261 LIKE mseg-menge,
menge_con_262 LIKE mseg-menge,
menge_con1_261 LIKE mseg-menge,
menge_con1_262 LIKE mseg-menge,
menge_ret_291 LIKE mseg-menge,
menge_ret1_291 LIKE mseg-menge,
menge_ret_292 LIKE mseg-menge,
menge_ret1_292 LIKE mseg-menge,
menge_unit_301 LIKE mseg-menge,
menge_unit1_301 LIKE mseg-menge,
menge_unit_302 LIKE mseg-menge,
menge_unit1_302 LIKE mseg-menge,
menge_sub LIKE mseg-menge,
menge_sub1 LIKE mseg-menge,
menge_oth LIKE mseg-menge,
menge_oth1 LIKE mseg-menge,
END OF s_calc,
BEGIN OF s_data,
matnr LIKE mara-matnr,
matkl LIKE mara-matkl,
mtart LIKE mara-mtart,
maktx LIKE makt-maktx,
menge_t LIKE mseg-menge,
menge_t1 LIKE mseg-menge,
menge_con LIKE mseg-menge,
menge_con1 LIKE mseg-menge,
menge_ret LIKE mseg-menge,
menge_ret1 LIKE mseg-menge,
menge_unit LIKE mseg-menge,
menge_unit1 LIKE mseg-menge,
menge_sub LIKE mseg-menge,
menge_sub1 LIKE mseg-menge,
menge_oth LIKE mseg-menge,
menge_oth1 LIKE mseg-menge,
END OF s_data.
DATA: w_mseg TYPE s_mseg,
i_mseg TYPE s_mseg OCCURS 0,
w_t001w TYPE s_t001w,
i_t001w TYPE s_t001w OCCURS 0,
w_mara TYPE s_mara,
i_mara TYPE s_mara OCCURS 0,
w_makt TYPE s_makt,
i_makt TYPE s_makt OCCURS 0,
w_calc TYPE s_calc,
i_calc TYPE s_calc OCCURS 0,
w_data TYPE s_data,
i_data TYPE s_data OCCURS 0.
DATA: line_cnt TYPE i,
v_temp TYPE p DECIMALS 2.
ALV DATA DECLERATION
DATA : IT_FIELD TYPE SLIS_T_FIELDCAT_ALV,
WA_FIELD TYPE SLIS_FIELDCAT_ALV.
DATA : IT_LAYOUT TYPE SLIS_LAYOUT_ALV.
IT_LAYOUT-ZEBRA = 'X'.
IT_LAYOUT-TOTALS_TEXT = 'Grand Total'.
IT_LAYOUT-SUBTOTALS_TEXT = 'Sub Total'.
IT_LAYOUT-INFO_FIELDNAME = 'LINE_COLOR'.
DATA: WA_COMMENTRY TYPE SLIS_LISTHEADER.
DATA: IT_COMMENTRY TYPE SLIS_T_LISTHEADER.
DATA: WA_COMMENTRY1 TYPE SLIS_LISTHEADER.
DATA: IT_COMMENTRY1 TYPE SLIS_T_LISTHEADER.
DATA: WA_EVENT TYPE SLIS_ALV_EVENT.
DATA: IT_EVENT TYPE SLIS_T_EVENT.
WA_EVENT-NAME = 'TOP_OF_PAGE'.
WA_EVENT-FORM = 'TOP'.
APPEND WA_EVENT TO IT_EVENT.
DATA : WA_SORT TYPE slis_sortinfo_alv,
IT_SORT TYPE SLIS_T_SORTINFO_ALV.
CLEAR WA_SORT.
WA_SORT-SPOS = '1'.
WA_SORT-FIELDNAME = 'MATKL'.
WA_SORT-TABNAME = 'I_DATA'.
WA_SORT-SUBTOT = 'X'.
APPEND WA_SORT TO IT_SORT.
CLEAR WA_SORT.
WA_SORT-SPOS = '2'.
WA_SORT-FIELDNAME = 'MTART'.
WA_SORT-TABNAME = 'I_DATA'.
WA_SORT-SUBTOT = 'X'.
APPEND WA_SORT TO IT_SORT.
DEFINE MAC1.
WA_FIELD-TABNAME = 'I_DATA'.
WA_FIELD-FIELDNAME = &1.
WA_FIELD-COL_POS = &2.
WA_FIELD-SELTEXT_L =&3.
WA_FIELD-DO_SUM = &4.
APPEND WA_FIELD TO IT_FIELD.
END-OF-DEFINITION.
MAC1 'MATKL' '1' 'MATERIAL GROUP' 'X'.
MAC1 'MTART' '2' 'MATERIAL TYPE' 'X'.
MAC1 'MATNR' '3' 'MATERIAL NO' 'X'.
MAC1 'MAKTX' '4' 'DESCRIPTION' 'X'.
MAC1 'MENGE_CON1' '5' 'CONSUMPTION FOR PERIOD' 'X'.
MAC1 'MENGE_CON' '6' 'CONSUMPTION FOR CUMULATIVE' 'X'.
MAC1 'MENGE_RET1' '7' 'RETURN FROM DEPT. FOR PERIOD' 'X'.
MAC1 'MENGE_RET' '8' 'RETURN FROM DEPT.CUMULATIVE' 'X'.
MAC1 'MENGE_UNIT1' '9' 'INTER UNIT FOR PERIOD' 'X'.
MAC1 'MENGE_UNIT' '10' 'INTER UNIT CUMULATIVE' 'X'.
MAC1 'MENGE_SUB1' '11' 'SUB CONTRACTOR FOR PERIOD' 'X'.
MAC1 'MENGE_SUB' '12' 'SUB CONTRACTOR CUMULATIVE' 'X'.
MAC1 'MENGE_OTH1' '13' 'OTHERS FOR PERIOD' 'X'.
MAC1 'MENGE_OTH' '14' 'OTHERS CUMULATIVE' 'X'.
MAC1 'MENGE_t1' '15' 'TOTAL FOR PERIOD' 'X'.
MAC1 'MENGE_t' '16' 'TOTAL CUMULATIVE' 'X'.
SELECTION-SCREEN: BEGIN OF BLOCK B1 WITH FRAME TITLE text-001.
PARAMETERS: p_werks LIKE t001w-werks DEFAULT '1023' OBLIGATORY.
select-options: s_matkl FOR mara-matkl,
s_mtart FOR mara-mtart,
s_matnr FOR mara-matnr,
s_budat FOR mkpf-budat OBLIGATORY.
PARAMETERS: year(4) DEFAULT '2007'.
SELECTION-SCREEN:END OF BLOCK B1.
START-OF-SELECTION.
SELECT lk~mblnr
lk~mjahr
lk~budat
lp~zeile
lp~bwart
lp~matnr
lp~werks
lp~menge
ma~mtart
ma~matkl
INTO CORRESPONDING FIELDs OF TABLE i_mseg
FROM MSEG AS lp INNER JOIN MKPF AS lk
ON lkmblnr EQ lpmblnr
AND lkmjahr EQ lkmjahr
INNER JOIN mara AS ma
ON mamatnr EQ lpmatnr
WHERE lp~werks EQ p_werks
AND lp~matnr IN s_matnr
AND lk~budat LE s_budat-high.
clear line_cnt. "Count line of i_table i_mseg
DESCRIBE TABLE i_mseg LINES line_cnt.
IF line_cnt GT 0. "If i_mseg has records
SELECT matnr "Collect material description
maktx
spras
INTO CORRESPONDING FIELDS OF TABLE i_makt
FROM makt
FOR ALL ENTRIES IN i_mseg
WHERE matnr EQ i_mseg-matnr
AND spras EQ 'E'.
CLEAR line_cnt.
DESCRIBE TABLE i_makt LINES line_cnt.
IF line_cnt GT 0.
SORT i_makt BY MATNR ASCENDING.
DELETE ADJACENT DUPLICATES FROM i_makt COMPARING matnr.
ENDIF.
SELECT werks "Collect plant name
name1
INTO CORRESPONDING FIELDS OF TABLE i_t001w
FROM t001w
FOR ALL ENTRIES IN i_mseg
WHERE werks EQ i_mseg-werks.
CLEAR line_cnt.
DESCRIBE TABLE i_t001w LINES line_cnt.
IF line_cnt GT 0.
SORT i_t001w BY werks ASCENDING.
DELETE ADJACENT DUPLICATES FROM i_t001w COMPARING werks.
ENDIF.
LOOP AT i_mseg INTO w_mseg. "Move recored into data i_tab
w_calc-matnr = w_mseg-matnr.
w_calc-mtart = w_mseg-mtart.
w_calc-matkl = w_mseg-matkl.
READ TABLE i_makt WITH KEY matnr = w_mseg-matnr INTO w_makt.
IF sy-subrc = 0.
w_calc-maktx = w_makt-maktx.
ENDIF.
IF w_mseg-bwart EQ '261' .
w_calc-menge_con_261 = w_mseg-menge.
IF w_mseg-budat GE s_budat-low.
w_calc-menge_con1_261 = w_mseg-menge.
ENDIF.
ENDIF.
IF w_mseg-bwart EQ '262' .
w_calc-menge_con_262 = w_mseg-menge.
IF w_mseg-budat GE s_budat-low.
w_calc-menge_con1_262 = w_mseg-menge.
ENDIF.
ENDIF.
IF w_mseg-bwart EQ '291' OR w_mseg-bwart EQ '201'.
w_calc-menge_ret_291 = w_mseg-menge.
IF w_mseg-budat GE s_budat-low.
w_calc-menge_ret1_291 = w_mseg-menge.
ENDIF.
ENDIF.
IF w_mseg-bwart EQ '292' OR w_mseg-bwart EQ '202'.
w_calc-menge_ret_292 = w_mseg-menge.
IF w_mseg-budat GE s_budat-low.
w_calc-menge_ret1_292 = w_mseg-menge.
ENDIF.
ENDIF.
IF w_mseg-bwart EQ '301'.
w_calc-menge_unit_301 = w_mseg-menge.
IF w_mseg-budat GE s_budat-low.
w_calc-menge_unit1_301 = w_mseg-menge.
ENDIF.
ENDIF.
IF w_mseg-bwart EQ '302'.
w_calc-menge_unit_302 = w_mseg-menge.
IF w_mseg-budat GE s_budat-low.
w_calc-menge_unit1_302 = w_mseg-menge.
ENDIF.
ENDIF.
IF w_mseg-bwart EQ '543'.
w_calc-menge_sub = w_mseg-menge.
IF w_mseg-budat GE s_budat-low.
w_calc-menge_sub1 = w_mseg-menge.
ENDIF.
ENDIF.
COLLECT w_calc INTO i_calc.
ENDLOOP. "ENDLOOP of Move recored into data i_tab
LOOP AT i_calc INTO w_calc.
w_data-matnr = w_calc-matnr.
w_data-mtart = w_calc-mtart.
w_data-matkl = w_calc-matkl.
w_data-maktx = w_calc-maktx.
v_temp = w_calc-menge_con_261 - w_calc-menge_con_262.
w_data-menge_con = v_temp.
CLEAR v_temp.
v_temp = w_calc-menge_con1_261 - w_calc-menge_con1_262.
w_data-menge_con1 = v_temp.
CLEAR v_temp.
v_temp = w_calc-menge_ret_291 - w_calc-menge_ret_292.
w_data-menge_ret = v_temp.
CLEAR v_temp.
v_temp = w_calc-menge_ret1_291 - w_calc-menge_ret1_292.
w_data-menge_ret1 = v_temp.
CLEAR v_temp.
v_temp = w_calc-menge_unit_301 - w_calc-menge_unit_302.
w_data-menge_unit = v_temp.
CLEAR v_temp.
v_temp = w_calc-menge_unit1_301 - w_calc-menge_unit1_302.
w_data-menge_unit1 = v_temp.
CLEAR v_temp.
w_data-menge_sub = w_calc-menge_sub.
w_data-menge_sub1 = w_calc-menge_sub.
v_temp = w_data-menge_con + w_data-menge_ret + w_data-menge_unit + w_data-menge_sub.
w_data-menge_t = v_temp.
CLEAR v_temp.
v_temp = w_data-menge_con1 + w_data-menge_ret1 + w_data-menge_unit1 + w_data-menge_sub1.
w_data-menge_t1 = v_temp.
CLEAR v_temp.
APPEND w_data TO i_data.
ENDLOOP.
ENDIF. "ENDIf i_mseg has records
Display_ALV
END-OF-SELECTION.
DATA : DATE(85),
DATE_LOW(10),
DATE_HIGH(10),
MSK TYPE STRING,
DATE1(10),
date2(10).
WA_COMMENTRY-TYP = 'H'.
WA_COMMENTRY-INFO = 'Material Consumption Report'.
APPEND WA_COMMENTRY TO IT_COMMENTRY.
CLEAR WA_COMMENTRY.
CONCATENATE S_BUDAT-LOW6(2) '/' S_BUDAT-LOW4(2) '/' S_BUDAT-LOW+0(4) INTO DATE1.
CONCATENATE S_BUDAT-high6(2) '/' S_BUDAT-high4(2) '/' S_BUDAT-high+0(4) INTO DATE2.
CONCATENATE 'Material Consumption Report :' DATE1 'To' date2 INTO DATE SEPARATED BY SPACE.
WA_COMMENTRY-TYP = 'S'.
WA_COMMENTRY-INFO = DATE.
APPEND WA_COMMENTRY TO IT_COMMENTRY.
CLEAR WA_COMMENTRY.
*SORT I_DATA BY MTART MATKL .
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
I_CALLBACK_PROGRAM = SY-REPID
I_CALLBACK_TOP_OF_PAGE = 'TOP_OF_PAGE'
I_BACKGROUND_ID = 'ALV_BACKGROUNG'
I_GRID_TITLE = 'STOCK LEDGER SUMMARY'
IS_LAYOUT = IT_LAYOUT
IT_FIELDCAT = IT_FIELD
IT_SORT = IT_SORT
I_SAVE = 'X'
IT_EVENTS = IT_EVENT
TABLES
T_OUTTAB = I_DATA.
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
FORM TOP .
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
EXPORTING
IT_LIST_COMMENTARY = IT_COMMENTRY
I_LOGO = 'INOXLOGO'
I_END_OF_LIST_GRID =
I_ALV_FORM.
REFRESH IT_COMMENTRY.
ENDFORM. " TOP-OF-PAGEIt is giving me error on sort statement
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
I_CALLBACK_PROGRAM = SY-REPID
I_CALLBACK_TOP_OF_PAGE = 'TOP_OF_PAGE'
I_BACKGROUND_ID = 'ALV_BACKGROUNG'
I_GRID_TITLE = 'STOCK LEDGER SUMMARY'
IS_LAYOUT = IT_LAYOUT
IT_FIELDCAT = IT_FIELD
IT_SORT = IT_SORT <<<<<<<<<<<<<<<<<<<<<<<<<<<
I_SAVE = 'X'
IT_EVENTS = IT_EVENT
TABLES
T_OUTTAB = I_DATA.
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF. -
Hi Friends,
im writting a report pgm to upload some data into ztable from sapia directory.
the code is given below...
SELECTION-SCREEN: BEGIN OF BLOCK b1 WITH FRAME TITLE text-028.
PARAMETERS: p_file_p(30) DEFAULT '/sapia/iface/in/comm/sapfin/' LOWER CASE.
PARAMETERS: p_file_n(30) DEFAULT 'ac1018pl'.
SELECTION-SCREEN: END OF BLOCK b1.
SELECTION-SCREEN: BEGIN OF BLOCK b3 WITH FRAME TITLE text-029.
PARAMETERS: p_file_1(30) DEFAULT '/sapia/iface/in/arch/sapfin/' LOWER CASE.
SELECTION-SCREEN: END OF BLOCK b3.
SELECTION-SCREEN: BEGIN OF BLOCK b2 WITH FRAME TITLE text-030.
PARAMETERS: p_file_d(30) DEFAULT 'zace1018'.
SELECTION-SCREEN: END OF BLOCK b2.
CONCATENATE p_file_p p_file_n INTO v_infile.
TRANSLATE v_infile TO LOWER CASE.
OPEN DATASET v_infile FOR INPUT IN TEXT MODE ENCODING DEFAULT. " Opening the file/Checking for file existence
IF sy-subrc <> 0.
MESSAGE e012 WITH v_infile. " Error occured while opening the file <file name>
EXIT.
ELSE.
DO.
READ DATASET v_infile INTO wa_file. " Reading file contents
IF sy-subrc <> 0.
CLOSE DATASET v_infile.
IF n_counter = 0.
MESSAGE e013 WITH v_infile.
ENDIF.
EXIT.
ELSE.
APPEND wa_file TO it_file.
CLEAR wa_file.
n_counter = n_counter + 1.
ENDIF.
ENDDO.
ENDIF.
If i run this im getting dump error at run time as follows,
Runtime error : CONVT_CODEPAGE
Except :CX_SY_CONVERSION_CODEPAGE
Cause: Conversion is not possible. The data is read as far as possible. Text data where the conversion has failed is undefined (see also note below).
Plz sole the problem... i need it urgent... Helpful answers will be rewarded...Hi,
change the code and try..remove the lower case statement and also the translate statement.
SELECTION-SCREEN: BEGIN OF BLOCK b1 WITH FRAME TITLE text-028.
PARAMETERS: p_file_p(30) DEFAULT '/sapia/iface/in/comm/sapfin/' .
PARAMETERS: p_file_n(30) DEFAULT 'ac1018pl'.
SELECTION-SCREEN: END OF BLOCK b1.
SELECTION-SCREEN: BEGIN OF BLOCK b3 WITH FRAME TITLE text-029.
PARAMETERS: p_file_1(30) DEFAULT '/sapia/iface/in/arch/sapfin/' .
SELECTION-SCREEN: END OF BLOCK b3.
SELECTION-SCREEN: BEGIN OF BLOCK b2 WITH FRAME TITLE text-030.
PARAMETERS: p_file_d(30) DEFAULT 'zace1018'.
SELECTION-SCREEN: END OF BLOCK b2.
CONCATENATE p_file_p p_file_n INTO v_infile.
Regards,
Nagaraj -
PCUI showing dump errors after EEWB enhancement
Hi Experts,
I'm using CRM5.0.
After adding some fields by EEWB(Easy Enhancement Workbench) the PCUI application showing several dump errors in several places. How to correct this problem, should I regenerate all the layout by CRMC_BLUEPRINT or any other way is there to correct these errors. Please suggest a solution for that.This is very urgent.
Thanks In Advance
RanaHi Fred,
1>
Whenever I'm clicking F4 help button beside service prospect,contact person etc the following dump is coming as in opportunity transaction (CRMD_BUS2000111) likewise other transactions also.
Note
The following error text was processed in the system CS1 : CRM_BSP_LIBRARY:structureEdit: Act. table parameter gt_layout is empty
The error occurred on the application server nmpcsssb1_CS1_01 and in the work process 0 .
The termination type was: ERROR_MESSAGE_STATE
The ABAP call stack was:
Method: IF_BSP_ELEMENT~DO_AT_BEGINNING of program CL_CRM_BSP_STRUCTUREEDIT======CP
What can I do?
If the termination type was RABAX_STATE, then you can find more information on the cause of the termination in the system CS1 in transaction ST22.
If the termination type was ABORT_MESSAGE_STATE, then you can find more information on the cause of the termination on the application server nmpcsssb1_CS1_01 in transaction SM21.
If the termination type was ERROR_MESSAGE_STATE, then you can search for more information in the trace file for the work process 0 in transaction ST11 on the application server nmpcsssb1_CS1_01 . In some situations, you may also need to analyze the trace files of other work processes.
If you do not yet have a user ID, contact your system administrator.
Error code: ICF-IE-http -c: 500 -u: ABAP1 -l: E -s: CS1 -i: nmpcsssb1_CS1_01 -w: 0 -d: 20070521 -t: 115438 -v: ERROR_MESSAGE_STATE -e: CRM_BSP_LIBRARY:structureEdit: Act. table parameter gt_layout is empty
HTTP 500 - Internal Server Error
Your SAP Internet Communication Framework Team
second error:
2>
Whenever any business partner is selected in partner id of partner tab ,partner fn(sold-to-party) then it is showing the following dump error.
SAP Note
The following error text was processed in the system:
An exception with the type CX_SY_DYN_CALL_PARAM_NOT_FOUND occurred, but was neither handled locally, nor declared in a RAISING clause
Exception Class CX_SY_DYN_CALL_PARAM_NOT_FOUND
Error Name
Program CL_CRM_BSP_INTLAY_PARTNER=====CP
Include CL_CRM_BSP_INTLAY_PARTNER=====CM002
ABAP Class CL_CRM_BSP_INTLAY_PARTNER
Method PUT_DATA
Line 1269
Long text Call of the function CRM_PARTNER_GET_COM_BY_STRUCT failed: The formal parameter ET_RETURN_VALUES does not exist.
EEWB used to add a field Account No in Service order transaction.
which is now reflecting to all the transaction as a customer field.
Thanks
Koustav -
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
-
Dump error when clicked on text elements in SAP Script window
Hi All,
There is an inclusion in SAP Script. I have written the code in driver program. I need to pass the value to SAP Script in the requested position. But when I go to SE71 > Form Name > Change or Display > MAIN Window > Text Elements > I get a dump error.
Category ABAP Programming Error
Runtime Errors DATA_LENGTH_TOO_LARGE
Except. CX_SY_RANGE_OUT_OF_BOUNDS
ABAP Program SAPLSTXK
Application Component BC-SRV-SCR
Date and Time 30.04.2014 20:00:08
Short text
Invalid partial field access: Length is too large
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLSTXK" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_RANGE_OUT_OF_BOUNDS', was not
caught in
procedure "TOKEN_COMMENT" "(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:
In the executed program "SAPLSTXK", the system attempted to access the field
"ITF_TOKEN" of the type "C" and with the length 255 using the length 272.
However, a partial field access with a length specification that is
larger than the field length is not allowed.
How to correct the error
Reduce the length used to access the field.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"DATA_LENGTH_TOO_LARGE" "CX_SY_RANGE_OUT_OF_BOUNDS"
"SAPLSTXK" or "LSTXKFRN"
"TOKEN_COMMENT"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
2937 * todo empty comment ???
2938 if g_tm_open eq true or " Section
2939 g_tm_b_close eq true.
2940 l_token = '\chcbpat0'.
2941 l_len = strlen( l_token ).
2942 token_control = true.
2943 assign l_token to <itf1>.
2944 perform put_itf1_new using l_len.
2945 perform token_line_begin changing l_next_token.
2946 else. " without section
2947 concatenate '\chcbpat0\line' g_cf_string l_cbpat_token into l_token.
2948 l_len = strlen( l_token ).
2949 token_control = true.
2950 assign l_token to <itf1>.
2951 perform put_itf1_new using l_len.
2952 endif.
2953 elseif l_next_token-code eq ')L'. " \par
2954 l_token = '\par'.
2955 l_len = strlen( l_token ).
2956 token_control = true.
2957 assign l_token to <itf1>.
2958 perform put_itf1_new using l_len.
2959 elseif l_next_token-code eq '(C' or " \par + format
2960 l_next_token-code eq ')C' or
2961 l_next_token-code eq '(&' or
2962 l_next_token-code eq 'TA' or
2963 l_next_token-code eq 'SC' or
2964 l_next_token-code eq 'ST'.
2965 concatenate '\chcbpat0\par' g_pf_string g_cf_string l_cbpat_token into l_token.
2966 l_len = strlen( l_token ).
>>>>> itf_token(l_len) = l_token.
2968 token_control = true.
2969 assign l_token to <itf1>.
2970 perform put_itf1_new using l_len.
2971 endif.
2972
2973 * Step 7: (L to disarm
2974 if g_compose eq true and
2975 l_next_token-code eq '(L'.
2976 perform read_next_itf_token(rstxscan) using p_token.
2977 endif.
2978
2979 ENDFORM. " token_comment
2980 *&---------------------------------------------------------------------*
2981 *& Form create_lang_info
2982 *&---------------------------------------------------------------------*
2983 * add default language to rtf
2984 *----------------------------------------------------------------------*
2985 * -->P_HEADER text
2986 * <--P_RESULT text
How do I open the text elements? I need to pass the variable inside SAP Script.
Please Help. The requirement is pending from very long. Not able to rectify this issue.
Regards,
RekhaHi,
There is a SAP Note about this problem
566794 - Runtime error: STRING_OFFSET_TOO_LARGE during conversion
Correction Instructions
Correction Instructions
Software Component
Valid from
Valid to
Number
SAP_BASIS
46B
46D
473267
SAP_BASIS
610
620
473185
Support Packages & Patches
Support Packages
Software Component
Release
Support Package
SAP_BASIS
46B
SAPKB46B48
46C
SAPKB46C39
46D
SAPKB46D28
610
SAPKB61027
620
SAPKB62014
Regards
Miguel -
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 PMHi 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
Maybe you are looking for
-
I have a question for someone who has worked on this scenario before. In my IDoc => XI => File scenario, I collect IDoc in a message list and pass this for transformation (n:1) Does the IDoc in the collect list look A. <IDOCTYP> <IDOC>...</IDOC> <IDO
-
IE keeps crashing my computer and goes to the blue
Whenever I launch IE after 5-10 sec my computer crashes and goes to the blue screen. which does a memory dump. I then need to turn the computer off and restart it to get it to run. This will keep happening after the system does a repair. I'm not sure
-
CHARM Configuration Error - No Consolidation System
Hi Im facing following errors in solution manager's CHARM. No consolidation system found for SSD-150 (project ZCHARM_GIL) No track for project ZCHARM_GIL with log. system SSD/150 i have more queries. 1.solar_project_admin > system Landscape> systems
-
MBP 2.16 Intel Core Duo upgradable to n?
just wondering because if the 2.16 ghz is upgradable? According to the updater it says "Your computer does not meet the hardware requirements for this update."
-
Hi, we're having an issue that is affecting logons in windows 8.1 only. It seems that after the user accounts password is changed in any way the user can no longer logon to any windows 8.1 machine with a pre-existing profile, logon halts at the welco