Shared Memory Short Dump: SHMM ab_ShmResetLocks - anyone?

hello:)
I have a problem with shared memory area (SHMM) that dumps.
I have a tool that uses a shared memory area instance to store data.
When I run the tool and update the data stored in the instance, a short dump is thrown:
SYSTEM_SHM_AREA_OBSOLETE with the explanation:
An attempt was made to access a shared memory area that has already been
released. Possible reasons for release:
- explicit release from an ABAP program or from the shared objects
management transaction
- implicit release during resource shortages
The first one does not match, as I DO NOT explicitly release the instance of my area.
Moreover, ST22 shows me different parts of code every time, so my code is not the cause, or a specific part of code, or data that I shift.
The second one would probably be the cause.
But how can I avoid it?
Moreover, there in SM21(System Log) there is at this time, there is a runtime error, that says
ab_ShmResetLocks and nothing more:(
Shared Memory size is sufficient.
The Shared Memory Area Settings (SHMA) do not time out the read/write access(Lifetime: no entry and Automatic area structuring is set)
Any help is more than welcome, why i get the short dump!!
best regards
simon:)

Please check the following SAP notes:
[SAP Note 1105266 WDA: Runtime error SYSTEM_SHM_AREA_OBSOLETE|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bc_wd/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d31313035323636%7d]
Also check the below notes for related details.
Note 1322182 - Memory consumption of ABAP Shared Objects
[SAP Note 764187 SYSTEM_SHM_AREA_DETACHED runtime error|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bc_aba/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d373634313837%7d]
Please check the size of the shared memory object in the profile parameter abap/shared_objects_size_MB.
Regards,
Dipanjan

Similar Messages

Not enough memory short dump

I am investigating a performance problem with a SAP standard report. It falls over when trying to sort a table, the table size is [194994x294]. In know this is large but is it common for it to cause a EXSORT_NOT_ENOUGH_MEMORY short dump?

Hi,
Go to my computer and right click on it....
and go to properties.....
then go to advanced tab...
in it go to performance settings...
then go to advanced tab
in that go to virtual memory....in it click on change...
in change click on the radio button 'system managed size'
click on set and save it...
it might help you...
Regards
Debarshi

Short dump while extracting data

Hi,
When i extract the data from the datasource 2lis_05_item in rsa3 i m getting the following short dump. Can anyone tell what to do in this case?
Runtime Errors         CONNE_IMPORT_WRONG_STRUCTURE
Exceptn                CX_SY_IMPORT_MISMATCH_ERROR
Date and Time          06.12.2006 09:42:15
ShrtText
     Error when importing object "MC05Q00ITM_TAB".
What happened?
     Error in ABAP application program.
     The current ABAP program "SAPLMCEX" had to be terminated because one of t
     statements could not be executed.
     This is probably due to an error in the ABAP program.
     When attempting to import data, the
     structure of the complex object "MC05Q00ITM_TAB" was not compatible with
     target object.
Error analysis
     An exception occurred. This exception is dealt with in more detail below
     . The exception, which is assigned to the class 'CX_SY_IMPORT_MISMATCH_ER
      was neither
     caught nor passed along using a RAISING clause, in the procedure
      "MCEX_BW_LO_API" "(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:
     When attempting to import data, the structure of the complex object
      "MC05Q00ITM_TAB"
     was not compatible with the target object. The error occurred with
component no. 32.
sing RAISING Clause in Interface
Program                                 SAP
Include                                 LMC
Row                                     5
Module type                             (FU
Module Name                             MCE
gger Location of Exception
Program                                 SAP
Include                                 LMC
Row                                     241
Module type                             (FU
Module Name                             MCE
rce Code Extract
e SourceCde
11         endif.
12       enddo.
13     END-OF-DEFINITION.
14 ***** end macro *****

I suppose that you are doing enhancement to your datasource 2LIS_02_ITM
Have you done the following steps in the extractor:
1. Append the new field in MC02M_0ITM structure
2. Append the new field in MCEKPO structure
3. Use Tcode LBWE and expand the Purchsing to get 2LIS_02_ITM and click on the Datasource to uncheck the 'hide' and 'fields only'
4. Activate the data source, by using Tcode RSA5
3. After that I have make changes to the user-exit to add logic for the new field
Do remember to carry out the following steps before you modify the Extraction structure:
1. Make sure that the following steps are carried out at a time when no updates are performed so that no data is lost.
2. Start the update collective run directly from within the Customizing Cockpit. Up to PI(-A) 2001.2 , this collective run exclusively concerns the V3 update. As of PI(-A) 2002.1, depending on the update mode setting of the application, the collective run concerns either the V3 update or the update from the extraction queue ("Delta Queued", see Note 505700).
3. Load all data of the respective DataSource into the BW System.
Hope it helps.
regards
Vinod

Short Dump When activating BI Objects

Hi Experts,
When i try to activate any object ie., InfoObject, InfoCube, etc. it is moving to short dump. Can anyone please help in this issue, why it is going to short dump.
Thanks & Regards
Ramakrishna Kmaurthy

Hi Ramakrishna,
Can you please be more precise? What is the type of shortdump?
Shortdumps do not directly have to be a basis issue.
Please post the "subject" and the "short description" from the shortdump (ST22) in this thread.
Regards,
Steven Groot

Why do we call an ABAP Runtime error a "Short Dump"

Hi All,
I was just working on one of the ABAP runtime errors with my technical counterpart and a question came to my mind "Why do we call an ABAP Runtime error a "Short Dump"?".
I tried asking a few friends of mine working in the technical space in SAP and they were not able to answer.
So, some one of you experts help me getting answer to this question.
Thanks in Advance.
Nitin.

ABAP Runtime error is a generalized term .......... meaning the error occured while runtime.
wheare as short dump.
Short - means brief.
dump - error information from the memory
Short dumps (also called ABAP memory dumps). Short dumps occur when an ABAP program fails.
Short dumps provide basic information about which program failed and what the error was.
hope this helps.

Short dump when opening the segment builder

After the upgrade from CRM 4.0 to 2007, we are no longer able to open the Segment Builder. We always get a short dump (Message_type_X). Anyone encountered this problem before and has a solution?
Thanx in advance!

Hi,
though it is true that in CRM 2007 the GUI transactions should not be used anymore I am able to start the segment builder directly via transactioin CRMD_MKTSEG. It is working without a shortdump.
For documentation I suppose you have to refer to SAP: Help or the documentation available under service.sap.com. The blog posted here might be an alternative as well.
cheers Carsten

Short Dump TSV_TNEW_PAGE_ALLOC_FAILED while using shared memory objects

Hi Gurus,
We are using shared memory objects to stor some data which we will be reading later. I have implemented the interfce IF_SHM_BUILD_INSTANCE in root class and using its method BUILD for automatic area structuring.
Today our developments moved from dev system to quality system, and while writing the data into the shared memory using the methods ATTACH_FOR_WRITE and DETACH_COMMIT in one report. We started getting the run time error TSV_TNEW_PAGE_ALLOC_FAILED.This is raised when the method DETACH_COMMIT is called to commit the changes in the shared memory.
Everyhting works fine before DETACH_COMMIT. I know that it is happening since the program ran out of extended memory, but I am not sure why it is happening at DETACH_COMMIT call. If excessive memory is being used in the program, this run time error should have been raised while calling the ATTACH_FOR_WRITE method or while filling the root class attributes. I am not sure why it is happening at DETACH_COMMIT method.
Many Thanks in advance.
Thanks,
Raveesh

Hi raveesh,
as Naimesh suggested: Probably system parameter for shared memory area is too small. Compare the system parameters in devel and QA, check what other shared memory areas are used.
Regarding your question, why it does not fail at ATTACH_FOR_WRITE but then on DETACH_COMMIT:
Probably ATTACH_FOR_WRITE will set an exclusive write lock on the shared memory data, then write to some kind of 'rollback' memory and DETACH_COMMIT will really put the data into shared memory area and release the lock. The 'rollback' memory is in the LUW's work memory which is much bigger as the usual shared memory size.
This is my assumption - don't know who can verify or reject it.
Regards,
Clemens

Short dump due to Memory Space

Hi Experts,
I have an internal table whose width is 3576 characters. My selection criteria is selecting approximately 1 million record from the database table.
Out of the 3576 characters, I m not even filling 150 characters a row using selection fields.
The short dump is as follows:
Error analysis
    The internal table "\PROGRAM=ZPMWO_DSR_RECONCILIATION\FORM=RECONCILIATION\DATA=
    LT_VIQMEL_I" could not be further extended. To enable
    error handling, the table had to be delete before this log was written.
    As a result, the table is displayed further down or, if you branch to
    the ABAP Debugger, with 0 rows.
    At the time of the termination, the following data was determined for
    the relevant internal table:
    Memory location: "Session memory"
    Row width: 3576
    Number of rows: 1035860
    Allocated rows: 1035860
    Newly requested rows: 4 (in 1 blocks)
How to correct this?? I mean how do i increase the memory space required for this process??

Hi,
Check there is not an endless loop which is appending data in the internal table.
Regards,
Ankur Parab

Short Dump - GETWA_NOT_ASSIGNED - Flexible upload of RFD

Hi,
SEM 6.0 / BI 7.0
When i try to do a Flexible upload for a sample RFD, i get the following dump:
Runtime Errors         GETWA_NOT_ASSIGNED
Date and Time          11/25/2008 16:22:01
Short dump has not been completely stored (too big)
Short text
    Field symbol has not yet been assigned.
What happened?
    Error in the ABAP Application Program
    The current ABAP program "CL_UC_TASK_EXECUTION==========CP" had to be
     terminated because it has
    come across a statement that unfortunately cannot be executed.
Error analysis
    You attempted to access an unassigned field symbol
    (data segment 32776).
    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.
Trigger Location of Runtime Error
    Program                               CL_UC_TASK_EXECUTION==========CP
    Include                                 CL_UC_TASK_EXECUTION==========CM02V
    Row                                     155
    Module type                          (METHOD)
    Module Name                        COMPARE_OLD_AND_NEW_DOCS
Flexible upload - Delete all / Cumulative
Has anyone encountered this type of dump before?
My Observation
(Data Rows contain the following columns - Item / Company / Trading partner / PV LC)
When i give a trading partner which is not defined in the system, the system is interpreting the header row & data rows. Also, it gives an error message for each row.
But,
When i give a trading partner which is defined in the system, or when i remove the trading partner column in total, it throws the above short dump.
The breakdown category defined in the system are Trading partner & Movement type.
Both, have the breakdown type 1. (optional breakdown, initialized value allowed).
Pls note that after several permutations & combinations - to trace the error, i have removed all the columns & kept the minimum required (Item / Company / Trading partner / PV LC).
Appreciate your comments / inputs.
Thanks!
Kumar

Hi Kumar,
The note refers to FINBASIS 300 release.
In the present system we have, it is FINBASIS 600.
I raised an OSS message.
Anyway, implementation of the note helped me with all releases.
But, first of all, I mentioned another remedy that you may see here:
SPRO: SEM/Business Analytics -> Fin. Basis -> Master Data Framework -> System Settings -> Profile Parameter Setting.
It's about setting parameter for ABAP shared memory on the server. If you do not set this parameter to 200-300 MB, you constantly will have the errors like I mentioned while trying to save master data. Did you read my previous message carefully and look at this hint?
In case of breakdown type 1 - the upload should happen - if we dont specify any values for the breakdown category. Pls confirm.
- Confirmation. The system will accept any value, including null.
Is it true that we cannot load RFD data (with both movement type & trading partner information), in one go? If yes, what is the reason behind it.
- No confirmation. Where is it from? I always do such a load.

Shared Memory

Hi to all
I'm just developing an application in BSP. I wanted to use a Shared Memory (new futures in ABAP) as my data container (I would like to avoid statefuul application). The problem which I have at the moment is, when I'm trying to set any data which is object I have each tiem Short dump (it is comming from method CL_SHM_AREA->detach_commit).
Is anyone has any experience with data type object and SHM? Can someone help me to solve this problem?
regards
Olgeird

People have good reason to have low opinions of older implementations of shared memory. The mini don't use those old implementations of video.
My impression after using my mini for a week with both a 20" Cinema Display and a 26" Sony HDTV is that Intel did a fabulous job with this chip set and Apple did a fabulous job making it's programs fly on that chip set.
We're talking as fast as most G5 PowerMac - dual CPU - with lots of dedicated VRAM and PCI-X interface for typical tasks. (I don't do 3D gaming, don't render pro video, I do take Raw and 6Mega Pixel pictures and expect iMovie/iDVD/iPhoto to fly when I tax them with normal challenging amounts of data.)
There are some tasks where my G5 blows away my new mini - but for day to day tasks, there is little difference in how fast they "feel" when sitting at the keyboard and mouse.

Short Dump while executing New Hire (action type) in PA40

Hi All,
i am getting short dump while executing PA40 for new hire action type can anyone look into this and guide as i am new to HCM.
Category               ABAP Programming Error
Runtime Errors         SYNTAX_ERROR
ABAP Program           /1PAPAXX/HDR_21000A
Application Component Not Assigned
Date and Time          21.08.2014 14:07:03
Short text
    Syntax error in program "/1PAPAXX/HDR_21000A ".
What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPFP50M" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
    The following syntax error occurred in program "/1PAPAXX/HDR_21000A " in
    include "/1PAPAXX/HDR_21000AO01 " in
    line 52:
    ""LV_LENGTH" has already been declared"
    The include has been created and last changed by:
    Created by: "HCM04 "
    Last changed by: "HCM03 "
    Error in the ABAP Application Program
    The current ABAP program "SAPFP50M" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
What can you do?
    Please eliminate the error by performing a syntax check
    (or an extended program check) on the program "/1PAPAXX/HDR_21000A ".
    You can also perform the syntax check from the ABAP Editor.
    If the problem persists, proceed as follows:
    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
    The following syntax error was found in the program /1PAPAXX/HDR_21000A :
    ""LV_LENGTH" has already been declared"
How to correct the error
    Probably the only way to eliminate the error is to correct the program.
    If you cannot solve the problem yourself 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..... 731
    SAP Basis Level. 0007
    Application server... "dc-ds-erp"
    Network address...... "172.16.23.111"
    Operating system..... "Linux"
    Release.............. "3.0.13-0.27-default"
    Hardware type........ "x86_64"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 1
    Shortdump setting.... "full"
    Database server... "dc-ds-erp"
    Database type..... "ORACLE"
    Database name..... "ECD"
    Database user ID.. "SAPSR3"
    Terminal.......... "NLC-HP"
    Char.set.... "C"
    SAP kernel....... 720
    created (date)... "Sep 14 2013 06:16:24"
    create on........ "Linux GNU SLES-11 x86_64 cc4.3.4 use-pr130820"
    Database version. "OCI_112, 11.2.0.3.0, V1, default"
    Patch level. 500
    Patch text.. " "
    Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*"
    SAP database version. 720
    Operating system..... "Linux 2.6, Linux 3"
    Memory consumption
    Roll.... 0
    EM...... 37708200
    Heap.... 0
    Page.... 106496
    MM Used. 4666776
    MM Free. 3709976
User and Transaction
    Client.............. 210
    User................ "HCM03"
    Language key........ "E"
    Transaction......... "PA40 "
    Transaction ID...... "53EF470299AB5D67E1000000AC10176F"
    EPP Whole Context ID.... "005056A301D11EE48A9D08B337F884E3"
    EPP Connection ID....... 00000000000000000000000000000000
    EPP Caller Counter...... 0
    Program............. "SAPFP50M"
    Screen.............. "MP000000 1000"
    Screen Line......... 3
    Debugger Active..... "none"
Information on where terminated
    Termination occurred in the ABAP program "SAPFP50M" - in
    "GET_HEADER_WITH_TCLAS".
    The main program was "MP000000 ".
    In the source code you have the termination point in line 146
    of the (Include) program "FP50MDHD".
Source Code Extract
Line
SourceCde
116
CALL FUNCTION 'HR_HEADER_GET'
117
      EXPORTING
118
           DHDID                    = FHD_HID
119
           BEGDA                    = BEGDA
120
           TCLAS                    = TCLAS
121
* Es wird nur einer der folgenden 3 Parameter benutzt.
122
* Ausgewertet wird zunaechst MOLGA, dann P0001 dann PERNR.
123
* Der erste der nicht initial ist wird ausgewertet.
124
*           MOLGA                   =
125
           P0001                    = P0001
126
           PERNR                    = PSPAR-PERNR
127
      IMPORTING
128
           PROG                     = HEADER_PROG
129
           DNUM                     = HEADER_DYNNR
130
       EXCEPTIONS
131
            HEADER_DEACTIVATED          = 1
132
            HEADER_UNKNOWN              = 2
133
            HEADER_GENERATE_DEACTIVATED = 3
134
            HEADER_GENERATE_FAILED      = 4
135
            INTERNAL_ERROR              = 5
136
            OTHERS                      = 6.
137
138
IF NOT SY-SUBRC IS INITIAL.
139
* Bei Problemen gibt's eben ein leeres Dynpro.
140
    HEADER_PROG = 'SAPMP50A'.
141
    HEADER_DYNNR = '0090'.
142
ELSE. " NOT sy-subrc IS INITIAL.                                   "
143
* Dann setzen wir jetzt auch noch das Datum fest.
144
    PERFORM HEADER_BEGDA_SET IN PROGRAM (HEADER_PROG) USING BEGDA.
145
* Und schalten auf Uebergabe der PERNR mit globalen Variablen.
>>>>>
    PERFORM HEADER_LAZY_ON IN PROGRAM (HEADER_PROG).
147
ENDIF. " (ELSE) NOT sy-subrc IS INITIAL.                           "
148
* Merken wie der Header heisst. Damit MPPERS00 sich erinnern kann.

Hi,
Error Log: Syntax error
""LV_LENGTH" has already been declared"
please check LV_LENGTH variable declaration.
It may be declared more once!

ST22 Short Dump STORAGE_PARAMETERS_WRONG_SET

Hi
We have a NW04 BW 350 system running on Windows 2003 32 Bit/MS SQL 2000 32 Bit.
When I go into RSA --> Monitoring --> PSA it says 'constructing administrators workbench' then fails with the short dump:
<b>STORAGE_PARAMETERS_WRONG_SET</b>
The shortdump reccommends increasing parameters abap/heap_area_dia and
abap/heap_area_nondia, I would have thought you would want to avoid using HEAP memory as this locks the memory into a single work process ?
Looking at the memory consumption in the shortdump :
<b>Memory usage.............
Roll..................... 1709536
EM....................... 108964960
Heap..................... 406948064
Page..................... 57344
MM Used.................. 495709152
MM Free.................. 17059832
SAP Release.............. "640"</b>
EM has only been used for about 100 MB, then it go's to HEAP memory.
Looking at ST02 the system has 4GB EM and only 1.7GB used at 42%, so why would the process only use 100 MB of EM?
ztta/roll_extension is set to default 2GB so it appears EM memory should be utilised more by the work process before going to HEAP memory.
What parameters affect the usage of EM before entering HEAP usage?
Thanks for any advice.

Dear friend
kindly see the folowing rsdb/ntab/entrycount     Number of nametab entries administrated     20000     30000
rsdb/ntab/ftabsize     Data area size for field description buffer     30000     60000
rsdb/ntab/irbdsize     Data area size for initial records buffer     6000     8000
rtbb/buffer_length     Size of single record table buffers     16383     60000
zcsa/table_buffer_area     Size of generic table buffer     64000000     120000000
zcsa/db_max_buftab     Directory entries in generic table buffer     5000     30000
zcsa/presentation_buffer_area     Size of the buffer allocated for screens     4400000     20000000
sap/bufdir_entries     Maximum number of entries in the presentation buffer     2000     10000
rsdb/obj/buffersize     Size of export/import buffer     4096     40000
rsdb/obj/max_objects     Max. no. of exporting/importing objects     2000     20000
Parameters     Description     Current value     Recommended value
em/initial_size_MB     Size of extended memory pool     4096     8192
em/global_area_MB     Size of SAP Extended Global Memory (see SAP Note 329021)     96     255
ztta/roll_area     Maximum roll area per user context     3000000     16773120
rdisp/PG_SHM     Paging buffer size in shared memory     8192     32768
Parameters     Description     Current value     Recommended value
rdisp/wp_ca_blk_no     Work process communication blocks     300     1000
rdisp/appc_ca_blk_no     Buffer size for CPI-C communications     100     2000
gw/max_conn     Max. number of active connections     500     2000
rdisp/tm_max_no     Max. number of entries in array tm_adm     200     2000
rdisp/max_comm_entries     Max. number of communication entries     500     2000
gw/max_overflow_size     Max. swap space for CPIC-requests in the gateway     5000000     100000000
gw/max_sys     Max. number of connected clients     300     1000
shailesh

Dbx rtc shared memory check

Hi!
There are two programs (server + client ) which are interconnected via shared mem.
When Im trying to check client program with dbx( -C and check -access ), server is always dumping core in protocol classes of shmem and client is hanging on handshaking procedure. Is there is any way to disable DBX RTC(access checks ) to put traps or mark somehow the shared memory which is used by client program ?

Hi Leonard!
Threre is the problem with sources and stuff for server binary - it is "third side" software with no syms at all. so the core file is quite useless.
Ive found out the way to run correctly with server and mem access check - it is all about servers parameters about places(addr + page size rounding) of shmem and also Ive figured out another problem - there is an errors in server logs for semaphors and shmem lock calls. It looks like dbx is trapping whole mmap area from client.
Im still on investigation so I will post any usefull results here.
btw, skippatch is working quite strange actually...
Here is an example:
%dbx -C ./some_binary
(dbx)modules > ./loaded_modules
do some preparation stuff with output files so the file should looks like this( Ive ran with sed ):
rtc skippatch wait3.o
rtc skippatch wait4.o
rtc skippatch waitid.o
rtc skippatch waitpid.o
rtc skippatch walkstack.o
(dbx)check -access
(dbx) <copy/paste prepared file >
(dbx)run
theoretically, RTC should not work at all just because generated and pasted file contains all objects and librarys which is used by target binary.
but actually, RTC is patching and working as usual.
ps. 5.10 Generic_138888-01 sun4u sparc SUNW,Netra-T12 with dbx 7.7 ( from sunstudio 12.1 ).
pps. Ive read your short HOWTO about DBX RTC usage from the blog - very useful! Tommorow I will try to go with LD_AUDIT option.

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_INSERT

Dear 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

Short Dump on BAPI_TRANSACTION_COMMIT with destination NONE

Hi All
I am using SAP-PM with Compatible Unit(CU) functionality in ECC6 environment.
After we release the CU design to Generate order we get SHORT DUMP.
Any help will be of great help.
I am pasting the details from the dump file here.
Please let me know.
Appretaite your help.
Thanks
Meghana
Runtime Errors         CALL_FUNCTION_REMOTE_ERROR
Date and Time          27.08.2007 18:01:10
Short text
"The current application triggered a termination with a short dump."
What happened?
Error in the ABAP Application Program
The current ABAP program "/***/SAPLCUORDER_N" had to be terminated because it
has
come across a statement that unfortunately cannot be executed.
The error occurred during an RFC call to another system.
In the target system, a short dump has been written as well.
More detailed information on the error cause can be found there.
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 error occurred when executing a REMOTE FUNCTION CALL.
It was logged under the name "MESSAGE_TYPE_X"
on the called page.
How to correct the error
Please refer to the notes described in the
short dump.
System environment
SAP-Release 700
Application server... "MB1ES1005"
Network address...... "10.191.97.206"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "2x Intel 801586"
Character length.... 16 Bits
Pointer length....... 32 Bits
Work process number.. 3
Shortdump setting.... "full"
Database server... "MB1ES1005"
Database type..... "ORACLE"
Database name..... "EC6"
Database user ID.. "SAPSR3"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Jul 25 2007 00:57:05"
create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version. "OCI_10201_SHARE (10.2.0.1.0) "
Patch level. 121
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, Windows
NT 6.0"
Memory consumption
Roll.... 8176
EM...... 14633136
Heap.... 0
Page.... 131072
MM Used. 5005432
MM Free. 1263944
User and Transaction
Client.............. 200
User................ 10086330
Language key........ "E"
Transaction......... "/***/DESIGN "
Transactions ID..... "409954DC5D77F1C58E2D0013725D3B3B"
Program............. "/***/SAPLCUORDER_N"
Screen.............. "/***/SAPLCUORDER_N 2000"
Screen line......... 34
Information on where terminated
Termination occurred in the ABAP program "/***/SAPLCUORDER_N" - in
"SAVE_DESIGN".
The main program was "/***/SAPLCUORDER_N ".
In the source code you have the termination point in line 594
of the (Include) program "/***/LCUORDER_NF07".
Source Code Extract
Line
SourceCde
564
ENDIF .
565
ENDLOOP .
566
IF l_ret-type = 'E' OR
567
l_ret-type = 'A' .
568
CLEAR: save_okcode .
569
570
Show Messages
571
CALL FUNCTION '/***/N_LOG_ADD_MSG'
572
EXPORTING
573
i_log_type = 'G'
574
TABLES
575
t_ret      = t_ret.
576
PERFORM log_order_create_show .
577
Show first Message
578
     MESSAGE ID l_ret-id TYPE l_ret-type NUMBER l_ret-number
579
     WITH
580
       l_ret-message_v1 l_ret-message_v2
581
       l_ret-message_v3 l_ret-message_v4.
582
CALL FUNCTION '/***/N_DESIGN_INIT' .
583
ELSE .
584
IF g_design_mode = con_mode_crea.
585
Need to update DMS documents with real design number
586
PERFORM document_prepare_002 USING con_desnum_tmp_1
587
lv_desnum.
588
ENDIF.
589
Commit design BAPI's
590
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT' .
591
592
IF save_okcode = con_order.
593
Commit order BAPI's
>>>>>
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
595
DESTINATION 'NONE'.
596
597
call of fct. RFC_CONNECTION_CLOSE is important to get a new
598
initial roll area with initial internal tables next time
599
CALL FUNCTION 'RFC_CONNECTION_CLOSE'
600
EXPORTING
601
destination          = 'NONE'
602
EXCEPTIONS
603
destination_not_open = 1
604
OTHERS               = 2.
605
ENDIF.
606
607
IF lv_desnum IS INITIAL .
608
lv_desnum = /***/cudesign-desnum .
609
ENDIF .
610
SET PARAMETER ID '/***/DESNUM' FIELD lv_desnum .
611
    Changes saved
612
MESSAGE ID '/***/MSG' TYPE 'S' NUMBER '529' WITH lv_desnum .
613
ENDIF .
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
0
SY-TABIX
1
SY-DBCNT
1
SY-FDPOS
0
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
2000
SY-UCOMM
CU01
SY-TITLE
Change Design: 50000109
SY-MSGTY
X
SY-MSGID
00
SY-MSGNO
341
SY-MSGV1
MESSAGE_TYPE_X
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO
0
SY-DATUM
20070827
SY-UZEIT
180110
SY-XPROG
SAPMSSY1
SY-XFORM
XAB_READ
Active Calls/Events
No.   Ty.          Program                             Include                             Line
Name
4 FORM         /***/SAPLCUORDER_N                  /***/LCUORDER_NF07                    594
SAVE_DESIGN
3 FORM         /***/SAPLCUORDER_N                  /***/LCUORDER_NF07                   2616
CHECK_AND_SAVE_F07
2 FORM         /***/SAPLCUORDER_N                  /***/LCUORDER_NF04                    311
USER_COMMAND_D2000
1 MODULE (PAI) /***/SAPLCUORDER_N                  /***/LCUORDER_NI05                     28
USER_COMMAND_2000
Chosen variables
Name
Val.
No.       4 Ty.          FORM
Name SAVE_DESIGN
%_DUMMY$$
2222
0000
0000
0000
CL_GUI_RESOURCES=>COL_TEXTAREA
31
1000
F000
G_DESIGN_MODE
R
5
2
0
0
CON_MODE_CREA
I
4
9
0
0
GT_NODE_CUI
Table[initial]
SY-REPID
/***/SAPLCUORDER_N
2454254544545445542222222222222222222222
F35DF310C35F2452FE0000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
CON_DESNUM_TMP_1
TM00000001CY
543333333345
4D0000000139
000000000000
000000000000
LV_DESNUM
222222222222
000000000000
000000000000
000000000000
SAVE_OKCODE
CU01
4533222222222222222222222222222222222222222222222222222222222222222222
3501000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
CON_ORDER
CU01
4533222222222222222222222222222222222222222222222222222222222222222222
3501000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
SY-XPROG
SAPMSSY1
5454555322222222222222222222222222222222
310D339100000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
CON_DELETE
LVMS
4545222222222222222222222222222222222222222222222222222222222222222222
C6D3000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
No.       3 Ty.          FORM
Name CHECK_AND_SAVE_F07
CL_GUI_ALV_GRID=>MC_MB_VIEW
&MB_VIEW
2445544522222222222222222222222222222222222222222222222222222222222222
6D2F695700000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
GT_OP
Table IT_303[2x1320]
PROGRAM=/***/SAPLCUORDER_NDATA=GT_OP
Table reference: 118
TABH+ 0(20) = 7039FC3C5824DB3C00000000760000002F010000
TABH+ 20(20) = 0200000028050000FFFFFFFF0400000030140000
TABH+ 40( 8) = 08000000C1308001
store        = 0x7039FC3C
ext1         = 0x5824DB3C
shmId        = 0     (0x00000000)
id           = 118   (0x76000000)
label        = 303   (0x2F010000)
fill         = 2     (0x02000000)
leng         = 1320 (0x28050000)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000093
occu         = 8     (0x08000000)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 8     (cmpManyEq)
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         = 0x2010FC3C
pgHook       = 0x00000000
idxPtr       = 0x00000000
shmTabhSet   = 0x00000000
id           = 234   (0xEA000000)
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 8     (0x08000000)
lineAlloc    = 8     (0x08000000)
shmVersId    = 0     (0x00000000)
shmRefCount = 1     (0x01000000)
>>>>> 1st level extension part <<<<<
regHook      = 0x60B7153D
collHook     = 0x00000000
ext2         = 0x1024DB3C
>>>>> 2nd level extension part <<<<<
tabhBack     = 0xE00FFC3C
delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func      = 0x00000000
pb_handle    = 0x00000000
G_BADI_PROGRAM
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
LOG_ERROR
2
0
0
0
CON_BUTT_DELETED
@11QDelete@
43355466676422222222222222222222222222222222
011C145C545000000000000000000000000000000000
00000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000
G_CU_EXIT_CU_EXPLODE
F0000000
F0000000
/***/CUDESIGN-OBJNR
CY00000000000000008835
4533333333333333333333
3900000000000000008835
0000000000000000000000
0000000000000000000000
CL_GUI_RESOURCES=>COL_TEXTAREA
31
1000
F000
G_SEC_COUNT
0
0000
0000
LV_UPD
X
5
8
0
0
%_SPACE
2
0
0
0
GS_ROW_NO
0.0.0.1.
0000
1000
0000
0000
SCREEN
/***/CUDESIGN-GLTRP
2454245445444244555222222222222222222222222222222222222222222222222222222222222222222222222222
F35DF3545397ED7C420000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SY-MSGID
00
33222222222222222222
00000000000000000000
00000000000000000000
00000000000000000000
SWO_%CONTAINER
000000000
2222222222222222222222222222222233333333322222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SPACE
2
0
0
0
SY-MSGNO
341
333
341
000
000
/***/CVCUI-CUTYP
2
0
0
0
SY-MSGV1
MESSAGE_TYPE_X
44554445555455222222222222222222222222222222222222
D533175F4905F8000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
SY-MSGV2
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
SY-MSGV3
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
SY-MSGV4
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
No.       2 Ty.          FORM
Name USER_COMMAND_D2000
/***/CVCUI
0.0.0.0.0.0.0.1.                                                                         000000
2220000000022222222222222222222222222222222222222222222222222222222222222222222222223333332222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SYST-REPID
/***/SAPLCUORDER_N
2454254544545445542222222222222222222222
F35DF310C35F2452FE0000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
CON_MODE_COPY
C
4
3
0
0
LT_BAPI_RETURN
Table IT_1778[2x1088]
PROGRAM=/***/SAPLCUORDER_NFORM=USER_COMMAND_D2000DATA=LT_BAPI_RETURN
Table reference: 310
TABH+ 0(20) = 8837083D407E1C3D0000000036010000F2060000
TABH+ 20(20) = 0200000040040000FFFFFFFF04000000F0170000
TABH+ 40( 8) = 08000000C1308101
store        = 0x8837083D
ext1         = 0x407E1C3D
shmId        = 0     (0x00000000)
id           = 310   (0x36010000)
label        = 1778 (0xF2060000)
fill         = 2     (0x02000000)
leng         = 1088 (0x40040000)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000113
occu         = 8     (0x08000000)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 8     (cmpManyEq)
occu0        = 1
groupCntl    = 0
rfc          = 1
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
isCtfyAble   = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0x50C6073D
pgHook       = 0x00000000
idxPtr       = 0x00000000
shmTabhSet   = 0x00000000
id           = 1534 (0xFE050000)
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 8     (0x08000000)
lineAlloc    = 8     (0x08000000)
shmVersId    = 0     (0x00000000)
shmRefCount = 1     (0x01000000)
>>>>> 1st level extension part <<<<<
regHook      = 0x00000000
collHook     = 0x00000000
ext2         = 0x6067033D
>>>>> 2nd level extension part <<<<<
tabhBack     = 0xE82F063D
delta_head   = 0000000000000000CF000000000000000400000020180000000000004D00430055004F000000000
pb_func      = 0x00000000
pb_handle    = 0x00000000
CON_MODE_ORDE
O
4
F
0
0
TGSBT
22222222222222222222222222222222222222
00000000000000000000000000000000000000
00000000000000000000000000000000000000
00000000000000000000000000000000000000
CL_GUI_RESOURCES=>COL_TEXTAREA
31
1000
F000
LS_NUMBERS-AUFNR_NEW
000001000677
333333333333
000001000677
000000000000
000000000000
T024I
200UT10100PG for Term & Comp
33355333335426672567622246672222222222222222
20054101000706F20452D0603FD00000000000000000
00000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000
LS_T399X
200UT10UM01                  X    INST 30UT01UT01
3335533543322222222222222222252222445522335533553322222222222222222222222222222222222222222222
20054105D01000000000000000000800009E3400305401540100000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
CON_VBKZ_U
U
5
5
0
0
/***/CU_ORDER_IO-DISP_FACTOR
2097152
0
0
LS_DESIGN
200########000050000109DDCY00000000000000008835PROFILE1 0001UT10UM0100220100MWH001
333D5FC807333333333333344453333333333333333333355444443223333553354333333333345433322222222222
200CDB1E02B00005000010944390000000000000000883502F69C5100000154105D0100220100D7800100000000000
000599F215300000000000000000000000000000000000000000000000000000000000000000000000000000000000
0004C91D3DB00000000000000000000000000000000000000000000000000000000000000000000000000000000000
/***/CUDESIGN
200########000050000109DDCY00000000000000008835PROFILE1 0001UT10UM0100220100MWH001
333D5FC807333333333333344453333333333333333333355444443223333553354333333333345433322222222222
200CDB1E02B00005000010944390000000000000000883502F69C5100000154105D0100220100D7800100000000000
000599F215300000000000000000000000000000000000000000000000000000000000000000000000000000000000
0004C91D3DB00000000000000000000000000000000000000000000000000000000000000000000000000000000000
G_DROP_COUNT
0
0000
0000
LS_DESIGN-DESNUM
000050000109
333333333333
000050000109
000000000000
000000000000
No.       1 Ty.          MODULE (PAI)
Name USER_COMMAND_2000
GT_SELTAB_INIT
Table[initial]
Internal notes
The termination was triggered in function "RfcExtendedReceive"
of the SAP kernel, in line 422 of the module
"//bas/700_REL/src/krn/rfc/abrfcrcv.c#4".
The internal operation just processed is "FUNC".
Internal mode was started at 20070827180011.
Status of connection:
RFC state: " "
RFC error text: "RFC_ERROR_SYSTEM_FAILURE"
CPI-C error text: "The current application triggered a termination with a short
dump."
Active Calls in SAP Kernel
Lines of C Stack in Kernel (Structure Differs on Each Platform)
SAP (R) - R/3(TM) Callstack, Version 1.0
Copyright (C) SAP AG. All rights reserved.
Callstack without Exception:
App       : disp+work.EXE (pid=26488)
When      : 8/27/2007 18:1:10.942
Threads   : 2
Computer Name       : MB1ES1005
User Name           : ec6adm
Number of Processors: 2
Processor Type: x86 Family 15 Model 4 Stepping 10
Windows Version     : 5.2 Current Build: 3790
State Dump for Thread Id 5e10
eax=000f93c0 ebx=0000042c ecx=00003118 edx=00000000 esi=0000042c edi=00000000
eip=7c82ed54 esp=056d71f0 ebp=056d7260 iopl=0         nv up ei ng nz ac po cy
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000             efl=00200297
function : KiFastSystemCallRet
7c82ed54 c3               ret
7c82ed55 8da42400000000   lea     esp,[esp]              ss:056d71f0=7c822124
7c82ed5c 8d642400         lea     esp,[esp]              ss:62bd5803=00000000
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
056d7260 77e6ba42 0000042c 0001d4c0 00000000 056d7298 ntdll!KiFastSystemCallRet
056d7274 0109504d 0000042c 0001d4c0 00000001 7c38b5c8 kernel32!WaitForSingleObject
056d7298 00582118 00582151 7c38b5c8 7c38b5c8 7c38b5c8 disp+work!NTDebugProcess (ntstcdbg.c (501))
056d729c 00582151 7c38b5c8 7c38b5c8 7c38b5c8 01e9b1b8 disp+work!NTStack (dptstack.c (1367))
056d72b8 00582185 7c38b5c8 00000000 008b7ec8 7c38b5c8 disp+work!CTrcStack2 (dptstack.c (352))
056d72c4 008b7ec8 7c38b5c8 00000000 005f0059 00330030 disp+work!CTrcStack (dptstack.c (182))
056d72e8 008bb39f 00711076 056d8018 056d7be8 00200020 disp+work!rabax_CStackSave [abrabax.c (7063)
056d7b90 009eca8b 020b9e4c 020b9e14 000001a6 5d88acf0 disp+work!ab_rabax (abrabax.c (1243))
056d7bcc 009ed19e 00000003 00711076 00000020 00000000 disp+work!rcv_message (abrfcrcv.c (422))
056d8068 009ed29d 00000003 00000000 00710c47 056d80c0 disp+work!RfcExtendedReceive [abrfcrcv.c (14
056d808c 00714873 00000003 00710c47 056d80c0 00711076 disp+work!ab_rfcreceive (abrfcrcv.c (59))
056d80e4 0071886b 2694a7c8 2694a7cc 2694a7cc 2694a7cc disp+work!jfunc_get (abfunc.c (5103))
056d89f4 007191d0 00000003 000000b4 00000000 05e8b7c0 disp+work!jfunc_nonstandard [abfunc.c (1655)
056dcfb0 006e3e2d 00000003 3ced8f90 00000000 056dd018 disp+work!ab_jfunc (abfunc.c (554))
056dd018 0081cb5e 00000000 3ced8f90 056dd164 3cedb514 disp+work!ab_extri (abextri.c (552))
056dd02c 00897dbd 00000000 3cedae46 005bf4cd 3ceda13c disp+work!ab_xevent (abrunt1.c (281))
056dd038 005bf4cd 3ceda13c 000000ea 3cedae46 00000000 disp+work!ab_dstep (abdynpro.c (492))
056dd164 005c25be 3ced8f90 3ced8f90 056dfc78 00000000 disp+work!dynpmcal (dymainstp.c (2398))
056dd178 005c1def 00000001 3ced8f90 00000003 056dfc78 disp+work!dynppai0 (dymainstp.c (1004))
056dd194 00595e69 3ced8f90 00000001 00000001 00000001 disp+work!dynprctl (dymainstp.c (360))
056dfcec 00490e06 00000004 0049d15f 00000004 01dadd00 disp+work!dynpen00 (dymain.c (1628))
056dfcf4 0049d15f 00000004 01dadd00 00000003 00000002 disp+work!Thdynpen00 (thxxhead.c (4773))
056dfee0 0049d6d6 00000001 00000000 00000000 00430000 disp+work!TskhLoop (thxxhead.c (4455))
056dff00 00421c36 00000000 00000000 7ffde000 056dff60 disp+work!ThStart (thxxhead.c (1173))
056dff14 00401080 00000003 05876980 00000001 00000000 disp+work!DpMain (dpxxdisp.c (1121))
056dff60 01242970 00000003 05876980 05877a10 01cce000 disp+work!nlsui_main (thxxanf.c (82))
056dffc0 77e523e5 00000000 00000000 7ffde000 8967f020 disp+work!wmainCRTStartup (crtexe.c (395))
056dfff0 00000000 0124282d 00000000 00905a4d 00000003 kernel32!IsProcessorFeaturePresent
State Dump for Thread Id 61fc
eax=00000000 ebx=00000103 ecx=0587a700 edx=02714360 esi=00000000 edi=00000000
eip=7c82ed54 esp=0799fec0 ebp=0799ff04 iopl=0         nv up ei pl zr na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000             efl=00000246
function : KiFastSystemCallRet
7c82ed54 c3               ret
7c82ed55 8da42400000000   lea     esp,[esp]              ss:0799fec0=7c821514
7c82ed5c 8d642400         lea     esp,[esp]              ss:64e9e4d3=00000000
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
0799ff04 0119030a 000006e0 00000000 00000000 0587a798 ntdll!KiFastSystemCallRet
0799ff84 7c349565 00000000 00000000 00000000 0587a700 disp+work!SigIMsgFunc (signt.c (610))
0799ffb8 77e6608b 0587a700 00000000 00000000 0587a700 MSVCR71!endthreadex
0799ffec 00000000 7c3494f6 0587a700 00000000 00000000 kernel32!GetModuleFileNameA
List of ABAP programs affected
Index
Typ
Program
Group
Date
Time
Size
Lang.
0
Prg
/***/SAPLCUORDER_N
0
10.08.2007
10:12:44
541696
E
1
Typ
/***/CUDESIGN
0
10.08.2007
10:05:19
7168
2
Typ
/***/CU_ORDER_IO
0
10.08.2007
09:53:38
4096
3
Typ
/***/DESTYPE
0
10.08.2007
10:05:21
2048
4
Typ
/***/PRF_ORD
0
10.08.2007
10:05:21
4096
5
Prg
SAPMSSYD
0
04.04.2007
10:28:36
21504
E
6
Prg
SAPFSYSCALLS
0
09.09.2004
14:18:32
8192
E
7
Typ
/***/G_CUST
0
10.08.2007
09:53:39
3072
8
Prg
/***/SAPLTABLES
8
10.08.2007
10:13:00
19456
E
9
Typ
/***/G_CHAR
0
10.08.2007
10:05:21
3072
10
Prg
SAPLCTCE
10
09.09.2004
14:18:34
9216
E
11
Typ
CABN
0
18.09.2001
10:02:26
12288
12
Prg
SAPLICON
12
04.04.2007
10:10:28
27648
E
13
Prg
%_CICON
12
07.02.2006
10:40:00
104448
E
14
Typ
ICONT
0
04.04.2007
10:10:08
2048
15
Typ
NRIV
0
02.04.1998
08:14:54
3072
16
Prg
SAPLBSVA
16
04.04.2007
14:47:00
296960
E
17
Typ
/***/CU_ORDER_S_OP_N
0
10.08.2007
09:53:39
14336
18
Prg
CL_GUI_CONTROL================CP
18
28.02.2005
21:03:09
112640
E
19
Prg
%_CCNTL
18
18.02.2005
14:15:08
15360
E
20
Typ
OBJ_RECORD
0
14.02.1998
08:30:43
2048
21
Prg
CL_GUI_OBJECT=================CP
21
05.07.2005
13:10:15
375808
E
22
Prg
CL_GUI_CFW====================CP
22
28.02.2005
21:03:09
172032
E
23
Prg
CL_GUI_PROPS_CONSUMER=========CP
23
18.02.2005
14:15:08
30720
E
24
Prg
SAPLTHFB
24
04.04.2007
13:24:38
390144
E
25
Typ
EUDB
0
06.11.2003
20:28:08
8192
26
Prg
SAPLSFES
26
08.08.2007
16:46:17
259072
E
27
Prg
SAPLSPLUGIN
27
09.09.2004
14:18:36
8192
E
28
Prg
SAPLSTTM

Yes even i find it strange. But there is no syntax error and the fact is that it was working 2 days back. Suddenly it has started giving us this dump.
The code is as follows.
Commit design BAPI's
      CALL FUNCTION 'BAPI_TRANSACTION_COMMIT' .
      IF save_okcode = con_order.
Commit order BAPI's
        CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
          DESTINATION 'NONE'.
Here con_order is CU01.
Please let me know if anybody has faced this problem earlier.
Thanks in Advance
Meghana

Shared Memory Short Dump: SHMM ab_ShmResetLocks - anyone?

Similar Messages

Maybe you are looking for