ECC 6.0 bar chart short dump
We are starting an upgrade from 4.7(non-Unicode) to ECC 6.0(Unicode), using SAPgui for Windows (version 7.10). In our 4.7 systems, the graphical bar chart on the Project Planning Board (txn CJ2C) works as expected. However, in the 6.0 development system, before displaying the gantt chart, the system short dumps with CREATE_ERROR.
I have searched the forums and looked through OSS notes and was unable to find anything that described the problem or was pertinent to our release. I have debugged through the transaction and am finding that the short dump occurs in method cl_gui_barchart=>constructor around the following code:
at line 83 if the system is unicode (which it is), the code calls method cl_gui_frontend_services=>check_gui_support, exporting 'ganttcontrol'/'usedataasstream' and expecting a result in variable l_guisupp_data_as_string. When it returns from the check_gui_support method, l_guisupp_data_as_string is blank, so the next "if" statement raises an error that is not handled:
if l_guisupp_data_as_string = abap_true.
.....code not executed because the variable = abap_false.
else.
.....raise create_error. <<<<< this is where the dump occurs.
endif.
Note that in the debugger, if I force l_guisupp_data_as_string to be = abap_true, the gantt chart/barchart displays as expected. (gotta love the debugger) But since it is standard SAP code I would prefer to resolve the problem without a modification and am hoping someone out there can point me in the right direction.
This short dump occurs with gui versions 710 and lower. (I personally am using sapgui version 710, patch level 7.) Has anyone had problems like this with the graphical elements in SAP or does anyone have a suggestion as to why the gui is not displaying the barchart correctly in our unicode system?
Sorry for the very long message, but thanks in advance for the help!
Amanda Salt
Edited by: Amanda Salt on Jun 17, 2008 11:14 PM
We are starting an upgrade from 4.7(non-Unicode) to ECC 6.0(Unicode), using SAPgui for Windows (version 7.10). In our 4.7 systems, the graphical bar chart on the Project Planning Board (txn CJ2C) works as expected. However, in the 6.0 development system, before displaying the gantt chart, the system short dumps with CREATE_ERROR.
I have searched the forums and looked through OSS notes and was unable to find anything that described the problem or was pertinent to our release. I have debugged through the transaction and am finding that the short dump occurs in method cl_gui_barchart=>constructor around the following code:
at line 83 if the system is unicode (which it is), the code calls method cl_gui_frontend_services=>check_gui_support, exporting 'ganttcontrol'/'usedataasstream' and expecting a result in variable l_guisupp_data_as_string. When it returns from the check_gui_support method, l_guisupp_data_as_string is blank, so the next "if" statement raises an error that is not handled:
if l_guisupp_data_as_string = abap_true.
.....code not executed because the variable = abap_false.
else.
.....raise create_error. <<<<< this is where the dump occurs.
endif.
Note that in the debugger, if I force l_guisupp_data_as_string to be = abap_true, the gantt chart/barchart displays as expected. (gotta love the debugger) But since it is standard SAP code I would prefer to resolve the problem without a modification and am hoping someone out there can point me in the right direction.
This short dump occurs with gui versions 710 and lower. (I personally am using sapgui version 710, patch level 7.) Has anyone had problems like this with the graphical elements in SAP or does anyone have a suggestion as to why the gui is not displaying the barchart correctly in our unicode system?
Sorry for the very long message, but thanks in advance for the help!
Amanda Salt
Edited by: Amanda Salt on Jun 17, 2008 11:14 PM
I just installed the latest patch on the SAPgui, so I am now running:
Release: 710 Final Release
File Version: 7100.2.8.1039
Build: 983952
Patch Level: 8
But I am still getting the short dump. I have done extensive searches of SAP Help, OSS notes, and this and other forums (even just looking up the problem on "google") but can't seem to find anything that applies to this scenario. I'm not very familiar with the methods in cl_gui_frontend_services, so if anyone can give me a pointer of where else I can look, I would greatly appreciate it!
I also have edited the Subject line to be more informative about the problem
Similar Messages
-
Short Dump with VA22 transaction in ECC 6
Hi All,
We are on ECC 6 and facing a short dump whenever we are trying to save some quotation. We are getting the following error.
There is probably an error in the program "SAPLSYDB". The program is triggered in the update task. There, the following ABAP/4 statements are not allowed:
CALL SCREEN
CALL DIALOG
CALL TRANSACTION
SUBMIT
"POSTING_ILLEGAL_STATEMENT" " "
"SAPLSYDB" or "LSYDBU27"
"DB_COMMIT".
Is there a sap note for this. Any link or pointer to this will be highly appreciated.
Regards,
JayantHello,
This looks like a problem for SAP. I assume that you have not modified the
program SAPLSYDB. I also assume that you have searched the Service Marketplasce
for any OSS notes. My next step would be to create a message to SAP to get them to
have a look.
Regards
Greg Kern -
Experts plz help me short dump
hi experts
plz help me
in ecc 6.0 gettin a short dump
THANKS IN ADVANCE
error is ::
For the statement
"TRANSFER f TO ..."
only character-type data objects are supported at the argument position
"f".
In this case. the operand "f" has the non-character-type "T_LINE". The
current program is a Unicode program. In the Unicode context, the type
'X' or structures containing not only character-type components are
regarded as non-character-type.
and it is coming in line::
LOOP AT v_tab.
TRANSFER v_tab TO p_file. "<b>this line contains error</b>
ENDLOOP.
FYI::
TYPES: BEGIN OF t_line,
pspid(9) TYPE c,
tab1 TYPE x,
post1 TYPE proj-post1,
tab2 TYPE x,
vernr TYPE prps-vernr,
tab3 TYPE x,
astnr TYPE prps-astnr,
tab4 TYPE x,
usr00(12) TYPE c,
tab5 TYPE x,
END OF t_line.
PARAMETERS: p_file LIKE rlgrap-filename OBLIGATORY. "DMA20040510
OPEN DATASET p_file FOR OUTPUT IN TEXT MODE ENCODING DEFAULT.
QUESTION:::
CAN WE USE FEILD SYMBOL IN IT
LIKE TRANSFER <Fs> TO P_FILE.Hi,
LOOP AT v_tab ASSIGNING <in>.
p_file = <in>.
ENDLOOP.
Best regards,
Prashant -
Short Dump while copying Org structure from ERP to CRM
Hello Experts:
We are trying to copy the Org structure from ECC to CRM.
We have a standard transaction 'CRMC_R3_ORG_GENERATE' to copy the the org structure from ECC or the IMG path:
SPRO->CRM->Master Data->Organization Management->Data Transfer->Coppy ECC Sales Structure
We have a multiple assignment scenario where each sales groups are assigned to multiple sales offices and likewise,each sales office is assigned to multiple sales org unit in ECC.
This can be achieved by turning on the enhanced version.
In our current business,even though the sales offices and groups are created,but are not having relavance in the business,hence while running in the sandbox system, we ran the program to copy the structures in the standard mode(default) and we could copy it without issues and create the org units for every entity in CRM based on how the number ranges are defined.
What happens when enhanced version switch is turned on ::
While we turn the mode to enhanced version, The system automatically::
- enhances the Function tab page in the ppoma_crm transaction to include a grid table, in which you maintain multiple assignments of organizational units
- generates an extra dialog box to the Organization tab page in business transactions for you to select the relevant assignment path for the organizational unit
- adapts the consistency check in business transactions to take into account organizational units that have been multiple assigned
Risk factor :
Once you have switched to the enhanced backend integration version of the organizational model you cannot return to the standard backend integration version. The system will also automatically make changes to the organizational model version in CRM Mobile Sales.
Also this structure will happen across all the clients in the system,so unfortunately cannot try in a sandbox client also of the new environment.
We are building our development box,so while running the above step in standard mode,the program gives a short dump due to long execution time even though we have the same amount of data as in our prototype system.
Also, we increased the idle time value to a very high value.
When I approached SAP OSS,I was told that it is due to the multiple assignment scenario,hence we need to switch to enhanced version in CRM before we run the copy program ( CRMC_ORG_R3_GENERATE )
I am not quite sure if the mismatch of the scenarios between CRM and ECC could be causing this short dump as we could run it in standard mode in our prototype/sandbox environment without issues even with the same data volume as in the new development system .
I am looking for help from all the experts if they have come across similar issue and your recommendations/feedback if this can be corrected.
Appreciate your guidance/recommendation on this issue.
thanks!!In CRM Best Practices Building block C05 is the step by step description how to replicate Org. structure and some of employee's master data.
Follow link - http://help.sap.com/bp_crmv12007/CRM_DE/BBLibrary/html/C05_EN_DE.htm -
How to avoid short dump in ECC 5.0
Hi
Can anyone tell me how to avoid short dump in ECC 5.0
I'm told we can avoid program going to short dump, instead IT WILL GRACEFULLY EXIT..Hi
By implementing the code as for every unsuccess/failure conditions control has come out of the program. then only u can avoid dumps even though u code the not perfect functionality.
Regards,
kumar -
Short Dump with Fetch in ECC 6.0
Hello Friends,
I have a query sth like this.
<b>fetch next cursor wc_cursor
into table it_bdi_entry
package size s_pkg.</b>
it_bdi_entry is a internal table of type bdi_entry.
When i use this fetch statement in ECC 6.0 and the fetching row is not all char (like bdi_entry) then i see a short dump saying sth like the source and target are not of same types. How do i overcome this error. please suggest. Thanks in advance.HI Ramu
I doubt the dump is due to UNICODE compliancy.
In UNICODE systems, we can transfer data between structures only when the structure are similar or having only character fields.
To avoid the dump, we might need to handle field by field.
Hope this helps.
Kind Regards
Eswar -
Short dump in ECC 6.0 during delta load
Hi,
We are currently working in BI upgrade project
from BW 2.1c to BI 7.0
At the same time R/3 is being upgraded from 4.0B to ECC 6.0
During delta load we are getting short dump in R/3 system.
Below is the short dump detalis
The current ABAP prgm "SAPMSSY1" had to be terminated because it has come across a statement that unfortunately cannot be executed.
The following syntax error occured in program "/BI0/SAPLQI2LIS_11_VAITM" in include "/BI0/SAPLQI2LIS_11_VAITM" is not Unicode-compatible, according to its attributes.
If any help can be provided on this issue it would be great.
Regards,
Nikhil
Edited by: Nikhil Sakhardanday on Sep 11, 2008 1:58 PMHi,
did you made UCCHECK ?
/manfred -
Short dump in BP after upgrade to ECC 6.0
Hi,
We have upgraded system to ECC 6.0 from ECC 5.0
After upgrade system is giving short dump in transaction BP, event tried to navigate on BP screen.
Short dump description:
A RAISE statement in the program "CL_OS_TRANSACTION=============CP" raised the exception condition "OS_COMMIT_TOP_FAILED".
Since the exception was not intercepted by a superior program, processing was terminated.
Please advise to resolve this issue.
Regards,
DipakWhen exactly does this error appear? On save? clicking on a specific entry?
I suggest opening an OSS call for this problem, this doesn't seem to known (at least I didn't find any notes)
Markus -
Short dump when '1 BOX PACK' clicked on VL02N, in ECC 6 system
Hi
I am getting a short dump "'DYNPRO_MSG_IN_HELP' "when i click '1 box pack' button in VL02N transaction during our upgrade system from 4.6C to ECC 6.0. When i go through the old SAP note - 401823, it says to add entries in VFBS transaction for all T185 entries for this kind of dumps. But i am missing entries for SAPMV50A, I0 and ZVPK combination at support pack level '14'(SAP_APPL) in our system.
Could anyone let me know the entries to be maintained for all the T185* tables mentioned in VFBS transaction.
(or) is there any OSS note already created for this issue? please let me know all the details.
Thank you,
AnilHi Laxmi,
We are already in Support pack. (SAPKH60014), and note which you given was SP - SAPKH60007, so this correction was already implemented in our system.
Is there a note/solution specific to '1 BOX PACK' dump and T185* table entry missing?
Let me know,
thank you,
Anil -
Classic scenario-SC not transferred to backend,short dump in ecc
hi Guru's,
Classic scenario, sc not transferred to backend, executed FM bbp_pd_sc_resubmit, short dump occurred in the backend stating call function not found
please help
short dump file attached
regards,
kiranHi Kiran,
Could you please send the DUMP for analysis.
Please try to use this -
This is the new report BBP_SC_AUTO_RETRANSFER to change the status from
I1111 Item in Transfer Process
I1112 Error in transfer/ transmission
Thanks,
From RBEI,
Snehal -
In SMARTFORMS when openee a Text Node, Giving a Short Dump
Hi
I am getting Short Dump in SMARTFORMS Transaction, when ever I opened a Text Node and made some changes in it.
With out opening a Text Node I can able to change and activate the SmartForm.
But if I open a Text Node I can able to make changes in the Text Node but later if i click on any other Node, it is giving a Short Dump.
But all other systems in my office are working fine.
I have tried the Utilities->Settings-> and changed the editor also.
I have also Installed the SAPGUI once again for this Issue. But still I am getting the same problem.
Can anyone Please help me on this Issue.
I am sending the error enalysis of the Short Dump.
Error analysis
Short text of error message:
Control Framework : Error processing control
Long text of error message:
Diagnosis
An error occurred when the system tried to process the commands
from the Automation Queue on the presentation server.
There are several possible reasons for this:
- The installation of the SAP GUI on the presentation server is
faulty or obsolete.
- There is an error in the application program
- There is an error in the SAPGUI or an integrated control
Procedure
1. Make sure that you have imported the appropriate Support
Package, the current kernel, and GUI patch for the release of your
system
2. Check whether the error occurs locally on one or a few PCs, or
generally on all PCs. Note whether the error only occurs for some
users, for example because of a specific Customizing setting.
If it only occurs locally, this suggests an installation problem
with the PC. Check the installation; if necessary, reinstall the
software. In the dump, search for the SY-MSGLI field, since it may
point to the cause of the error.
3. Activate the Automation Trace (in accordance with SAP Note
158985).
4.Start the transaction and continue until the screen immediately
before the dump.
5. From the System -> Utilities menu, choose Autom. Queue,
Synchronous Processing.
The status bar of the GUI displays the text:
"Automation synchron flush mode on"
6. If you now proceed with the application, the short dump will
display the ABAP call that caused the error; the Automation Trace
will contain the error on the presentation server.
7. If necessary, load the short dump and trace files on to
sapservX, so that SAP can analyze them.
Technical information about the message:
Message class....... "CNDP"
Number.............. 006
Thanks in Advance.Hi
I think dump is because of SAP GUI. If you are ECC 6.0 then install SAP GUI 710 with patch level 2 or more and check
Regards
Shiva -
Short Dump DATA_OFFSET_TOO_LARGE in dialog instance
Hi,
We recently install a Dialog Instance for our production system (ECC 5.0), and we received the Short Dump DATA_OFFSET_TOO_LARGE only in our Dialog Instance, in our Central Instance the error does not occur. This is the error:
Runtime Error DATA_OFFSET_TOO_LARGE
Except. CX_SY_RANGE_OUT_OF_BOUNDS
Date and Time 30.03.2007 08:19:13
ShrtText
Invalid partial field access: Offset too large
What happened?
Error in ABAP application program.
The current ABAP program "SAPLSNR3" 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?
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.
is especially useful if you want to keep a particular message.
Error analysis
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_RANGE_OUT_OF_BOUNDS', was neither caught nor passed along using a RAISING clause, in the procedure "NUMBER_GET_NEXT" "(FUNCTION)"
Since the caller of the procedure could not have expected this exception to occur, the running program was terminated.
The reason for the exception is:
The system tried to access field "Z_DB_GROUP_KEY" with type "C" and length 20 in the current program "SAPLSNR3" using offset 20.
Partial field access is not allowed with an offset specification that is larger than actual field length.
How to correct the error
Make the offset smaller with which you want to access the field.
You may able to find an interim solution to the problem in the SAP note system. If you have access to the note system yourself, use the following search criteria:
"DATA_OFFSET_TOO_LARGE" CX_SY_RANGE_OUT_OF_BOUNDSC
"SAPLSNR3" or "LSNR3U01"
"NUMBER_GET_NEXT"
User and Transaction
Client.............. 300
User................ 645
Language key........ "S"
Transaction......... "FNV5 "
Program............. "SAPLSNR3"
Screen.............. "SAPLFVDA 0400"
Screen line......... 323
Information on where terminated
The termination occurred in the ABAP program "SAPLSNR3" in "NUMBER_GET_NEXT".
The main program was "SAPMF67A ".
The termination occurred in line 99 of the source code of the (Include)program "LSNR3U01"
of the source code of program "LSNR3U01" (when calling the editor 990).
Error occurred during batch input processing
Processing was terminated because the exception "CX_SY_RANGE_OUT_OF_BOUNDS" occurred in the procedure "NUMBER_GET_NEXT" "(FUNCTION)" but was not handled locally, not declared in the RAISING clause of the procedure.
The procedure is in the program "SAPLSNR3 ". Its source code starts in line 5
of the (Include) program "LSNR3$01 ".
Our Database is DB2 UDB with FixPak 10, the Central Instance is on Solaris 9 and our Dialog Instance is on Linux Red Hat. Both instances have the same Kernel release (155) installed.
Can you help me please?
Best Regards,
Eduardo Perez.Hi Eduardo,
Just refresh the number range buffers in both instances and see what happens.
Go to SM56. From menu bar choose number range buffer. Choose client as as current client. Check the checkbox global reset. press enter.
There is one more thing you can check before buffer refresh. Look out for the number range object being used.
Then check it in SNRO txn. There you will find the transaction for maintaining the number range object intervals. GO to that transaction in both the instances and display the intervals. You will find discprency between the two instances.Though it is not very critical in case ur not able to find the number range object.
Regards.
Ruchit.
Message was edited by:
Ruchit Khushu -
REGARDING ALV REPORT SHORT DUMP
hI ALL,
IAM GETTING FOR THE FOLLOWING CODE,
PLEASE WHY THE ERROR IN ECC 6.0
TABLES AND DATA DECLARATION.
*TABLES: mara,makt.",marc.
data syrepid like sy-repid.
data sydatum(10). " LIKE sy-datum.
data sypagno(3) type n.
WHEN USING MORE THAN ONE TABLE IN ALV WE NEEED TO DECLARE THE TYPE
GROUP (TYPE-POOLS--------->SLIS)
type-pools : slis.
INTERNAL TABLE DECLARATION.
INTERNAL TABLE TO HOLD THE VALUES FROM THE MARA TABLE
data: begin of t_mara occurs 0,
matnr like mara-matnr,
meins like mara-meins,
mtart like mara-mtart,
matkl like mara-matkl,
end of t_mara.
INTERNAL TABLE TO HOLD THE CONTENTS FROM THE EKKO TABLE
data : begin of t_marc occurs 0,
matnr like mara-matnr,
werks like marc-werks,
minbe like marc-minbe.
data: end of t_marc.
INTERNAL TABLE TO HOLD THE VALUES FROM MAKT TABLE.
data : begin of t_makt occurs 0,
matnr like mara-matnr,
maktx like makt-maktx,
spras like makt-spras,
end of t_makt.
INTERNAL TABLE WHICH ACTUALLY MERGES ALL THE OTHER INTERNAL TABLES.
data: begin of itab1 occurs 0,
matnr like mara-matnr,
meins like mara-meins,
maktx like makt-maktx,
spras like makt-spras,
werks like marc-werks,
minbe like marc-minbe,
end of itab1.
THE FOLLOWING DECLARATION IS USED FOR DEFINING THE FIELDCAT
AND THE LAYOUT FOR THE ALV.
HERE AS slis_t_fieldcat_alv IS A INTERNAL TABLE WITHOUT A HEADER LINE
WE EXPLICITELY DEFINE AN INTERNAL TABLE OF THE SAME STRUCTURE AS THAT
OF slis_t_fieldcat_alv BUT WITH A HEADER LINE IN THE DEFINITION.
THIS IS DONE TO MAKE THE CODE SIMPLER.
OTHERWISE WE MAY HAVE TO DEFINE THE STRUCTURE AS IN THE NORMAL SAP
PROGRAMS.
IN THE FIELDCATALOG TABLE WE ACTUALLY PASS THE FIELDS FROM ONE OR
MORE TABLES AND CREATE A STRUCTURE
IN THE LAYOUT STRUCTURE WE BASICALLY DEFINE THE FORMATTING OPTIONS
LIKE DISPLAY IN THE ZEBRA PATTERN ,THE HOTSPOT OPTIONS ETC.
data: fieldcatalog type slis_t_fieldcat_alv with header line,
fieldlayout type slis_layout_alv.
DECLARING THE EVENTTABLE INTERNL TABLE FOR USING EVENTS LIKE
TOP-OF-PAGE ETC.
data : eventstab type slis_t_event with header line.
DECLARING AN INTERNAL TABLE TO HOLD THE DATA FOR THE TOP-OF-PAGE
data : heading type slis_t_listheader with header line.
data : heading1 type slis_t_listheader with header line.
data : heading2 type slis_t_listheader with header line.
data : heading3 type slis_t_listheader with header line.
data : heading4 type slis_t_listheader with header line.
data : heading5 type slis_t_listheader with header line.
data : heading6 type slis_t_listheader with header line.
data : heading7 type slis_t_listheader with header line.
data : heading8 type slis_t_listheader with header line.
STRUCTURE TO PASS THE COLOR ATTRIBUTES FOR DISPLAY.
data : colorstruct type slis_coltypes.
INITIALIZATION. *
initialization.
syrepid = sy-repid.
sypagno = sy-pagno.
clear fieldcatalog.
START-OF-SELECTION. *
start-of-selection.
SUBROUTINE TO POPULATE THE COLORSTRUCT
perform fill_colorstruct using colorstruct.
SUBROUTINE TO POPULATE THE FIELDS OF THE FIELD CATALOGUE
perform populate_fieldcatalog.
SUBROUTINE TO SELECT DATA FROM VARIOUS TABLES AND POPULATE IT IN THE
INTERNAL TABLE.
perform selectdata_and_sort.
SUBROUTINE TO POPULATE THE LAYOUT STRUCTURE.
perform populate_layout using fieldlayout.
SUBROUTINE TO CALL THE FUNCTION MERGE TO ENSURE PROPER DISPLAY.
perform merge_fieldcatalog.
SUBROUTINE TO POPULATE THE EVENTSTAB.
perform fill_eventstab tables eventstab.
SUBROUTINE TO POPULATE THE HEADING TABLES.
perform fill_headingtable tables heading using 'HEADING'.
perform fill_headingtable tables heading1 using 'HEADING1'.
perform fill_headingtable tables heading2 using 'HEADING2'.
perform fill_headingtable tables heading3 using 'HEADING3'.
perform fill_headingtable tables heading4 using 'HEADING4'.
perform fill_headingtable tables heading5 using 'HEADING5'.
perform fill_headingtable tables heading6 using 'HEADING6'.
perform fill_headingtable tables heading7 using 'HEADING7'.
perform fill_headingtable tables heading8 using 'HEADING8'.
SUBROUTINE TO DISPLAY THE LIST.
perform display_alv_list.
FORMS
IN THIS SUBROUTINE WE POPULATE THE FIELDCATALOG TABLE WITH THE NAMES
OF THE TABLE,FIELDNAME,WHETHER IT IS KEY FIELD OR NOT,HEADING AND
COLUMN JUSTIFICATION.
form populate_fieldcatalog.
perform fill_fields_of_fieldcatalog tables fieldcatalog
using 'ITAB1' 'MATNR' 'X' .
perform fill_fields_of_fieldcatalog tables fieldcatalog
using 'ITAB1' 'MEINS' ' '.
perform fill_fields_of_fieldcatalog tables fieldcatalog
using 'ITAB1' 'MAKTX' ' ' .
perform fill_fields_of_fieldcatalog tables fieldcatalog
using 'ITAB1' 'MTART' ' ' .
perform fill_fields_of_fieldcatalog tables fieldcatalog
using 'ITAB1' 'MATKL' ' ' .
perform fill_fields_of_fieldcatalog tables fieldcatalog
using 'ITAB1' 'SPRAS' ' ' .
perform fill_fields_of_fieldcatalog tables fieldcatalog
using 'ITAB1' 'WERKS' ' ' .
perform fill_fields_of_fieldcatalog tables fieldcatalog
using 'ITAB1' 'MINBE' ' ' .
endform. " POPULATE_FIELDCATALOG
FORM FILL_FIELDS_OF_FIELDCATALOG *
--> FIELDCATALOG *
--> P_TABNAME *
--> P_FIELDNAME *
--> P_KEY *
--> P_KEY *
form fill_fields_of_fieldcatalog tables fieldcatalog
structure fieldcatalog
using p_tabname
p_fieldname
p_key.
p_no_out.
fieldcatalog-tabname = p_tabname.
fieldcatalog-fieldname = p_fieldname.
fieldcatalog-key = p_key.
fieldcatalog-emphasize = '1234'.
*fieldcatalog-no_out = p_no_out.
append fieldcatalog.
endform. " FILL_FIELDSOFFIELDCATALOG
FORM POPULATE_LAYOUT *
--> FIELDLAYOUT *
form populate_layout using fieldlayout type slis_layout_alv.
fieldlayout-f2code = '&ETA' .
fieldlayout-zebra = 'X'.
FOR THE WINDOW TITLE.
fieldlayout-window_titlebar = 'ALV with Events'.
fieldlayout-colwidth_optimize = 'X'.
fieldlayout-no_vline = ' '.
*fieldlayout-no_input = 'X'.
fieldlayout-confirmation_prompt = ''.
fieldlayout-key_hotspot = 'X'.
This removes the column headings if the flag is set to 'X'
fieldlayout-no_colhead = ' '.
*fieldlayout-hotspot_fieldname = 'MAKTX'.
fieldlayout-detail_popup = 'X'.
fieldlayout-coltab_fieldname = 'X'.
endform. " POPULATE_LAYOUT
FORM SELECTDATA_AND_SORT *
form selectdata_and_sort.
select matnr meins mtart matkl from mara
into corresponding fields of t_mara
up to 500 rows .
select matnr maktx spras from makt
into corresponding fields of t_makt
where matnr = t_mara-matnr and
spras = sy-langu.
select matnr werks minbe from marc
into corresponding fields of t_marc
where matnr = t_mara-matnr.
append t_marc.
endselect.
append t_makt.
endselect.
append t_mara.
endselect.
perform populate_itab1.
sort itab1 by matnr.
endform. " SELECTDATA_AND_SORT
FORM MERGE_FIELDCATALOG *
form merge_fieldcatalog.
call function 'REUSE_ALV_FIELDCATALOG_MERGE'
exporting
i_program_name = syrepid
i_internal_tabname = 'ITAB1'
i_structure_name = 'COLORSTRUCT'
I_CLIENT_NEVER_DISPLAY = 'X'
i_inclname = syrepid
changing
ct_fieldcat = fieldcatalog[]
exceptions
inconsistent_interface = 1
program_error = 2
others = 3.
endform. " MERGE_FIELDCATALOG
IN THIS FUNCTION THE MINIMUM PARAMETERS THAT WE NEED TO PASS IS AS
FOLLOWS:-
i_callback_program --> CALLING PROGRAM NAME
i_structure_name --> STRUCTURE NAME.
is_layout --> LAYOUT NAME.
it_fieldcat ---> BODY OF THE FIELD CATALOGUE INTERNAL TABLE
form display_alv_list.
call function 'REUSE_ALV_LIST_DISPLAY'
exporting
I_INTERFACE_CHECK = ' '
i_callback_program = syrepid
I_CALLBACK_PF_STATUS_SET = ' '
I_CALLBACK_USER_COMMAND = ' '
i_structure_name = 'ITAB1'
is_layout = fieldlayout
it_fieldcat = fieldcatalog[]
IT_EXCLUDING =
IT_SPECIAL_GROUPS =
IT_SORT =
IT_FILTER =
IS_SEL_HIDE =
I_DEFAULT = 'X'
THE FOLLOWING PARAMETER IS SET AS 'A' INORDER TO DISPLAY THE STANDARD
TOOL BAR
i_save = 'A'
IS_VARIANT = ' '
it_events = eventstab[]
IT_EVENT_EXIT =
IS_PRINT =
I_SCREEN_START_COLUMN = 0
I_SCREEN_START_LINE = 0
I_SCREEN_END_COLUMN = 0
I_SCREEN_END_LINE = 0
IMPORTING
E_EXIT_CAUSED_BY_CALLER =
ES_EXIT_CAUSED_BY_USER =
tables
t_outtab = itab1
exceptions
program_error = 1
others = 2.
endform. " DISPLAY_ALV_LIST
*& Form POPULATE_ITAB1
text
--> p1 text
<-- p2 text
form populate_itab1.
loop at t_mara.
loop at t_makt where matnr = t_mara-matnr.
loop at t_marc where matnr = t_mara-matnr.
move-corresponding t_mara to itab1.
move-corresponding t_makt to itab1.
move-corresponding t_marc to itab1.
append itab1.
endloop.
endloop.
endloop.
endform. " POPULATE_ITAB1
*& Form FILL_EVENTSTAB
text
-->P_EVENTSTAB text *
form fill_eventstab tables p_eventstab structure eventstab.
WHEN THE FOLLOWING FUNCTION IS CALLED THE SYSTEM POPULATES THE
INTERNAL TABLE EVENTSTAB WITH A LIST OF EVENTS NAME.
AS SHOWN BELOW WHEN USING I_LIST_TYPE = 0 THE FUNCTION RETURNS 14
EVENTS NAME.
call function 'REUSE_ALV_EVENTS_GET'
exporting
i_list_type = 0
importing
et_events = p_eventstab[]
exceptions
list_type_wrong = 1
others = 2.
BY CALLING THE ABOVE FUNCTION WE FIRST POPULATE THE EVENTSTAB WITH
THE PREDEFINED EVENTS AND THEN WE MOVE THE FORM NAME AS SHOWN BELOW.
WE ASSIGN A FORM NAME TO THE EVENT AS REQUIRED BY THE USER.
FORM NAME CAN BE ANYTHING.THE PERFORM STATEMENT FOR THIS FORM
IS DYNAMICALY CALLED.
read table p_eventstab with key name = slis_ev_top_of_page.
if sy-subrc = 0 .
move 'TOP_OF_PAGE' to p_eventstab-form.
append p_eventstab.
endif.
read table p_eventstab with key name = slis_ev_top_of_coverpage.
if sy-subrc = 0 .
move 'TOP_OF_COVERPAGE' to p_eventstab-form.
append p_eventstab.
endif.
read table p_eventstab with key name = slis_ev_end_of_coverpage .
if sy-subrc = 0 .
move 'END_OF_COVERPAGE' to p_eventstab-form.
append p_eventstab.
endif.
read table p_eventstab with key name = slis_ev_foreign_top_of_page.
if sy-subrc = 0 .
move 'FOREIGN_TOP_OF_PAGE' to p_eventstab-form.
append p_eventstab.
endif.
read table p_eventstab with key name = slis_ev_foreign_end_of_page.
if sy-subrc = 0 .
move 'FOREIGN_END_OF_PAGE' to p_eventstab-form.
append p_eventstab.
endif.
read table p_eventstab with key name = slis_ev_list_modify.
if sy-subrc = 0 .
move 'LIST_MODIFY' to p_eventstab-form.
append p_eventstab.
endif.
read table p_eventstab with key name = slis_ev_top_of_list.
if sy-subrc = 0 .
move 'TOP_OF_LIST' to p_eventstab-form.
append p_eventstab.
endif.
read table p_eventstab with key name = slis_ev_end_of_page.
if sy-subrc = 0 .
move 'END_OF_PAGE' to p_eventstab-form.
append p_eventstab.
endif.
read table p_eventstab with key name = slis_ev_end_of_list .
if sy-subrc = 0 .
move 'END_OF_LIST' to p_eventstab-form.
append p_eventstab.
endif.
endform. " FILL_EVENTSTAB
*& Form FILL_HEADINGTABLE
text
-->P_HEADING text *
form fill_headingtable tables p_heading structure heading
using tablename.
case tablename.
when 'HEADING'.
p_heading-typ = 'H'.
concatenate
' REPORT NAME:-' syrepid
' ABB Industry Pte Ltd' into p_heading-info.
append p_heading.
write sy-datum using edit mask '__/__/____' to sydatum.
concatenate
' DATE:-' sydatum ' USER: ' sy-uname 'PAGE NO:' sypagno
into p_heading-info.
append p_heading.
when 'HEADING1'.
p_heading-typ = 'H'.
p_heading-info = 'TOP-OF-COVER-PAGE'.
append p_heading.
when 'HEADING2'.
p_heading-typ = 'H'.
p_heading-info = 'END-OF-COVER-PAGE'.
append p_heading.
when 'HEADING3'.
p_heading-typ = 'H'.
p_heading-info = 'FOREIGN-TOP-OF-PAGE'.
append p_heading.
when 'HEADING4'.
p_heading-typ = 'H'.
p_heading-info = 'FOREIGN-END-OF-PAGE'.
append p_heading.
WHEN 'HEADING5'.
P_HEADING-TYP = 'H'.
P_HEADING-INFO = 'LIST-MODIFY'.
APPEND P_HEADING.
when 'HEADING6'.
p_heading-typ = 'H'.
p_heading-info = 'END-OF-PAGE'.
append p_heading.
when 'HEADING7'.
p_heading-typ = 'H'.
p_heading-info = 'END-OF-LIST'.
append p_heading.
when 'HEADING8'.
p_heading-typ = 'H'.
p_heading-info = 'TOP-OF-LIST'.
append p_heading.
endcase.
endform. " FILL_HEADINGTABLE
FORM TOP_OF_PAGE *
form top_of_page.
call function 'REUSE_ALV_COMMENTARY_WRITE'
exporting
it_list_commentary = heading[]
exceptions
others = 1.
endform.
*& Form FILL_COLORSTRUCT
text
-->P_COLORSTRUCT text *
form fill_colorstruct using p_colorstruct type slis_coltypes .
p_colorstruct-heacolfir-col = 6.
p_colorstruct-heacolfir-int = 1.
p_colorstruct-heacolfir-inv = 1.
endform. " FILL_COLORSTRUCT
FORM TOP_OF_COVERPAGE *
form top_of_coverpage.
call function 'REUSE_ALV_COMMENTARY_WRITE'
exporting
it_list_commentary = heading1[]
exceptions
others = 1.
endform.
FORM END_OF_COVERPAGE *
form end_of_coverpage.
call function 'REUSE_ALV_COMMENTARY_WRITE'
exporting
it_list_commentary = heading2[]
exceptions
others = 1.
endform.
FORM FOREIGN_TOP_OF_PAGE *
form foreign_top_of_page.
call function 'REUSE_ALV_COMMENTARY_WRITE'
exporting
it_list_commentary = heading3[]
exceptions
others = 1.
endform.
FORM FOREIGN_END_OF_PAGE *
form foreign_end_of_page.
call function 'REUSE_ALV_COMMENTARY_WRITE'
exporting
it_list_commentary = heading4[]
exceptions
others = 1.
endform.
FORM LIST_MODIFY *
*FORM LIST_MODIFY.
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
EXPORTING
IT_LIST_COMMENTARY = HEADING5[]
EXCEPTIONS
OTHERS = 1.
*ENDFORM.
FORM END_OF_PAGE *
form end_of_page.
call function 'REUSE_ALV_COMMENTARY_WRITE'
exporting
it_list_commentary = heading6[]
exceptions
others = 1.
endform.
FORM END_OF_LIST *
form end_of_list.
call function 'REUSE_ALV_COMMENTARY_WRITE'
exporting
it_list_commentary = heading7[]
exceptions
others = 1.
endform.
FORM TOP_OF_LIST *
form top_of_list.
call function 'REUSE_ALV_COMMENTARY_WRITE'
exporting
it_list_commentary = heading8[]
exceptions
others = 1.
endform.
SHORT DUMP IS
This error may occur if
- You address a typed field symbol before it has been set with
ASSIGN
- You address a field symbol that pointed to the line of an
internal table that was deleted
- You address a field symbol that was previously reset using
UNASSIGN or that pointed to a local field that no
longer exists
- You address a global function interface, although the
respective function module is not active - that is, is
not in the list of active calls. The list of active calls
can be taken from this short dump.
PLEASE GIVE ME ANSWER.
REGARDSHI I MADE SOME CHANGES TO UR CODE...
RUN IF THIS IS THE REQ ...
IN SELECT QUERIES OF RETRIEVING DATA..
form selectdata_and_sort.
select matnr meins mtart matkl from mara
into corresponding fields of TABLE t_mara
WHERE MATNR = T_MARA-MATNR.
up to 200 rows .
IF SY-SUBRC = 0.
MESSAGE I001 WITH ' DATA RET FROM MARA'.
ENDIF.
IF T_MARA[] IS NOT INITIAL .
select
matnr
maktx
spras
From
makt
into corresponding fields of TABLE t_makt
FOR ALL ENTRIES IN T_MARA
where matnr = t_mara-matnr and
spras = sy-langu.
ENDIF.
IF SY-SUBRC = 0 .
MESSAGE I001 WITH ' DATA RET FROM MAKT'.
ENDIF.
IF T_MAKT[] IS NOT INITIAL.
select matnr
werks
minbe
from marc
into corresponding fields of TABLE t_marc
FOR ALL ENTRIES IN
T_MAKT where matnr = t_maKT-matnr.
ENDIF.
ENDFORM. "selectdata_and_sort
JUST TRY THIS CODE.. -
Business Graphic working but short dumping when 'No Data' is available
Dear Experts,
I am trying to plot a graph (Bar chart) and it is working very well except when these is no data. In that instance instead of not displaying a data, it is giving short dump.
I am trying to plot a graph for a project from a list of the projects. In the Context, List of projects is a parent node while the cost data (used for drawing graph) is on child node. Both are with the cardinality of 0..n
When the project has cost data, graph is working beautifully but when the project does not have a cost data i get short dump.
Here is the what I get in Internet explorer.
The following error text was processed in the system UPG : Access via 'NULL' object reference not possible.
The error occurred on the application server SAPSANDPIT_UPG_00 and in the work process 2 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Method: IF_NW7_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/CBUSINESS_GRAPHICS======CP
Method: IF_NW7_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/C8STANDARD==============CP
Method: IF_NW7_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/C8STANDARD==============CP
Method: IF_NW7_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/C7STANDARD==============CP
Method: IF_WDR_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program CL_WDR_VIEW_ADAPTER===========CP
Method: IF_WDR_NW7_DELTA_RENDERER~CALCULATE_DELTA_BLOCKS of program CL_WDR_VIEW_ADAPTER===========CP
Method: IF_WDR_NW7_DELTA_RENDERER~CALCULATE_DELTA_BLOCKS of program CL_WDR_WINDOW_CONTENT_ADAPTER=CP
Method: SET_CONTENT of program CL_WDR_NW7_INT_WIN_ADAPTER====CP
Method: SET_CONTENT of program CL_WDR_NW7_MAIN_WIN_ADAPTER===CP
Method: IF_WDR_CLIENT~SEND_RESPONSE of program CL_WDR_CLIENT_SSR_LS==========CP
And here is what is in ST22
Runtime Errors OBJECTS_OBJREF_NOT_ASSIGNED_NO
Exception CX_SY_REF_IS_INITIAL
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not
caught in
procedure "IF_NW7_VIEW_ELEMENT_ADAPTER~SET_CONTENT" "(METHOD)", 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:
You attempted to use a 'NULL' object reference (points to 'nothing')
access a component.
An object reference must point to an object (an instance of a class)
before it can be used to access components.
Either the reference was never set or it was set to 'NULL' using the
CLEAR statement.
Problem is at following point
mv_CHARTDATA = mv_DATA->create_simple_element( name = 'ChartData' parent = mv_DATA ). "#
* >> END_UCA BUSINESS_GRAPHICS|BUSINESS_GRAPHICS|CHARTDATA
* >> Property: Get BUSINESS_GRAPHICS-SERIES_SOURCE
mv_SERIES_SOURCE = get_bound_node( i_binding = wd_BUSINESS_GRAPHICS->bp_SERIES_SOURCE )
* >> Property: UCA BUSINESS_GRAPHICS-SERIES_ELEMENTS
* >> UCA BUSINESS_GRAPHICS|BUSINESS_GRAPHICS|SERIES_ELEMENTS
mv_SERIES_ELEMENTS = mv_SERIES_SOURCE->get_elements( ).
* >> END_UCA BUSINESS_GRAPHICS|BUSINESS_GRAPHICS|SERIES_ELEMENTS
* >> Property: UCA BUSINESS_GRAPHICS-SERIES_SOURCE_PATH
* >> UCA BUSINESS_GRAPHICS|BUSINESS_GRAPHICS|SERIES_SOURCE_PATH
mv_SERIES_SOURCE IN in above code is initial when data does not exists for a project.
Thanks in advance for your help.
ABAPerForgot to add following info from ST22
Information on where terminated
Termination occurred in the ABAP program "/1WDA/CBUSINESS_GRAPHICS======CP" -
in "IF_NW7_VIEW_ELEMENT_ADAPTER~SET_CONTENT".
The main program was "SAPMHTTP ".
In the source code you have the termination point in line 753
of the (Include) program "/1WDA/CBUSINESS_GRAPHICS======CCIMP".
The termination is caused because exception "CX_SY_REF_IS_INITIAL" occurred in
procedure "IF_NW7_VIEW_ELEMENT_ADAPTER~SET_CONTENT" "(METHOD)", but it was
neither handled locally nor declared
in the RAISING clause of its signature.
The procedure is in program "/1WDA/CBUSINESS_GRAPHICS======CP "; its source
code begins in line
390 of the (Include program "/1WDA/CBUSINESS_GRAPHICS======CCIMP ".
Thanks
ABAPer -
Short dump while creating a plant.
Dear experts,
Iam getting a short dump whenever I try to create a plant and save it. Iam posting the contents of the dump ... Iam using Ecc 6.0 with Oracle as database. Kindly help me to resolve this ...
Runtime Errors RAISE_EXCEPTION
Date and Time 27.10.2007 17:10:59
Short text
Exception condition "DATA_INCONS_IN_EXIT_MANAGEM" raised.
What happened?
The current ABAP/4 program encountered an unexpected
situation.
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
A RAISE statement in the program "CL_EXITHANDLER================CP" raised the
exception
condition "DATA_INCONS_IN_EXIT_MANAGEM".
Since the exception was not intercepted by a superior
program, processing was terminated.
Short description of exception condition:
For detailed documentation of the exception condition, use
Transaction SE37 (Function Library). You can take the called
function module from the display of active calls.
How to correct the error
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:
"RAISE_EXCEPTION" " "
"CL_EXITHANDLER================CP" or "CL_EXITHANDLER================CM001"
"GET_INSTANCE"
or
"CL_EXITHANDLER================CP" "DATA_INCONS_IN_EXIT_MANAGEM"
or
"SAPLS_IMG_TOOL_5 " "DATA_INCONS_IN_EXIT_MANAGEM"
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
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
System environment
SAP-Release 700
Application server... "BSLERP"
Network address...... "10.60.0.30"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "4x Intel 801586"
Character length.... 16 Bits
Pointer length....... 32 Bits
Work process number.. 0
Shortdump setting.... "full"
Database server... "BSLERP"
Database type..... "ORACLE"
Database name..... "BTS"
Database user ID.. "SAPSR3"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Apr 2 2006 23:08:16"
create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version. "OCI_10103_SHARE "
Patch level. 52
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
Memory consumption
Roll.... 8176
EM...... 17768808
Heap.... 0
Page.... 65536
MM Used. 12293456
MM Free. 1291704
User and Transaction
Client.............. 800
User................ "MURTHYTSN"
Language key........ "E"
Transaction......... "SPRO "
Program............. "CL_EXITHANDLER================CP"
Screen.............. "SAPLSZA1 0201"
Screen line......... 70
Information on where terminated
Termination occurred in the ABAP program "CL_EXITHANDLER================CP" -
in "GET_INSTANCE".
The main program was "SAPLS_IMG_TOOL_5 ".
In the source code you have the termination point in line 36
of the (Include) program "CL_EXITHANDLER================CM001".
Source Code Extract
Line
SourceCde
6
type_ref TYPE REF TO cl_abap_typedescr,
7
class_name TYPE seoclsname,
8
abs_type_classname TYPE string,
9
def_impl TYPE seex_boolean VALUE seex_false,
10
mig_enhspotname TYPE enhspotname,
11
is_impl TYPE enhboolean,
12
mig_badi_name TYPE enhbadiid.
13
14
CALL METHOD cl_exithandler=>get_class_name_by_interface
15
EXPORTING
16
instance = instance
17
IMPORTING
18
class_name = class_name
19
CHANGING
20
exit_name = exit_name
21
EXCEPTIONS
22
no_reference = 1
23
no_interface_reference = 2
24
no_exit_interface = 3
25
data_incons_in_exit_managem = 4
26
class_not_implement_interface = 5
27
OTHERS = 6.
28
CASE sy-subrc.
29
WHEN 1.
30
RAISE no_reference.
31
WHEN 2.
32
RAISE no_interface_reference.
33
WHEN 3.
34
RAISE no_exit_interface.
35
WHEN 4.
>>>>>
RAISE data_incons_in_exit_managem.
37
WHEN 5.
38
RAISE class_not_implement_interface.
39
ENDCASE.
40
41
CONCATENATE '\CLASS=' class_name INTO abs_type_classname.
42
43
Is the given instance initial?
44
IF NOT instance IS INITIAL.
45
CALL METHOD cl_abap_typedescr=>describe_by_object_ref
46
EXPORTING
47
p_object_ref = instance
48
RECEIVING
49
p_descr_ref = type_ref.
50
CHECK type_ref->absolute_name NE abs_type_classname.
51
ENDIF.
52
53
SELECT SINGLE mig_enhspotname mig_badi_name FROM sxs_attr INTO (mig_enhspotname,mig_badi_n
54
WHERE exit_name = exit_name.
55
Contents of system fields
Name
Val.
SY-SUBRC
4
SY-INDEX
1
SY-TABIX
0
SY-DBCNT
0
SY-FDPOS
0
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
ADDR0200
SY-UCOMM
CHCK
SY-TITLE
Edit address: 5002
SY-MSGTY
SY-MSGID
SY-MSGNO
000
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO
0
SY-DATUM
20071024
SY-UZEIT
171059
SY-XPROG
SAPCNVE
SY-XFORM
CONVERSION_EXIT
Active Calls/Events
No. Ty. Program Include Line
Name
43 METHOD CL_EXITHANDLER================CP CL_EXITHANDLER================CM001 36
CL_EXITHANDLER=>GET_INSTANCE
42 FUNCTION SAPLXSZAR ZXSZARU01 25
EXIT_SAPLSZAR_001
41 FUNCTION SAPLSZAR LSZARU01 108
ADDR_REGIONAL_DATA_CHECK
40 FORM SAPLSZA2 LSZA2F20 382
CHECK_ADDR1_DATA
39 FUNCTION SAPLSZA2 LSZA2U02 42
ADDR_CHECK
38 FUNCTION SAPLSZA0 LSZA0U01 79
ADDR_INSERT
37 FORM SAPLSZA1 LSZA1F22 1886
INSERT_ADDRESS_INTO_MEMORY
36 FORM SAPLSZA1 LSZA1F22 2234
PUT_ADDRESS_TO_MEMORY
35 FORM SAPLSZA1 LSZA1I02 409
D0100_OK_CODE
34 FORM SAPLSZA1 LSZA1F03 17
D0100_OK_CODE_WRAPPER
33 MODULE (PAI) SAPLSZA1 LSZA1I02 13
D0100_OK_CODE
32 FUNCTION SAPLSZA1 LSZA1U01 200
ADDR_DIALOG_INTERN
31 FUNCTION SAPLSZA1 LSZA1U05 177
ADDR_DIALOG
30 FORM SAPL0ORG LSVIMF24 292
ADDRESS_MAINTAIN
29 FORM SAPL0ORG LSVIMFX2 577
DETAIL_PAI
28 MODULE (PAI) SAPL0ORG LSVIMIXX 354
DETAIL_PAI
27 FORM SAPL0ORG LSVIMF2L 337
CALL_DYNPRO
26 FUNCTION SAPL0ORG L0ORGU34 35
VIEWPROC_V_T001W
25 FUNCTION SAPL0ORG L0ORGU33 49
VIEWFRAME_V_T001W
24 FUNCTION SAPLSVIM LSVIMU01 138
VIEW_MAINTENANCE
23 FUNCTION SAPLSVIM LSVIMU03 427
VIEW_MAINTENANCE_CALL
22 FORM SAPLS_CUS_ACTIVITY LS_CUS_ACTIVITYF01 358
START_SELECTED_TRANSACTION
21 MODULE (PAI) SAPLDSYH LDSYHI12 56
D1200_PAI_MODULE
20 FUNCTION SAPLDSYH LDSYHU11 70
OUTLINE_LIST_TCODES
19 FUNCTION SAPLS_CUS_ACTIVITY LS_CUS_ACTIVITYU07 103
S_CUS_ACTIVITY_EXECUTE
18 FUNCTION SAPLS_CUS_IMG_ACTIVITY LS_CUS_IMG_ACTIVITYU04 35
S_CUS_IMG_ACTIVITY_EXECUTE
17 FUNCTION SAPLS_IMG_TOOL_1 LS_IMG_TOOL_1U02 63
STREE_EXIT_TO_OBJECT_COBJ
16 FUNCTION SAPLSHI1 LSHI1U16 120
STREE_EXIT_TO_OBJECT
15 FORM SAPLSHI01 LSHI01F0Y 185
EXIT_TO_OBJECT_HC
14 FORM SAPLSHI01 LSHI01F05 70
HANDLE_LINK_CLICK
13 METHOD SAPLSHI01 LSHI01CI1 25
LCL_APPLICATION=>HANDLE_LINK_CLICK
12 METHOD CL_ITEM_TREE_CONTROL==========CP CL_ITEM_TREE_CONTROL==========CM013 53
CL_ITEM_TREE_CONTROL=>HANDLE_NODE_KEY_ITEM_NAME_EVT
11 METHOD CL_ITEM_TREE_CONTROL==========CP CL_ITEM_TREE_CONTROL==========CM00S 60
CL_ITEM_TREE_CONTROL=>HANDLE_EVENT
10 METHOD CL_GUI_COLUMN_TREE============CP CL_GUI_COLUMN_TREE============CM01O 15
CL_GUI_COLUMN_TREE=>HANDLE_EVENT
9 METHOD CL_TREE_CONTROL_BASE==========CP CL_TREE_CONTROL_BASE==========CM017 32
CL_TREE_CONTROL_BASE=>DISPATCH
8 METHOD CL_GUI_CFW====================CP CL_GUI_CFW====================CM001 138
CL_GUI_CFW=>DISPATCH
7 FORM SAPLSHI01 LSHI01F1M 17
EXECUTE_USER_COMMAND_W_EXITS
6 FUNCTION SAPLSHI01 LSHI01U12 30
STREE_BROWSER_PAI
5 MODULE (PAI) SAPLSHI01 LSHI01I01 55
PAI_200
4 FUNCTION SAPLSHI01 LSHI01U07 165
STREE_BROWSER_DYNP_HC
3 FUNCTION SAPLSHI21 LSHI21U03 144
STREE_EXTERNAL_DISPLAY
2 FORM SAPLS_IMG_TOOL_5 LS_IMG_TOOL_5F01 20
DISPLAY_REFERENCE_IMG
1 MODULE (PAI) SAPLS_IMG_TOOL_5 LS_IMG_TOOL_5I01 39
USER_COMMAND_0100
Chosen variables
Name
Val.
No. 43 Ty. METHOD
Name CL_EXITHANDLER=>GET_INSTANCE
EXIT_NAME
22222222222222222222
00000000000000000000
00000000000000000000
00000000000000000000
NULL_INSTANCE_ACCEPTED
2
0
0
0
ACT_IMP_EXISTING
2
0
0
0
INSTANCE
F0000000
F0000000
SY-REPID
CL_EXITHANDLER================CP
4454545444444533333333333333334522222222
3CF589481E4C52DDDDDDDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
%_SPACE
2
0
0
0
CL_DRAGDROP=>COPY
1
0000
1000
CL_WB_REQUEST=>TO_IMMEDIATE_START
SY-SUBRC
4
0000
4000
CL_DRAGDROP=>USEDEFAULTEFFECT
4
0000
4000
SYST-REPID
CL_EXITHANDLER================CP
4454545444444533333333333333334522222222
3CF589481E4C52DDDDDDDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
CL_GUI_CONTROL=>LIFETIME_DEFAULT
0
0000
0000
%_ARCHIVE
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
ABS_TYPE_CLASSNAME
No. 42 Ty. FUNCTION
Name EXIT_SAPLSZAR_001
IV_NATION
2
0
0
0
X_ACCEPT_ERROR
2
0
0
0
X_ADRC_STRUC
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
X_DIALOG_ALLOWED
X
5
8
0
0
Y_ADRC_STRUC
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Y_RETCODE
2
0
0
0
ERROR_TABLE[]
Table IT_2299[0x572]
\FUNCTION-POOL=SZA1\FORM=INSERT_ADDRESS_INTO_MEMORY\DATA=ERROR_TABLE[]
Table reference: 208
TABH+ 0(20) = 00000000F8EB2E3D00000000D0000000FB080000
TABH+ 20(20) = 000000003C020000FFFFFFFF04A90100303E0000
TABH+ 40( 8) = 10000000C1248001
store = 0x00000000
ext1 = 0xF8EB2E3D
shmId = 0 (0x00000000)
id = 208 (0xD0000000)
label = 2299 (0xFB080000)
fill = 0 (0x00000000)
leng = 572 (0x3C020000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000317
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = Not allocated
pghook = Not allocated
idxPtr = Not allocated
shmTabhSet = Not allocated
id = Not allocated
refCount = Not allocated
tstRefCount = Not allocated
lineAdmin = Not allocated
lineAlloc = Not allocated
shmVersId = Not allocated
shmRefCount = Not allocated
shmIsReadOnly = Not allocated
>>>>> 1st level extension part <<<<<
regHook = 0x00000000
collHook = 0x00000000
ext2 = 0xD09AD03C
>>>>> 2nd level extension part <<<<<
tabhBack = 0x30F18E3D
delta_head = 000000000000000000000000000000000000000000000000000000000000000000000000
pb_func = 0x00000000
pb_handle = 0x00000000
SY-XPROG
SAPCNVE
5454454222222222222222222222222222222222
3103E65000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
SY-XFORM
CONVERSION_EXIT
444545544454545222222222222222
3FE65239FEF5894000000000000000
000000000000000000000000000000
000000000000000000000000000000
%_VIASELSCR
0
4
%_SPACE
2
0
0
0
SY-REPID
SAPLXSZAR
5454555452222222222222222222222222222222
310C83A120000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
LR_EXIT
F0000000
F0000000
%_DUMMY$$
2222
0000
0000
0000
Y_ERROR_TABLE
Table[initial]
No. 41 Ty. FUNCTION
Name ADDR_REGIONAL_DATA_CHECK
IV_NATION
2
0
0
0
X_ACCEPT_ERROR
2
0
0
0
X_ADRC_STRUC
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
X_DIALOG_ALLOWED
X
5
8
0
0
X_T005
800IN IND064 ININD000 00 15500 4111 0000 00 436 664000INDIEN 000 1
3334424443332222222222224444433322233233333223333223333233233322222233333344444423332322222222
8009E09E40640000000000009E9E40000000001550000411100000000004360000006640009E495E00000100000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Y_ADRC_REGIO
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Y_ADRC_STRUC
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Y_RETCODE
2
0
0
0
ERROR_TABLE[]
Table IT_2299[0x572]
SY-XPROG
SAPCNVE
5454454222222222222222222222222222222222
3103E65000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
LV_MAND
C
422
300
000
000
SY-REPID
SAPLSZAR
5454554522222222222222222222222222222222
310C3A1200000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
%_SPACE
2
0
0
0
%_CX_GRID_ID
1
0000
1000
SYST-REPID
SAPLSZAR
5454554522222222222222222222222222222222
310C3A1200000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
SV_THERE_IS_CUST_EXIT
X
5
8
0
0
T005S
22222222222222
00000000000000
00000000000000
00000000000000
T005
00 000 00 00 00 00 0000 00 000 000
2222222223322222222222222222233322233233233222332223333233222222222222233322222223332222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
CO_ERROR
E
4
5
0
0
No. 40 Ty. FORM
Name CHECK_ADDR1_DATA
SY-MSGV3
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
SY-MSGV4
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
FIELDNAME
222222222222222222222222222222
000000000000000000000000000000
000000000000000000000000000000
000000000000000000000000000000
C_NULL
0
0000
0000
RETURNCODE_ERRORS
2
0
0
0
C_ERROR_OCCURRED
E
4
5
0
0
H_ADRC_STRUC+0(1800)
2020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
ADDR1_DATA+460(1800)
2020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
H_ADRC_STRUC
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
C_COMM_TTX
TTX
555
448
000
000
NATION
2
0
0
0
G_ACCEPT_ERROR
2
0
0
0
G_DIALOG_ALLOWED
X
5
8
0
0
T005
800IN IND064 ININD000 00 15500 4111 0000 00 436 664000INDIEN 000 1
3334424443332222222222224444433322233233333223333223333233233322222233333344444423332322222222
8009E09E40640000000000009E9E40000000001550000411100000000004360000006640009E495E00000100000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
TSAD6T
222222222222222222222222222222222222222222222222
000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000
ERROR_TABLE[]
Table IT_2299[0x572]
%_SPACE
2
0
0
0
No. 39 Ty. FUNCTION
Name ADDR_CHECK
ADDRESS_HANDLE
8005002
3333333222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
8005002000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
ADDRESS_NUMBER
2222222222
0000000000
0000000000
0000000000
ADDRESS_OBJECT_TYPE
1
3
1
0
0
NATION
2
0
0
0
RETURNCODE
2
0
0
0
ERROR_TABLE[]
Table IT_2299[0x572]
ADDRESS_DATA_1
00000000000000000003XYZ SOLUTIONS LIMITED
3333333333333333333355525445544452444454422222222222222222222222222222222222222222222222222222
0000000000000000000389A03FC549FE30C9D945400000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
ADDRESS_DATA_2
0000000000000000
3333333333333333222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
ADDRESS_DATA_3
0000000000000000
3333333333333333222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
LV_ADRC_STRUC+0(1800)
2020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
ADDRESS_DATA_1+460(1800)
2020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
C_DEFAULT_HANDLE
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SYST-REPID
SAPLSZA2
5454554322222222222222222222222222222222
310C3A1200000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
ERROR_TABLE
000
2222222222222222222223332222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
LV_ADRC_STRUC
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
C_DEFAULT_NATION
2
0
0
0
C_SHOW_ALL
2
0
0
0
C_PERSONAL_ADDRESS
2
3
2
0
0
SY-REPID
SAPLSZA2
5454554322222222222222222222222222222222
310C3A1200000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
ADDRESS_DATA_2+32(1800)
2020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
No. 38 Ty. FUNCTION
Name ADDR_INSERTDear Sunil,
Thanks a lot for your reply. I did search in service market place for notes regarding this problem. However, i could not find possible solutions to resolve this. I will once again search the notes in case if i have missed something. in case, if you come across any solutions to resolve this problem, Kindly post that here and that would be a great help for me.
Regards,
Chaitanya
Maybe you are looking for
-
No data Found the whole report is suppressed
<p>Hello, </p><p>I am trying to create a report with two commands (without link) Command1 would have data in any circumstance as it has the report information (e.g title etc.,) which is stored in database. </p><p>Command2 data is dependent on the p
-
Getting error in my device while signing up to ICloud. The same ID's is working well in downloading itunes
-
Deletion and Creation of storage location.
Dear Experts, Plz advise how can we un-assign any storage location from any material & how can we create the new storage location. Regards Sumit Kalyan
-
Is it possible to link two or more accounts without merging?
Is it possible to link two or more accounts without merging? For example: give access for apple id [email protected] (obviously fake and is used by John) to apple id [email protected] (also obviously fake and is used by Rose). This would only al
-
Activity - Questionnaire Details
Hello, I have an activity that has got a questionnaire attached with that. Is there a way i can find the linking tables between the Activity Number and Questionnaire Number ? Thanks Vathsan