ABAP Dump : IW41 Transaction : PM Order confirmation save

Dear all .,
System - Upgraded ECC 6.0 ( from 4.6C)
Testing in QA .
Transaction - IW41 : Create PM Order Confirmation>Tick Final confirmation>saved
Runtime Errors         SYNTAX_ERROR
Date and Time          06.10.2007 16:41:09
Short text
     Syntax error in program "RMCX0013 ".
What happened?
     Error in the ABAP Application Program
     The current ABAP program "SAPLMCS0" had to be terminated because it has
     come across a statement that unfortunately cannot be executed.
     The following syntax error occurred in program "RMCX0013 " in include "RMCX0013
      " in
     line 0:
     "The program "RMCX0013" is not Unicode-compatible, according to its pro"
     "gram attributes."
     The include has been created and last changed by:
     Created by: "DDIC "
     Last changed by: "DDIC "
Please help
Thanks & Regards ., GSD

Hi Guruprasad,
RMCX0013 is generated by a LIS structure. I don't know what's the reason in detail, but I hope if you re-generate your LIS structures, this can be overcome.
RMCX0013 (or Forms in this program) will be called dynamically (see list of active programs in the dump). If the calling program is active for unicode-check and the called not, this leads to incompatibility.
Regards,
Clemens

Similar Messages

ABAP Dump when using Shift Related Confirmations in CO11N

Dear SAP Gurus,
We have activated business function LOG_PP_SRN_CONF for doing shift
related confirmations using T Code CO11N.
On entering the production order and operation number in CO11N, the
system proposes the actual data. Then we select the shift number.
If we try to change the selected shift again, the system gives an ABAP
dump - "OBJECTS_OBJREF_NOT_ASSIGNED" and exits the program.
Please suggest some SAP Note or other solution for the problem.
Thanks!
With Regards,
Nitin

Dear Prasobh,
Thanks for the quick reply.
I have checked the OSS Note - 1359966 as mentioned by you.
However, there are 2 things which make me feel that the note is not relevant to my scenario -
1. The note says that the confirmation profile for CO11N includes the detail area "0240-Quantities: Subdivided Quantities". I'm not using this detail area in my confirmation profile. Instead, I'm using the detail area "0200-Quantities: yield/scrap/rework/reason".
2. System may issue termination message COCF 000 when single-screen entry for the confirmation (CO11N) is called by another application such as the order information system (COOIS). However, I'm getting this dump when i run the T Code CO11N directly. Further, I don't get the termination message at all.
Please suggest.
With Regards,
Nitin

ABAP DUMP IN transaction TBI6.

Hi Experts,
I am getting short dump from transaction TBI6 when I give business partner and company code and check any of the check box below and save. It is giving dump.
Dump analysis is saying Read statement with not work in unicode.
This is standard program. Program name : SAPLBUSS.
Is there any patch to include for not giving the short dump
Can any one suggest how to solve this problem....

Search for an OSS note on <a href="http://service.sap.com">SAP MarketPlace</a>
Greetings,
Blag.

Regarding ABAP dump during time ticket confirmation.

Hi PP Gurus,
I'm getting an ABAP dump while doing time ticket confirmation for a process order using COR6N. The dump is coming only for one plant and all the plants are working fine.
The reason for dump is
The current application program detected a situation which really should not occur. Therefore, a termination with a short dump was triggered on purpose by the key word MESSAGE (type X).
I tried to analyze the dump and got OSS# 385830. But this note only talking about the conversion of message from A to X type. What should be the reason (configuration/product error) behind that?
If anybody came across the same, please comment on this
Thanks & Regards,
Abu Arbab

Hi,
Since this dump is happening only for a particular plant, compare the config set of this plant with the other plant which is working fine, you should be able to resolve it.
Alternatively, ask your abaper to analyze the dump in ST22 & he / she should be able to let you know the exact reason why the dump is occurring.
Regards,
Vivek

ABAP Dump in ME28

Hi All,
Now I Get an ABAP Dump on Transaction ME28 release of purchaseorder, Actually the reason for this dump comes from purchase order print out program in Transaction ME23N we made a custom program to print the purchaseorder and after taking the print prview while going backe we use the FM 'POPUP_TO_CONFIRM_STEP' for a confirmation for sending the mail all this things are working with out any problum in ME23N.
But my problum is that at the time of relesing the P.O using ME28 I get an abab dump while analaysing it i found that this error is duto the
Call Screen statement in FM 'POPUP_TO_CONFIRM_STEP' , reason is that call screen statement is not allowed at update task
please help me to solve this
Regards
Nausal

Hi,
there are some restrictions in some contexts. In your case the printing program is called in UPDATE TASK and you try to display screen. This is not possible. Hence you get that dump. So basically you can not display screen from that point when it is called from ME28. You need to find a better point to display your pop up window.
Cheers

Regarding EXPORT_COMPRESS_ERROR ABAP dump

Hello Experts,
In our BI System, we are getting EXPORT_COMPRESS_ERROR ABAP dump. And not able to find out any SAP notes regarding this dump.
Waiting for your kind response.
Runtime Errors         EXPORT_COMPRESS_ERROR
Date and Time          11.04.2008 16:40:42
Short text
Internal error when compressing data.
What happened?
Error in the SAP kernel.
The current ABAP "SAPLRSDRI_SERVICES" program had to be terminated because the
ABAP processor detected an internal system error.
In the EXPORT TO DATABASE statement, an internal error occurred
when compressing data.
What can you do?
Note which actions and input led to the error.
For further help in handling the problem, contact your SAP administrator
You can use the ABAP dump analysis transaction ST22 to view and manage
termination messages, in particular for long term reference.
Error analysis
There is an internal system error.
eliminated with ABAP/4.
Last error logged in SAP kernel
Component............ "EM"
Place................ "SAP-Server u962004s_P38_67 on host u962004s (wp 23)"
Version.............. 37
Error code........... 7
Error text........... "Warning: EM-Memory exhausted: Workprocess gets PRIV "
Description.......... " "
System call.......... " "
Module............... "emxx.c"
Line................. 1881
The error reported by the operating system is:
Error number..... " "
Error text....... " "
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:
"EXPORT_COMPRESS_ERROR" " "
"SAPLRSDRI_SERVICES" or "LRSDRI_SERVICESF01"
"DATA_WRAP_UC"
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... "u962004s"
Network address...... "10.200.230.110"
Operating system..... "HP-UX"
Release.............. "B.11.23"
Hardware type........ "ia64"
Character length.... 8 Bits
Pointer length....... 64 Bits
Work process number.. 23
Shortdump setting.... "full"
Database server... "u962004s"
Database type..... "ORACLE"
Database name..... "P38"
Database user ID.. "SAPP38"
Char.set.... "de_DE.iso88591"
SAP kernel....... 700
created (date)... "Dec 30 2007 21:06:56"
create on........ "HP-UX B.11.23 U ia64"
Database version. "OCI_102 (10.2.0.2.0) "
Patch level. 141
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "HP-UX B.11"
Memory consumption
Roll.... 6219104
EM...... 2291965488
Heap.... 2302579280
Page.... 16384
MM Used. 4399764848
MM Free. 194652624
User and Transaction
Client.............. 100
User................ "K59461"
Language Key........ "D"
Transaction......... " "
Transactions ID..... "47FF35AD14F65486E10000000AC8E66E"
Program............. "SAPLRSDRI_SERVICES"
Screen.............. "SAPMSSY1 3004"
Screen Line......... 2
Information on caller of Remote Function Call (RFC):
System.............. "P38"
Database Release.... 700
Kernel Release...... 700
Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
Call Type........... "asynchron with reply and non-transactional (emode 0,
imode 0)"
Inbound TID.........." "
Inbound Queue Name..." "
Outbound TID........." "
Outbound Queue Name.." "
Client.............. 100
User................ "K59461"
Transaction......... " "
Call Program........."SAPLZ_ZOP01_VCUBES"
Function Module..... "RSDRI_INFOPROV_READ_RFC"
Call Destination.... "NONE"
Source Server....... "u962004s_P38_67"
Source IP Address... "10.200.230.110"
Additional information on RFC logon:
Trusted Relationship " "
Logon Return Code... 0
Trusted Return Code. 0
Note: For releases < 4.0, information on the RFC caller are often
only partially available.
Information on where terminated
Termination occurred in the ABAP program "SAPLRSDRI_SERVICES" - in
"DATA_WRAP_UC".
The main program was "SAPMSSY1 ".
In the source code you have the termination point in line 194
of the (Include) program "LRSDRI_SERVICESF01".
Source Code Extract
Line
SourceCde
164
165
CLEAR: l_string.
166
167
CALL METHOD cl_abap_container_utilities=>fill_container_c
168
EXPORTING
169
im_value     = <l_s_data>
170
IMPORTING
171
ex_container = l_string.
172
173
PERFORM wrap_str_to_c255
174
USING    l_string
175
CHANGING e_t_outdata.
176
177
ENDLOOP.
178
179
ENDFORM.                    " data_wrap_std
180
181
*&      Form data_wrap_uc
182
183
      text
184
185
     -->P_I_T_DATA text
186
     <--P_E_OUTDATA_UC text
187
188
FORM data_wrap_uc
189
USING    i_t_data      TYPE STANDARD TABLE
190
i_compress    TYPE rs_bool
191
CHANGING e_outdata_uc TYPE xstring.
192
193
IF i_compress = rs_c_true.
>>>>>
EXPORT rsdri = i_t_data
195
TO DATA BUFFER e_outdata_uc
196
COMPRESSION ON.
197
ELSE.
198
EXPORT rsdri = i_t_data
199
TO DATA BUFFER e_outdata_uc
200
COMPRESSION OFF.
201
ENDIF.
202
203
IF sy-subrc <> 0.
204
   RAISE conversion_error.
205
ENDIF.
206
207
ENDFORM.                    " data_wrap_uc
208
209
210
FORM data_wrap_250
211
212
213
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
1
SY-TABIX
0
SY-DBCNT
1
SY-FDPOS
25
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
CPIC- und RFC-Steuerung
SY-MSGTY
E
SY-MSGID
BL
SY-MSGNO
209
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO
0
SY-DATUM
20080411
SY-UZEIT
163555
SY-XPROG
SAPLRSDRI
SY-XFORM
RSDRI_INFOPROV_READ_RFC
Active Calls/Events
No.   Ty.          Program                             Include                             Line
Name
7 FORM         SAPLRSDRI_SERVICES                  LRSDRI_SERVICESF01                    194
DATA_WRAP_UC
6 FUNCTION     SAPLRSDRI_SERVICES                  LRSDRI_SERVICESU04                     29
RSDRI_DATA_WRAP
5 FORM         GP49E5DYREKDNLT28VWMJJ5FAZY         GP49E5DYREKDNLT28VWMJJ5FAZY           199
INFOPROV_READ_RSDRI
4 FUNCTION     SAPLRSDRI                           LRSDRIU02                             153
RSDRI_INFOPROV_READ_RFC
3 FORM         SAPLRSDRI                           LRSDRIU02                               1
RSDRI_INFOPROV_READ_RFC
2 FORM         SAPMSSY1                            SAPMSSY1                               85
REMOTE_FUNCTION_CALL
1 MODULE (PBO) SAPMSSY1                            SAPMSSY1                               30
%_RFC_START
Chosen variables
Name
Val.
No.       7 Ty.          FORM
Name DATA_WRAP_UC
SYST-REPID
SAPLRSDRI_SERVICES
5454554545545544452222222222222222222222
310C23429F352693530000000000000000000000
I_COMPRESS
X
5
8
RS_C_TRUE
X
5
8
SY
###############################################################################À##############
0000000000000000000000000000000000000000000000010000000000000000000000000000000C00000000000000
0001000000000000000000000000000000000000000100090001000000010000000000000000002000000000000000
I_T_DATA
Table IT_4214[3004988x1456]
PROGRAM=GP49E5DYREKDNLT28VWMJJ5FAZYFORM=INFOPROV_READ_RSDRIDATA=L_T_DATA
Table reference: 245
TABH+ 0(20) = C0000005B3A98DB0000000000000000000000000
TABH+ 20(20) = 000000F500001076002DDA3C000005B0FFFFFFFF
TABH+ 40(16) = 0400002A00000B10000824C401800000
store        = 0xC0000005B3A98DB0
ext1         = 0x0000000000000000
shmId        = 0     (0x00000000)
id           = 245   (0x000000F5)
label        = 4214 (0x00001076)
fill         = 3004988 (0x002DDA3C)
leng         = 1456 (0x000005B0)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000040
occu         = 8     (0x00000008)
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         = 0xC0000009BB9B2090
pgHook       = 0x600000008EAEC160
idxPtr       = 0x0000000000000000
shmTabhSet   = 0x0000000000000000
id           = 3503 (0x00000DAF)
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 3014656 (0x002E0000)
lineAlloc    = 3004992 (0x002DDA40)
shmVersId    = 0     (0x00000000)
shmRefCount = 1     (0x00000001)
>>>>> 1st level extension part <<<<<
regHook      = Not allocated
collHook     = Not allocated
ext2         = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack     = Not allocated
delta_head   = Not allocated
pb_func      = Not allocated
pb_handle    = Not allocated
%_DUMMY$$
2222
0000
E_OUTDATA_UC
ÿ#######1100####ÒWÜ#####°ï6=³$Ç~ßsæ#ä5L#¼ -^##há#°#!&ß3#ð#ô#Á#p6##Òâ¬###Å#.À#6²aÀ#kÀ6´1ÀOp##ú#
F000008033330000D5D01190BE33B2C7D7E8E348BA25816E8B822D30F8F1C07321DEA019C12C93B6C86C3B3C4700F0
F61122001100000027C52FD20F6D347EF36545C1C0DE008100016F3B064D13063B22C59855E056210BB06410F019A0
SYST
###############################################################################À##############
0000000000000000000000000000000000000000000000010000000000000000000000000000000C00000000000000
0001000000000000000000000000000000000000000100090001000000010000000000000000002000000000000000
No.       6 Ty.          FUNCTION
Name RSDRI_DATA_WRAP
I_COMPRESS
X
5
8
I_RESULT250
2
0
I_T_DATA
Table IT_4214[3004988x1456]
I_UNICODE_RESULT
X
5
8
E_OUTDATA_UC
ÿ#######1100####ÒWÜ#####°ï6=³$Ç~ßsæ#ä5L#¼ -^##há#°#!&ß3#ð#ô#Á#p6##Òâ¬###Å#.À#6²aÀ#kÀ6´1ÀOp##ú#
F000008033330000D5D01190BE33B2C7D7E8E348BA25816E8B822D30F8F1C07321DEA019C12C93B6C86C3B3C4700F0
F61122001100000027C52FD20F6D347EF36545C1C0DE008100016F3B064D13063B22C59855E056210BB06410F019A0
E_T_OUTDATA
Table[initial]
E_T_OUTDATA250
Table[initial]
RS_C_FALSE
2
0
SY-REPID
SAPLRSDRI_SERVICES
5454554545545544452222222222222222222222
310C23429F352693530000000000000000000000
No.       5 Ty.          FORM
Name INFOPROV_READ_RSDRI
SY-SUBRC
0
0000
0000
SY-REPID
GP49E5DYREKDNLT28VWMJJ5FAZY
4533434554444453355444344552222222222222
7049554925B4EC42867DAA561A90000000000000
SY
###############################################################################À##############
0000000000000000000000000000000000000000000000010000000000000000000000000000000C00000000000000
0001000000000000000000000000000000000000000100090001000000010000000000000000002000000000000000
%_DUMMY$$
2222
0000
%_SPACE
2
0
SYST-REPID
GP49E5DYREKDNLT28VWMJJ5FAZY
4533434554444453355444344552222222222222
7049554925B4EC42867DAA561A90000000000000
I_OUTU
X
5
8
RS_C_TRUE
X
5
8
L_T_DATA
Table IT_4214[3004988x1456]
E_RFCOUT_UC
ÿ#######1100####ÒWÜ#####°ï6=³$Ç~ßsæ#ä5L#¼ -^##há#°#!&ß3#ð#ô#Á#p6##Òâ¬###Å#.À#6²aÀ#kÀ6´1ÀOp##ú#
F000008033330000D5D01190BE33B2C7D7E8E348BA25816E8B822D30F8F1C07321DEA019C12C93B6C86C3B3C4700F0
F61122001100000027C52FD20F6D347EF36545C1C0DE008100016F3B064D13063B22C59855E056210BB06410F019A0
I_S_RFCMODE
0.0.0.1.
22222222222222222222222222222222222222220000
00000000000000000000000000000000000000000000
I_S_RFCMODE-RFC_RECEIVER
222222222222222222222222222222
000000000000000000000000000000
E_EOD
X
5
8
I_S_RFCMODE-ID
2222222222
0000000000
No.       4 Ty.          FUNCTION
Name RSDRI_INFOPROV_READ_RFC
I_AUTHORITY_CHECK
R
5
2
I_CURRENCY_CONVERSION
X
5
8
I_DEBUG
2
0
I_FILENAME
222222222222222222222222222222222222222222222222222222222222
000000000000000000000000000000000000000000000000000000000000
I_INFOPROV
B100_CB3E
433354434222222222222222222222
2100F3235000000000000000000000
I_MAXROWS
0
0000
0000
I_READ_ODS_DELTA
2
0
I_REFERENCE_DATE
20080411
33333333
20080411
I_RESULTTYPE
U
5
5
I_ROLLUP_ONLY
X
5
8
I_SAVE_IN_FILE
2
0
I_SAVE_IN_TABLE
2
0
I_S_RFCMODE
0.0.0.1.
22222222222222222222222222222222222222220000
00000000000000000000000000000000000000000000
I_TABLENAME
222222222222222222222222222222
000000000000000000000000000000
I_USE_AGGREGATES
X
5
8
I_USE_DB_AGGREGATION
X
5
8
E_AGGREGATE
B100_CB3E$X
433354434252222222222222222222
2100F3235480000000000000000000
E_END_OF_DATA
X
5
8
E_RFCDATA_UC
ÿ#######1100####ÒWÜ#####°ï6=³$Ç~ßsæ#ä5L#¼ -^##há#°#!&ß3#ð#ô#Á#p6##Òâ¬###Å#.À#6²aÀ#kÀ6´1ÀOp##ú#
F000008033330000D5D01190BE33B2C7D7E8E348BA25816E8B822D30F8F1C07321DEA019C12C93B6C86C3B3C4700F0
F61122001100000027C52FD20F6D347EF36545C1C0DE008100016F3B064D13063B22C59855E056210BB06410F019A0
E_SPLIT_OCCURRED
2
0
E_T_FIELD[]
Table IT_4[180x40]
FUNCTION-POOL=RSDRIFORM=RSDRI_INFOPROV_READ_RFCDATA=%_%_E_T_FIELD
Table reference: 4
TABH+ 0(20) = C0000005B3902040C0000005B38D281000000000
TABH+ 20(20) = 0000000400000004000000B400000028FFFFFFFF
TABH+ 40(16) = 0400000100000F700010249401800000
store        = 0xC0000005B3902040
ext1         = 0xC0000005B38D2810
shmId        = 0     (0x00000000)
id           = 4     (0x00000004)
label        = 4     (0x00000004)
fill         = 180   (0x000000B4)
leng         = 40    (0x00000028)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000060
occu         = 16    (0x00000010)
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         = 0xC0000005B39020A0
pgHook       = 0xC0000005B38FC770
idxPtr       = 0x0000000000000000
shmTabhSet   = 0x0000000000000000
id           = 16    (0x00000010)
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 304   (0x00000130)
lineAlloc    = 304   (0x00000130)
shmVersId    = 0     (0x00000000)
shmRefCount = 1     (0x00000001)
>>>>> 1st level extension part <<<<<
regHook      = 0x0000000000000000
collHook     = 0x0000000000000000
ext2         = 0xC0000005B38D27A0
>>>>> 2nd level extension part <<<<<
tabhBack     = 0xC0000005B38D2740
delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func      = 0x0000000000000000
pb_handle    = 0x0000000000000000
E_T_RFCDATA[]
Table IT_5[0x256]
FUNCTION-POOL=RSDRIFORM=RSDRI_INFOPROV_READ_RFCDATA=%_%_E_T_RFCDATA
Table reference: 5
TABH+ 0(20) = 0000000000000000C0000005B38D292000000000
TABH+ 20(20) = 00000005000000050000000000000100FFFFFFFF
TABH+ 40(16) = 0400000100000E580010249401800000
store        = 0x0000000000000000
ext1         = 0xC0000005B38D2920
shmId        = 0     (0x00000000)
id           = 5     (0x00000005)
label        = 5     (0x00000005)
fill         = 0     (0x00000000)
leng         = 256   (0x00000100)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000055
occu         = 16    (0x00000010)
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      = 0x0000000000000000
collHook     = 0x0000000000000000
ext2         = 0xC0000005B38D28B0
>>>>> 2nd level extension part <<<<<
tabhBack     = 0xC0000005B38D2850
delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func      = 0x0000000000000000
pb_handle    = 0x0000000000000000
E_T_RFCDATAV[]
Table IT_6[0x100]
FUNCTION-POOL=RSDRIFORM=RSDRI_INFOPROV_READ_RFCDATA=%_%_E_T_RFCDATAV
Table reference: 6
TABH+ 0(20) = 0000000000000000C0000005B38D2A3000000000
TABH+ 20(20) = 00000006000000060000000000000064FFFFFFFF
TABH+ 40(16) = 0400000100000F000010249401800000
store        = 0x0000000000000000
ext1         = 0xC0000005B38D2A30
shmId        = 0     (0x00000000)
id           = 6     (0x00000006)
label        = 6     (0x00000006)
fill         = 0     (0x00000000)
leng         = 100   (0x00000064)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000058
occu         = 16    (0x00000010)
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      = 0x0000000000000000
collHook     = 0x0000000000000000
ext2         = 0xC0000005B38D29C0
>>>>> 2nd level extension part <<<<<
tabhBack     = 0xC0000005B38D2960
delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func      = 0x0000000000000000
pb_handle    = 0x0000000000000000
I_T_RANGE[]
Table IT_0[24x153]
FUNCTION-POOL=RSDRIFORM=RSDRI_INFOPROV_READ_RFCDATA=%_%_I_T_RANGE
Table reference: 0
TABH+ 0(20) = C0000005B38C97E0C0000005B38C97A000000000
TABH+ 20(20) = 00000000000000000000001800000099FFFFFFFF
TABH+ 40(16) = 04000001000004B80010249421800000
store        = 0xC0000005B38C97E0
ext1         = 0xC0000005B38C97A0
shmId        = 0     (0x00000000)
id           = 0     (0x00000000)
label        = 0     (0x00000000)
fill         = 24    (0x00000018)
leng         = 153   (0x00000099)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000011
occu         = 16    (0x00000010)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 2     (cmpSingleMcmpR)
occu0        = 1
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 1
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
isCtfyAble   = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0xC0000005B38C9840
pgHook       = 0xC0000005B38CA1F0
idxPtr       = 0x0000000000000000
shmTabhSet   = 0x0000000000000000
id           = 2     (0x00000002)
refCount     = 1     (0x00000001)
tstRefCount = 0     (0x00000000)
lineAdmin    = 48    (0x00000030)
lineAlloc    = 48    (0x00000030)
shmVersId    = 0     (0x00000000)
shmRefCount = 3     (0x00000003)
>>>>> 1st level extension part <<<<<
regHook      = 0xC0000005B3AB3F70
collHook     = 0x0000000000000000
ext2         = 0xC0000005B38C9730
>>>>> 2nd level extension part <<<<<
tabhBack     = 0xC0000005B38C96D0
delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func      = 0x0000000000000000
pb_handle    = 0x0000000000000000
I_T_REQUID[]
Table IT_7[0x12]
FUNCTION-POOL=RSDRIFORM=RSDRI_INFOPROV_READ_RFCDATA=%_%_I_T_REQUID
Table reference: 7
TABH+ 0(20) = 0000000000000000C0000005B38D2B4000000000
TABH+ 20(20) = 0000000700000007000000000000000CFFFFFFFF
TABH+ 40(16) = 04000001000006780010249401800000
store        = 0x0000000000000000
ext1         = 0xC0000005B38D2B40
shmId        = 0     (0x00000000)
id           = 7     (0x00000007)
label        = 7     (0x00000007)
fill         = 0     (0x00000000)
leng         = 12    (0x0000000C)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000019
occu         = 16    (0x00000010)
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      = 0x0000000000000000
collHook     = 0x0000000000000000
ext2         = 0xC0000005B38D2AD0
>>>>> 2nd level extension part <<<<<
tabhBack     = 0xC0000005B38D2A70
delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func      = 0x0000000000000000
pb_handle    = 0x0000000000000000
I_T_RTIME[]
Table IT_1[3x121]
FUNCTION-POOL=RSDRIFORM=RSDRI_INFOPROV_READ_RFCDATA=%_%_I_T_RTIME
Table reference: 1
TABH+ 0(20) = C0000005B38CB680C0000005B38CB64000000000
TABH+ 20(20) = 00000001000000010000000300000079FFFFFFFF
TABH+ 40(16) = 04000001000005980010249401800000
store        = 0xC0000005B38CB680
ext1         = 0xC0000005B38CB640
shmId        = 0     (0x00000000)
id           = 1     (0x00000001)
label        = 1     (0x00000001)
fill         = 3     (0x00000003)
leng         = 121   (0x00000079)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000015
occu         = 16    (0x00000010)
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         = 0xC0000005B38CB6E0
pgHook       = 0x0000000000000000
idxPtr       = 0x0000000000000000
shmTabhSet   = 0x0000000000000000
id           = 3     (0x00000003)
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 16    (0x00000010)
lineAlloc    = 16    (0x00000010)
shmVersId    = 0     (0x00000000)
shmRefCount = 1     (0x00000001)
>>>>> 1st level extension part <<<<<
regHook      = 0x0000000000000000
collHook     = 0x0000000000000000
ext2         = 0xC0000005B38CB5D0
>>>>> 2nd level extension part <<<<<
tabhBack     = 0xC0000005B38CB570
delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func      = 0x0000000000000000
pb_handle    = 0x0000000000000000
I_T_SFC[]
Table IT_2[17x52]
FUNCTION-POOL=RSDRIFORM=RSDRI_INFOPROV_READ_RFCDATA=%_%_I_T_SFC
Table reference: 2
TABH+ 0(20) = C0000005B38CBFA0C0000005B38CBF6000000000
TABH+ 20(20) = 00000002000000020000001100000034FFFFFFFF
TABH+ 40(16) = 0400000100000DB00010249401800000
store        = 0xC0000005B38CBFA0
ext1         = 0xC0000005B38CBF60
shmId        = 0     (0x00000000)
i

Hello,
did you resolve the problem ?
Please tell me how if it's resolved.
Best Regards

ABAP dump DDIC_TYPE_INCONSISTENCY

Hi Expert,
we are getting the below abap dump DDIC_TYPE_INCONSISTENCY frequently.
Runtime Errors         DDIC_TYPE_INCONSISTENCY
Date and Time          10.06.2008 12:11:34
What can you do?
     Note which actions and input led to the error.
     For further help in handling the problem, contact your SAP administrator
    You can use the ABAP dump analysis transaction ST22 to view and manage
     termination messages, in particular for long term reference.
Error analysis
     There is an internal system error.
     eliminated with ABAP/4.
How to correct the error
     The internal system error cannot be fixed by ABAP means only.
     You may be able to find a solution in the SAP note system. If you have
     access to the SAP note system, try searching for the following terms:
      "DDIC_TYPE_INCONSISTENCY" " "
      "SAPLMEACCTVI" or "LMEACCTVITOP"
     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:
     "DDIC_TYPE_INCONSISTENCY" " "
     "SAPLMEACCTVI" or "LMEACCTVITOP"
     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.
Please help me to fix this issue.
Thanks & Regards,
Reddy V

Hi Antoni,
Please note the below sm21 log
Details Page 2 Line 27 System Log: Local Analysis of UBSDEV                   1
Time     Type Nr   Clt   User   TCode   Grp N      Text
12:11:34 DIA   001 120 VSALI            AB 0       Run-time error   "DDIC_TYPE_INCONSISTENCY" occurred
Run-time error "DDIC_TYPE_INCONSISTENCY" occurred
Details
Recording at local and central time........................ 10.06.2008 12:11:34
Task...... Process                     User...... Terminal Session TCode Program Cl Problem cl          Package
29480      Dialog work process No. 001 VSALI      acerdev0       1               T Transaction Problem SABP
Further details for this message type
Module nam   Line     Error text
abucutil        1053 ab_RxDdicTypeError
Documentation for system log message AB 0 :
The specified runtime error has occurred in the system.
Parameter
abcdefghijklmnopqrstuvwxyz .. DDIC_TYPE_INCONSISTENCY
Technical details
File Offset   RecFm    System log type        Grp     N
40    319860   l            Error (Module, Row)    AB     0
variable message data
ab_RxDdicTypeError                                  abucutil1053
Regards,
Reddy V

ABAP DUMP:MEMORY LOW

Dear all,
While running a particular report ZMIS in my production server I am getting the following error.Well I also found this is coming for other reports also where we have to fetch data for 3-4 months.This is the dump I am getting
Note which actions and input led to the error.
For further help in handling the problem, contact your SAP administrator
You can use the ABAP dump analysis transaction ST22 to view and manage
termination messages, in particular for long term reference.
In the system profile, set the parameters
-abap/heap_area_dia and
-abap/heap_area_nondia
to a maximum of 1089891456. To be on the safe side, reduce the value by 10,000,
000.
Then restart the SAP system.
I had added abap/heap_area_dia and
-abap/heap_area_nondia profiles and set them to 2GB. Also I had increased my abap/buffersize from 300MB to 400MB and restarted the server,still dump is coming.
I have even reported the error to SAP as asked by our implementation partner. SAP asked us to send the memory parameter. I asked SAP to please specify the name of the memory parameter and still waiting for their reply. If you know what memory parameter they are asking me to send it would be a great help.I checked in RZ11 and there are aroung 500 parameter and I guess they want me send the default values of these parameters.
Please suggest..
Regards,
vicky
Edited by: vicky singh on Jun 16, 2008 7:57 AM
Edited by: vicky singh on Jun 16, 2008 7:59 AM

Dear Rahul,
Thnx for your reply.SAP said:
The issue here is not parameters as such, it is the fact that you run
your SAP system on a 32bit CPU and this is the result of a lack of
address space for the process because of the 32bit CPU you have, there are some things that you can possibly do to help.
Do you know what are address space and how to increase it..?
Our server are installed on 32bit CPU. Do I need to install my server on 64bit CPU or some alternative solution exists..?
Obviously I am waiting for SAP reply before doing anything and reinstalling server now is not possible.
Please share some views..
Regards,
Vicky

Abap dump error while release Production order

Dear Gurus,
Abap dump error is creating while release production order , pour some light on this issue.
Regards,
Kamal

Hello,
use transaction ST22 to analyze the error type. There you have the detail of the error message, the program and the line of the ABAP code where the dump was triggered.
Best regards,
Andrea

ABAP dump Error while creating service order in PCUI.

Hi Experts,
                 We are getting following ABAP dump error while creating service order in PCUI which is working fine in GUI.
Runtime Errors         RAISE_EXCEPTION
Date and Time          02.01.2008 14:55:38
Short text
Exception condition "TYPE_NOT_FOUND" 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_CRM_ELEMDESCR==============CP" raised the
exception
condition "TYPE_NOT_FOUND".
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.
We have added custom fields in the service application. these custom fields with Z-structure & data elements are included in BSP structure CRMT_BSP_SRV_OIC_SRCHRES in development system.But the same Z structure & custom fields are exist in the production system but not included in BSP Structue CRMT_BSP_SRV_OIC_SRCHRES.
This may be the reason resulting this ABAP dump error in PCUI while creating Service order.
How these Z structures can be included in the BSP Structure CRMT_BSP_SRV_OIC_SRCHRES in production system?
Helpful answers would be rewrded max points as it is high priority issue.
Regards,
Basavaraj Patil

Hi Thirumala,
Thnaks for the reply.
            I have enhanced service application using transaction EEWB to add new custom fields. these fields are there in Z structure created by the system in production system. All the transports are moved to target system. Problem is that Z structure( contains custom fields) created while doing EEWB is not included in BSP structure.
I f transports are missed to move to target system, Is there any other alternative to solve this problem?
Regards,
Basavaraj Patil

Document number-PM order confirmation by IW41

Hi,
For PM work order confirmations, I want to fetch the document number. In which table can I find the document number stored? I found it in AFRU-CATSBELNR, but only for CATS confirmation. For confirmation of work order through IW41 transaction, is there any table where I get the document number?
Thanks and Regards,
Jegashree

Hi Jane,
I am getting the confirmation number.but not able to fetch the document number (I need this document number to fetch the cost per line item/confirmation from COEP table) Does the PM order confirmation through IW41 transaction have any document number?
Thanks

Fast entry transaction for entering purchase order confirmations

Does anyone know of fast entry transaction for entering purchase order confirmations similar to VL31N for inbound deliveries?
Thanks

dear John,
if i m not mistaken you want to give confirmation control to your existing POs.
If the case is this you can opt for a BDC to be run for updation.
Ask your abaper to do this thing.
revert back if this is not the the case.
Njoy
Ashish

Reg PM Order Confirmation(IW41)

Hi,
In PM Order internal Jobs time confirmation(IW41), i am in need to give the Personnel No. Can anyone please explain me where i have to configure the Personnel No in SPRO.? & How to link the personnel no field in IW41 page during time confirmation?

Hi,
For this you need to go to sproplantmaintenance&cutomer servicesmaintenanceandserviceprocessingservice confirmationcompletion confirmationset screentemplates for completion confirmation
here you create a new profile and the settings as below
choose header data as 3--customer service
screen area 1    1-Times for order operation
screen area 2    3-Goods movement
screen area 3     5-measurement or counter readings
remaining screens as you wish or keep it 0--not filled
and active push buttons check time, goodsmovement and measurement or counter readings.
after doing these settings save your profile and then go to iw42 screen
go to Extras-settings--give your new profile and save afterwards you will get your desired screen.
regards
satish

ABAP Programming Error when saving the Process Order confirmation in COR6N

Hello,
We have an issue related to Process Order confirmation using Tcode COR6N. When we enter all the inputs to confirm( Activity, yield and phase) and click on save it gives ABAP Programming Error (Exception condition "SEQ_NOT_FOUND" raised).
Any inputs in this regard, would be appreciated.

Hello
I can observe that you have implemented the report ZOPSECRE and that an inconsistency was found.
This repor corrects inconsistent orders which do not have an operation or a sequence, or the two of them.
The report checks whether there is at least one operation or one sequence and creates both including status objects.
Therefore, you need to have the default valus for the operation generation defined on OPJG for this order type/plant.
BR
Caetano

ABAP DUMP While doing GI Through Zmovement type in MIGO Transaction

Hi ,
We have migrated from FM FBS to BCS from 12.01.2015.
And we are using 101 profile with GR and IR update.
We received blow ABAP Dump while doing the GI through MIGO Transaction.
Can you please help on this.
Dump detatils
Category               ABAP Programming Error
Runtime Errors         MESSAGE_TYPE_X
ABAP Program           CL_BUAVC_ENTRY================CP
Application Component PSM-FM-BCS-AC
Date and Time          13.01.2015 09:10:00
Operating system..... "AIX 1 6, AIX 1 7"                                                      |
|                                                                                                  |
|    Memory consumption                                                                            |
|    Roll.... 0                                                                                    |
|    EM...... 33518336                                                                             |
|    Heap.... 0                                                                                    |
|    Page.... 196608                                                                               |
|    MM Used. 21989120                                                                             |
|    MM Free. 3145840                                                                              |
|User and Transaction                                                                              |
|    Client.............. 256                                                                      |
|    User................ "MM_BUX00_ZZ"                                                            |
|    Language key........ "R"                                                                      |
|    Transaction......... "MIGO_GI "                                                               |
|    Transaction ID...... "54AEDD9E3EE60710E10080000A15C616"                                       |
|                                                                                                  |
|    EPP Whole Context ID.... "54B35F7088300910E10080000A15C616"                                   |
|    EPP Connection ID....... 00000000000000000000000000000000                                     |
|    EPP Caller Counter...... 0                                                                    |
|                                                                                                  |
|    Program............. "CL_BUAVC_ENTRY================CP"                                       |
|    Screen.............. "SAPLMIGO 0001"                                                          |
|    Screen Line......... 18                                                                       |
|    Debugger Active..... "none"                                                                   |
|Information on where terminated                                                                   |
|    Termination occurred in the ABAP program "CL_BUAVC_ENTRY================CP" -                 |
|     in "POST".                                                                                   |
|    The main program was "SAPLMIGO ".                                                             |
|                                                                                                  |
|    In the source code you have the termination point in line 82                                  |
|    of the (Include) program "CL_BUAVC_ENTRY================CM00J".                               |
|Source Code Extract                                                                               |
|Line |SourceCde                                                                                   |
|   52|*--- method has provided some errors!):                                                     |
|   53|                                                                                            |
|   54|* Note 1499464:                                                                             |
|   55|*      IF cl_abap_aab_utilities=>is_active( id = 'BUAVC_GROUP'                              |
|   56|*       mode_assert_dump = 'X' ) = 'X'.                                                     |
|   57|      MOVE 'X' TO l_flg_dump.                                                               |
|   58|*      ENDIF.                                                                               |
|   59|                                                                                            |
|   60|*--- Check if the entry buffer of the AVC ledger contains data records                      |
|   61|*--- from previous COLLECT events:                                                          |
|   62|      IF ( l_f_avc_ledger-ref_ledger->entry_buffer_lines_count( ) > 0 ).                    |
|   63|*--- Sorry, must dump:                                                                      |
|   64|        ASSERT ID buavc_group                                                               |
|   65|               FIELDS c_avc_text 'POSTING_NOT_ALLOWED'                                      |
|   66|               CONDITION l_flg_dump <> 'X'.                                                 |
|   67|        IF l_flg_dump = 'X'.                                                                |
|   68|          MESSAGE x002(buavc) WITH c_avc_text space                                         |
|   69|                                   'POSTING_NOT_ALLOWED' space.                             |
|   70|        ENDIF.                                                                              |
|   71|      ENDIF.                                                                                |
|   72|    ENDIF.                                                                                  |
|   73|*----------------------------------------------------------------------                     |
|   74|* Note 1666556:                                                                             |
|   75|    IF me->g_commit_before_post EQ 'X'.                                                     |
|   76|*--- An unauthorized COMMIT WORK occurred before calling this POST                          |
|   77|*--- method. This COMMIT WORK has refreshed the AVC entry buffer and                        |
|   78|*--- would thus create a database inconsistency!                                            |
|   79|      MOVE 'X' TO l_flg_dump.                                                               |
|   80|      IF l_flg_dump = 'X'.                                                                  |
|   81|*--- Sorry, must dump (see note 1666556):                                                   |
|>>>>>|        MESSAGE x002(buavc) WITH c_avc_text space                                           |
|   83|                                 'INVALID_COMMIT' space.                                    |
|   84|      ENDIF.                                                                                |
|   85|    ENDIF.                                                                                  |
|   86|*----------------------------------------------------------------------                     |
|   87|                                                                                            |
|   88|                                                                                            |
|   89|*--- Call the POST method of the corresponding ledger instance:                             |
|   90|    CALL METHOD l_f_avc_ledger-ref_ledger->post                                             |
|   91|      EXPORTING                                                                             |
|   92|        i_ref_appl_log = me->g_ref_appl_log                                                 |
|   93|        i_doc_ref      = i_doc_ref.                                                         |
|   94|                                                                                            |
|   95| ENDLOOP.                                                                                  |
|   96|
Thanks Advance.
SAM

Hi Sam,
Please check if there is any commit statement written in badi or enhancement before calling this method for posting which is leading to update termination.
Regards,
Prakash.

ABAP Dump : IW41 Transaction : PM Order confirmation save

Similar Messages

Maybe you are looking for