SMQ1 DESTINATION NONE for 2LIS-Structurs 03, 11, 12, 13

Hi,
we are trying to extract deltas for the 2LIS-Structurs 03, 11, 12, 13. The init load has already work fine. But the delta doesnt work. We checked SMQ1 and the entries for the destinations are "NONE".
We tried the same for the 2LIS_02_HDR/ITM/SCL and the entries for the destination is the BW-System and the delta works.
What is wrong with the 2LIS-Structurs 03, 11, 12, 13?
Thanks in advance.
Nils

Hi,
do you see entries in MCEX03 (resp the others) and not in BWCLNT2LIS_03_BF?
This means that you have to schedule the collective update job for this application;
Goto LBWE with 03 (resp the other appl) and hit the job control; maintain print params (even dummies with LOCL) and then schedule your job on a regular basis in order to pass your outboundQ changes to the BW delta Q.
After one run you should see already LUWs in SMQ1 under your application; then RSA7 will show you the data.
hope this helps...
Olivier.

Similar Messages

RFC Destination None Error for MIGO

Hi,
I am getting RFC Destinatnation NONE error while posting Goods Receipt. GTS service for SD and MM is not active. Error showing for FM GRC01_COST_OBJECT_COST.
Can any one help in this regard.
Thanks in advance.
SP Raj

Hi,
Pl find the details below of the error.
Short text
    RFC destination "NONE" does not exist.
What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPLCK36" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
Error analysis
    The 'destination' "NONE" for a Remote Function Call
    is unknown.
    You can display the RFC destinations available in the system using
    the transaction SM59.
Trigger Location of Runtime Error
    Program                                 SAPLCK36
    Include                                 ISAUTO_CK_SAPLCK36============E
    Row                                     812
    Module type                             (FORM)
    Module Name                             PRICE_STRATEGY_NEW
806 ************************************************************************
807 *     DOERNER, GRC, 10/11/1999: Add one new strategy:
808 * 3b. Create costestimate during goods receipt
809 ************************************************************************
810     when 4.
811       if k_debug_loc is initial.
>>>>>         call function 'GRC01_COST_OBJECT_COST' destination 'NONE'
813                 exporting
814                      im_vbeln     = f_mtcom-vbeln
815                      im_posnr     = f_mtcom-posnr

SMQ1 - outbound queue with destination NONE

Dear all,
I did the setup for LIS application 13 two days back. I have scheduled the V3 job in LBWE but the job fails with ABAP Dump. I checked in SMQ1 and see that the destination in NONE for this datasource. Please help me.
Thanks and Regards
Adhira Anand

Hi Mti,
I did a init with data transfer and DSO is my first data target.
Please check the below ABAP dump.
What happened?
    The current application program detected a situation wh
    should not occur. Therefore, a termination with a short
    triggered on purpose by the key word MESSAGE (type X).
Error analysis
    Short text of error message:
    Structures have changed (sy-subrc=2)
    Long text of error message:
    Technical information about the message:
    Message class....... "MCEX"
    Number.............. 194
    Variable 1.......... 2
    Variable 2.......... " "
    Variable 3.......... " "
    Variable 4.......... " "
How to correct the error
    Probably the only way to eliminate the error is to correct the program.
    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:
    "MESSAGE_TYPE_X" " "
    "SAPLMCEX" or "LMCEXU22"
    "MCEX_UPDATE_18"
    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.
Information on where terminated
    Termination occurred in the ABAP program "SAPLMCEX" - in "MCEX_UPDATE_18".
    The main program was "RMCEXUP1 ".
    In the source code you have the termination point in line 156
    of the (Include) program "LMCEXU22".
    The program "SAPLMCEX" was started as a background job.
    Job Name....... "LIS-BW-VB_APPLICATION_18_635"
    Job Initiator.. "SDSDISP"
    Job Number..... 07003800
Thanks and Regards
Adhira Anand

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

Behaviour of CALL FUNCTION fname STARTING NEW TASK DESTINATION 'NONE'

As per ABAP help documentation, the statement CALL FUNCTION fname STARTING NEW TASK DESTINATION 'NONE' should create a new main session in same user session.The behaviour is wrong as per documentation.
But current behaviour:
The statement CALL FUNCTION fname STARTING NEW TASK DESTINATION 'NONE' is creating a new user session.
Any reason?

Hi Prakash,
I'd agree with Suhas, that you're reading the documentation wrong. Here's your quote:
As per ABAP help documentation, the statement CALL FUNCTION fname STARTING NEW TASK DESTINATION 'NONE' should create a new main session in current user session.
If you look at the help, you can see that it says:
When the destination NONE is used, a new main session is opened for the current user session.
Do you see the difference? Also, note that in this context main session basically means that we're talking about a new external session:
Each task ID defines a separate RFC connection with its own context, meaning that, in the case of repeated function module calls of the same task ID, the global data of the relevant function group can be accessed, if the connection still exists.
In dialog processing, note that the maximum number of six main sessions cannot be exceeded, else an error message is displayed.
If you're still in doubt, check out the online ABAP documentation for [CALL FUNCTION - STARTING NEW TASK|http://help.sap.com/abapdocu_70/en/ABAPCALL_FUNCTION_STARTING.htm]. So I'd say the documentation is in line with the actual behavior.
Cheers, harald

Plain call function versus destination 'none'

we have an RFC enabled function module which is being used as an rfc by external calls but is also used within the same sap system as a conventional function mdoule.
Currently the call in the same sap system uses a DESTINATION 'NONE' clause and I have noticed that in the SE30 Runtime analysis there is sometimes an expensive 'WAIT for RFC' against this function module call.
Can I simply remove the DESTINATION 'NONE' clause or is there a good reason for it being there?
Will a call without the clause always be more efficient than one with it or is there no difference?

Currently the call in the same sap system uses a DESTINATION 'NONE' clause and I have noticed that in the SE30 Runtime analysis there is sometimes an expensive 'WAIT for RFC' against this function module call.
I wish I had a running SAP system to quickly test this. Did you enable also profiling of RFC calls in SE30? Couldn't the trivial reason just be that the function module takes some time and since it's a synchronous calls the calling program has to wait for it to return?
Can I simply remove the DESTINATION 'NONE' clause or is there a good reason for it being there?
Well, I'd be really careful and first make sure that I understand why somebody put it there. Note that an RFC call is executed in it's own context (e.g. see comments in ABAP online documentation on [RFC destination|http://help.sap.com/abapdocu_70/en/ABENRFC_DESTINATION.htm]), so if that was the reason why the destination 'NONE' was introduced you probably shouldn't change it.
Also, a [synchronous RFC call|http://help.sap.com/abapdocu_70/en/ABAPCALL_FUNCTION_DESTINATION.htm] triggers an implicit database commit. In theory a program shouldn't rely on that, but I've seen my fair share of programs where developers were not aware of some side effects (and actually relied on them).
Or how about a funky setup where your RFC module actually has coding to call the original system back (i.e. usage of RFC destination 'BACK'); so removing the 'NONE' should cause trouble in this case as well...
There's probably lots of other possible traps once you start thinking about it. Most likely they are not relevant, but it definitely helps a lot if you can judge the skill set of the programmer who introduced this possibly unnecessary RFC call...
As far as performance is concerned I doubt that you'd gain much if it's a synchronous RFC (and the function module runs for some time and is not executed tons of times). Note though that RFC calls are limit to some stricter resource management (e.g. they can be controlled via quite a few profile parameters), so your RFC might timeout due to lack of resources, where your direct function call wouldn't do that. But if your RFC does some substantial work I doubt that the overhead for the RFC calls will be measurable.
Cheers, harald

Locking problem when calling FM in background OR destination NONE....

Hi,
I've made a RF transaction to handle some movements from one Storage Unit to another one by creating a TO using standard FM L_TO_CREATE_SINGLE - so far, so good.
My problem is that this FM makes a lot of standard checks (which is fine!) and if any of them fails - it issues a message, although I certainly don't want any message to be issued in this RF screen other than the ones that can be displayed on another screen.
In order to avoid those annoying on-line messages I've tried to call the function in background, and even with DESTINATION 'NONE' - and here it is doing fine regarding the message handling (it is handled by the sy-subrc handler after the FM call) BUT now I'm having an even more annoying problem -> a lock is created (on tables LQUAX and VEKP) which I can't get rid of!!! (unless deleting manually the lock in SM12.......)
Anyone experienced this by performing L_TO_CREATE_SINGLE in background mode or DESTINATION 'NONE' ?
A check whether the TO is succesfully created or not is important, as after the TO creation I'm creating an Idoc (via L_SUB_INITIATION_FOR_PICK_HU) for that TO.
Any ideas?
Message was edited by:
 Branko Jovanovic

Indeed, this solved my problem:
CALL FUNCTION 'L_TO_CREATE_SINGLE'
 EXPORTING
 i_lgnum = whs_id
 i_bwlvs = ltak-bwlvs
 i_matnr = wa_lqua-matnr
 i_werks = wa_lqua-werks
 i_lgort = wa_lqua-lgort
 i_charg = wa_lqua-charg
 i_anfme = rl03t-anfme
 i_altme = ltap-altme
 i_vltyp = ltap-vltyp
 i_vlpla = l_vlpla
 i_vlenr = ltap-vlenr
 i_nltyp = ltap-nltyp
 i_nlpla = l_nlpla
 i_nlenr = ltap-nlenr
 i_update_task = c_true
 i_commit_work = c_true
 IMPORTING
 e_tanum = g_tanum
 e_ltap = itab_ltap
 TABLES
 t_ltak = itab_ltak_vb
 t_ltap_vb = itab_ltap_vb
 EXCEPTIONS
 error_message = 01 "Shows errors if this is commented
 no_to_created = 1
 bwlvs_wrong = 2
 betyp_wrong = 3
 benum_missing = 4
 betyp_missing = 5
 foreign_lock = 6
 vltyp_wrong = 7
 vlpla_wrong = 8
 vltyp_missing = 9
 nltyp_wrong = 10
 nlpla_wrong = 11
 nltyp_missing = 12
 rltyp_wrong = 13
 rlpla_wrong = 14
 rltyp_missing = 15
 squit_forbidden = 16
 manual_to_forbidden = 17
 letyp_wrong = 18
 vlpla_missing = 19
 nlpla_missing = 20
 sobkz_wrong = 21
 sobkz_missing = 22
 sonum_missing = 23
 bestq_wrong = 24
 lgber_wrong = 25
 xfeld_wrong = 26
 date_wrong = 27
 drukz_wrong = 28
 ldest_wrong = 29
 update_without_commit = 30
 no_authority = 31
 material_not_found = 32
 lenum_wrong = 33
 OTHERS = 34.
IF sy-subrc NE 0.
 MOVE sy-subrc TO g_rc.
 message_id = sy-msgid.
 message_number = sy-msgno.
 message_var1 = sy-msgv1.
 message_var2 = sy-msgv2.
 message_var3 = sy-msgv3.
 message_var4 = sy-msgv4.
 PERFORM error_message.
ENDIF.
So I'll reward Arnold eventhough I got the answer earlier .....
Cheers!

How to find out name of table for a structure.

hello all,
I want to find out name of table for a structure ADDR1_DATA. can anybody pls tell me how to find out it?
Thanks,
Ashu

Hi Ashu,
You write the structure name in se11
after selecting the database table radio button
click on the where used list button in the application tool bar.
You will find the table name if it is used else where.
Check out the website at:
http://sap-idoc2edi-consulting.com/
Read the blog at:
http://blogs.ittoolbox.com/sap/ehadzipetros
Regards,
Jagadish

How to create internal table for a structure in BSP

hi ,
I have created a Structure in BSP.I want to create an internal table for that Structure. But in my coding ie.
<% data: begin of itab_1 .
 include type zuvendstr.
 data:end of itab_1.
 data wa_str like line of itab_1.
 loop at itab_1 into wa_str. %>
 <tr>
 <td><%=wa_str-name%> </td>
 <%endloop.%>
In this zuvendstr is Structure ,wa_str is workarea and itab_1 is an Internal table.But it is showinng an error that itab_1 is unknown.But we cannot define internal tables for an Structure in Page Attributes.So,please resolve how to create internal table for Structure in BSPS

Hi,
You can define itab_1 like this (assuming zuvendstr is a structure type):
DATA: itab_1 TYPE TABLE OF zuvendstr.
Regards,
Tanguy

Reciever file adapter configuration for Deep structure

Hi Experts,
I have a idoc to file scenario in which i used a data type for file in below format:
DT_Test
-->Recordset(0.unbounded)
>E21DPU1(0.unbounded)
>field1
>field2
>E21DPU5(0.unbounded)
>filed 3
>filed 4
>E21DP03(0.unbounded)
>filed 5
>filed 6
Here DT_test is datatype name,Recordset is a structure name which contain E21DPU1, E21DPU5,E21DPO3 stucture inside it.Now,E21DPU5 and E21DPO3 structures are under E21DPU1.
I am confused in creating content conversion parameters i.e what we have to mention in Recordset Stucture .
I used E21DPU1,,E21DPU5,,E21DP03,* .should it work for deep structure.
Thanks
Deepak

Hi,
file adapter does not handle 2 level deep structures
the easiest way to do it now is to go for abap or java mapping
and create a line for each of the output lines and handle this in the file adapter
so like <line> </line>
<line>E21DPU1(0.unbounded) with fields </line>
<line>E21DPU5(0.unbounded) with fields </line>
<line> etc. </line>
Regards,
Michal Krawczyk

Best practice for creating RFC destination entries for 3rd parties(Biztalk)

Hi,
We are on SAP ECC 6 and we have been creating multiple RFC destination entries for the external 3rd party applications such as Biz-talk and others using TCP/IP connection type and sharing the programid.
The RFC connections with IDOC as data flow have been made using Synchronous mode for time critical ones(few) and majority through asynchronous mode for others. The RFC destination entries have been created for many interfaces which have unique RFC destinations with its corresponding ports defined in SAP.
We have both inbound and outbound connectivity.with the large number of RFC destinations being added we wanted to review the same. We wanted to check with others who had encountered similar situation and were keen to learn their experiences.
We also wanted to know if there are any best practices to optimise on number of RFC destinations.
Here were a few suggestions we had in mind to tackle the same.
1. Create unique RFC destinations for every port defined in SAP for external applications as Biztalk for as many connections. ( This would mean one for inbound, one for outbound)
2. Create one single RFC destination entry for the external host/application and the external application receiving the idoc control record to interpret what action to perform at its end.
3. Create RFC destinations based on the modules it links with such as materials management, sales and distribution, warehouse management. This would ensure we can limit the number of RFC to be created and make it simple to understand the flow of data.
I have done checks on SAP best practices website, sap oss notes and help pages but could not get specific information I was after.
I do understand we can have as unlimited number of RFC destinations and maximum connections using appropriate profile parameters for gateway, RFC, client connections, additional app servers.
I would appreciate if you can suggest the best architecture or practice to achieve RFC destinations in an optimized manner.
Thanks in advance
Sam

Not easy to give a perfect answer
1. Create unique RFC destinations for every port defined in SAP for external applications as Biztalk for as many connections. ( This would mean one for inbound, one for outbound)
-> be careful if you have multi cllients ( for example in acceptance) RFC's are client independ but ports are not! you could run in to trouble
2. Create one single RFC destination entry for the external host/application and the external application receiving the idoc control record to interpret what action to perform at its end.
-> could be the best solution... its easier to create partner profiles and the control record will contain the correct partner.
3. Create RFC destinations based on the modules it links with such as materials management, sales and distribution, warehouse management. This would ensure we can limit the number of RFC to be created and make it simple to understand the flow of data.
-> consider this option 2.
We send to you messagebroker with 1 RFC destination , sending multiple idoctypes, different partners , different ports.

What command would you use to check for allocation, structural, or logical integrity problems?

What command would you use to check for allocation, structural, or logical integrity problems?

Wondering if you are looking for DBCC CHECKDB command? For more information, on that command, try to look at this:
http://technet.microsoft.com/en-us/library/ms176064.aspx

Configuring the Destination URL for the Adobe Document Services

hi all,
I am going through the documentation for "Configuring the Destination URL for the Adobe Document Services " at :
http://help.sap.com/saphelp_nw2004s/helpdata/en/02/560f41ca73d349e10000000a1550b0/frameset.htm
I am not able to understand 7th step
7. Define the user name and password. To find out how to create the user name and password for the Adobe document services, see Creating a User for Basic Authentication in the document Adobe Document Services Configuration Guide. You can find this guide in the SAP Service Marketplace under Quick Link /InstguidesNW04.
In our scenario
We are running NW04s SP11 on 2 machines
1) 32-bit machine with ADS and credentials properly configured on Web AS for Java installation
com.adobe AdobeDocumentServices null (710.20061024154505.342190)
com.adobe AdobeDocumentServicesEjbClientLibrary null (705.20060407121920.289077)
sap.com SAP-JEE 7.00 SP11 (1000.7.00.11.0.20070201154700)
sap.com SAP-JEECOR 7.00 SP11 (1000.7.00.11.0.20070201154700)
com.adobe DocumentServicesBinaries2 null (710.20060629085312.115621)
com.adobe DocumentServicesConfiguration null (710.20061024154505.342190)
com.adobe DocumentServicesDestProtoService null (710.20060821084105.325745)
com.adobe DocumentServicesLibrary null (710.20060629090137.115621)
com.adobe DocumentServicesLicenseDatabase null (705.20051005114147.242570)
com.adobe DocumentServicesLicenseManager null (710.20060929113452.336248)
com.adobe DocumentServicesLicenseService null (710.20060929113452.336248)
com.adobe DocumentServicesLicenseSupportService null (710.20060929113641.336248)

2) 64-bit machine with portal installation on Web AS for Java, with ESS and MSS
sap.com/SAP-JEECOR 7.00 SP11 (1000.7.00.11.0.20070201154700) 20070308153304
sap.com/SAP-JEE 7.00 SP11 (1000.7.00.11.0.20070201154700) 20070308153213
sap.com SAP_ESS 600 SP7 (1000.600.0.7.12.20070314050106)
sap.com SAP_MSS 600 SP7 (1000.600.0.7.4.20070321052655)
sap.com tc/wd/webdynpro null (7.0009.20060804145649.0000) 

Why do we have to create a new user for the server which is consuming the web service? We already have an user "ADSUser" defined for the Web AS server which has ADS services deployed.
I have opened this thread to solve the previous unanswered question I posted on SDN Empty area in place of Interactive form. .
One more thing the adobe print forms of ESS [Total Compensation Statement and Salary Statement] are rendering properly, only the ones with Interactive ability or not.
thanks,
Sanketh

Hello Sanketh,
1. To access the NW04s configuration guide,
 - Go to https://service.sap.com/adobe
 - On the left frame (tree), under Adobe > Media Library > Documentation
 - On the right had pane you will find the link to the NW04s Configuration guide
2. The link that you have mentioned below details the steps required to be carried out on the client machine that consumes the Adobe Document Services. In our case that is the j2ee engine on which your Web Dynpro application is running. It could be the same physical machine with two different j2ee instances hosting Web Dynpro and ADS or it could be two different physical machine or a single machine having a single instance of j2ee engine hosting both the Web Dynpro and the ADS.
You do not have to create a separate username and a password on the consuming machine but you need to configure the Web Service client proxy to point to the ADS (maybe hosted on a different machine) with the username and the password created on the ADS server. As you have mentioned, you have already created such an user on the ADS (ADSUser). This user authentication on the client machine (consuming server - Web Dynpro) would be required at the runtime by the j2ee engine to authenticate itself with the ADS.
Best Regards,
Krish

Mac user, PS CC 2014 latest version. When using "Save for Web" I bring my 900 x600px @72 ppi in to SFW and the output becomes 300ppi. The only way it stays at 72ppi is if I check "none" for metadata. I know to should not matter much, but I would prefer to

Mac user, PS CC 2014 latest version. When using "Save for Web" I bring my 900 x600px @72 ppi in to SFW and the output becomes 300ppi. The only way it stays at 72ppi is if I check "none" for metadata. I know to should not matter much, but I would prefer to keep all my web jpgs @ 72ppi. Any solutions?

It opens up as 900x600 @300ppi
Here's a screenshot-

Inconsistency in the Dictionary for the structure "MC02M_0ITM".

Hi Expert,
we are applying ehp3 for ERP 6.0. I am getting the below abap dump DDIC_TYPE_INCONSISTENCY.
Runtime Errors DDIC_TYPE_INCONSISTENCY
Date and Time          29.08.2011 10:12:27
Short text
     Inconsistency in the Dictionary for the structure "MC02M_0ITM".
What happened?
     Error in the SAP kernel.
     The current ABAP "SAPLMCEX" program had to be terminated because the
     ABAP processor detected an internal system error.
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" " "
      "SAPLMCEX" or "LMCEXTOP"
I can see there is error on Table MC02M_0ITM:
Table MC02M_0ITM could not be activated (E- Field ZZUNDTSORT in table MC02M_0ITM is specified twice. Please check )
when I run the program RSDDCHECK in your system, for check the structure "MC02M_0ITM".
There is som error.
Any Idea how can I solve this kind of error. Is it some repport for help this?
Regards

Hi Srikishan,
Thanks for reply.
There is just one field ZZUNDTSORT on talbe.
When I try to check the table I get this log:
Check table/structure MC02M_0ITM
           Check table MC02M_0ITM (REZ/29.08.11/11:14)
           Enhancement category 3 possible, but include or subty. not yet classified
           Field ZZAFHENTFORM in table MC02M_0ITM is specified twice. Please check
           Field ZZAFHKVANTUM in table MC02M_0ITM is specified twice. Please check
           Field ZZAFHTERMFRA in table MC02M_0ITM is specified twice. Please check
           Field ZZAFHTERMTIL in table MC02M_0ITM is specified twice. Please check
           Field ZZAFREGNDATO in table MC02M_0ITM is specified twice. Please check
           Field ZZAFREGNKVAMTUM in table MC02M_0ITM is specified twice. Please check
           Field ZZAFREGNMEINS in table MC02M_0ITM is specified twice. Please check
           Field ZZALTMATNR in table MC02M_0ITM is specified twice. Please check
           Field ZZALTMPRIS in table MC02M_0ITM is specified twice. Please check
           Field ZZANSOEGNR in table MC02M_0ITM is specified twice. Please check
           Field ZZANTHA in table MC02M_0ITM is specified twice. Please check
           Field ZZBK_DUMMY1 in table MC02M_0ITM is specified twice. Please check
           Field ZZBK_DUMMY2 in table MC02M_0ITM is specified twice. Please check
           Field ZZBK_GRKERN in table MC02M_0ITM is specified twice. Please check
           Field ZZBK_KNKERN in table MC02M_0ITM is specified twice. Please check
           Field ZZBK_MELDR in table MC02M_0ITM is specified twice. Please check
           Field ZZBK_OLIEIND in table MC02M_0ITM is specified twice. Please check
           Field ZZBK_RENS in table MC02M_0ITM is specified twice. Please check
           Field ZZBK_RENTFRO in table MC02M_0ITM is specified twice. Please check
           Field ZZBK_RENTIL in table MC02M_0ITM is specified twice. Please check
           Field ZZBK_TOR in table MC02M_0ITM is specified twice. Please check
           Field ZZBK_TORTIL in table MC02M_0ITM is specified twice. Please check
           Field ZZBPROT in table MC02M_0ITM is specified twice. Please check
           Field ZZBUREN in table MC02M_0ITM is specified twice. Please check
           Field ZZBVAND in table MC02M_0ITM is specified twice. Please check
           Field ZZFORBELNR in table MC02M_0ITM is specified twice. Please check
           Field ZZFORFALDSDATO in table MC02M_0ITM is specified twice. Please check
           Field ZZFORVUDB in table MC02M_0ITM is specified twice. Please check
           Field ZZGJAHR in table MC02M_0ITM is specified twice. Please check
           Field ZZKONCEPTNR in table MC02M_0ITM is specified twice. Please check
           Field ZZLAESSELV in table MC02M_0ITM is specified twice. Please check
           Field ZZLAGERLEJDATO in table MC02M_0ITM is specified twice. Please check
           Field ZZLAGERLEJSATS in table MC02M_0ITM is specified twice. Please check
           Field ZZLAGERSATSDATO in table MC02M_0ITM is specified twice. Please check
           Field ZZLAGERSATSDATO2 in table MC02M_0ITM is specified twice. Please check
           Field ZZLAGERSATSDATO3 in table MC02M_0ITM is specified twice. Please check
Regards

SMQ1 DESTINATION NONE for 2LIS-Structurs 03, 11, 12, 13

Similar Messages

Maybe you are looking for