Changes to SHPMNT03 Idoc after EHP 5.0 upgrade?

Hello,
Has there been any changes to the SHPMNT03 Idoc after the recent EHP 5.0 upgrade? Where can I get information regarding this?

You have to use an S-user that was created for the company you are contracted. Without that user you can't access documentation/releasenotes etc.
Markus

Similar Messages

IDOC after Material Change

Hi all,
I would like to send a IDOC after a material has changed.
I have to send the complete material by IDOC, so not by the change pointers (TC BD21).
Normally a user would change a material and then would start BD10 to send the material.
I have found a user exit EXIT_SAPLMGMU_001 but a that point the material is not saved.
How can I start BD10 after the material has been saved?
Or does someone know another way to achieve this?
Greetings Fred.

Hi Frek ,
If u r working ECC after saving the material (Please Check the code) . After this code create an Enhance Spot . where u can call ur transaction .
I hope it resolves ur problem .
Rgds
Sree M
Edited by: Sree Merugu on Apr 21, 2008 5:00 PM

Unable to create IDOCs after client copy

I'm unable to create IDOCs after a client copy. I receive a SAPSQL_ARRAY_INSERT_DUPREC or insert of duplicate rows ABAP dump.
Does anyone know what how to fix this. Thank you in advance.
Runtime Error          SAPSQL_ARRAY_INSERT_DUPREC
Except.                CX_SY_OPEN_SQL_DB
Date and Time          22.10.2007 16:50:51
ShrtText
The ABAP/4 Open SQL array insert results in duplicate database records.
What happened?
Error in ABAP application program.
The current ABAP program "SAPLEDI1" had to be terminated because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
is especially useful if you want to keep a particular message.
Error analysis
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
neither
caught nor passed along using a RAISING clause, in the procedure
"F09_IDOC_INSERT_WITH_NUMBER" "(FORM)"
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
If you use an ABAP/4 Open SQL array insert to insert a record in
the database and that record already exists with the same key,
this results in a termination.
(With an ABAP/4 Open SQL single record insert in the same error
situation, processing does not terminate, but SY-SUBRC is set to 4.)
How to correct the error
Use an ABAP/4 Open SQL array insert only if you are sure that none of
the records passed already exists in the database.
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"SAPSQL_ARRAY_INSERT_DUPREC" CX_SY_OPEN_SQL_DBC
"SAPLEDI1" or "LEDI1F09"
"F09_IDOC_INSERT_WITH_NUMBER"
If you cannot solve the problem yourself and you wish to send
an error message to SAP, include the following documents:
1. A printout of the problem description (short dump)
To obtain this, select in the current display "System->List->
Save->Local File (unconverted)".
2. A suitable printout of the system log
To obtain this, call the system log through transaction SM21.
Limit the time interval to 10 minutes before and 5 minutes
after the short dump. In the display, then select the function
"System->List->Save->Local File (unconverted)".
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, select the Editor function "Further Utilities->
Upload/Download->Download".
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
The exception must either be prevented, caught within the procedure
"F09_IDOC_INSERT_WITH_NUMBER"
"(FORM)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
System environment
SAP Release.............. "640"
Application server....... "auaplxr3q"
Network address.......... "128.197.135.5"
Operating system......... "AIX"
Release.................. "5.3"
Hardware type............ "000B439ED600"
Character length......... 8 Bits
Pointer length........... 64 Bits
Work process number...... 1
Short dump setting....... "full"
Database server.......... "auaplxr3q"
Database type............ "ORACLE"
Database name............ "Q63"
Database owner........... "SAPR3"
Character set............ "en_US.ISO8859-1"
SAP kernel............... "640"
Created on............... "Mar 22 2007 20:48:46"
Created in............... "AIX 1 5 00538A4A4C00"
Database version......... "OCI_920 "
Patch level.............. "175"
Patch text............... " "
Supported environment....
Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE
10.2.0.."
SAP database version..... "640"
Operating system......... "AIX 1 5, AIX 2 5, AIX 3 5"
Memory usage.............
Roll..................... 16128
EM....................... 4189928
Heap..................... 0
Page..................... 0
MM Used.................. 1469352
MM Free.................. 2718056
SAP Release.............. "640"
User and Transaction
Information on where terminated
The termination occurred in the ABAP program "SAPLEDI1" in
"F09_IDOC_INSERT_WITH_NUMBER".
The main program was "SAPMSSY1 ".
The termination occurred in line 108 of the source code of the (Include)
program "LEDI1F09"
of the source code of program "LEDI1F09" (when calling the editor 1080).
Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred in
the
procedure "F09_IDOC_INSERT_WITH_NUMBER" "(FORM)" but was not handled locally,
not declared in the
RAISING clause of the procedure.
The procedure is in the program "SAPLEDI1 ". Its source code starts in line 5
of the (Include) program "LEDI1F09 ".
Source Code Extract
Line
SourceCde
78
perform call_badi tables list_container_insert
79
using control
80
ident.
81
Aufruf des Badi's für das einstreuen neuer Segmente
82
perform call_insert_badi tables list_container_insert
83
using control
84
ident
85
changing maxsegnum.
86
87
   free list_container_insert
88
FREE_RETURN = 1.
89
ELSE. " no other IDoc is open in create-mode
90
LOOP AT LIST_CONTAINER_CREATE WHERE MANDT EQ SY-MANDT
91
AND   DOCNUM EQ IDENT.
92
LIST_CONTAINER_CREATE-DOCNUM = DOCNUM.
93
MODIFY LIST_CONTAINER_CREATE.
94
ADD 1 TO MAXSEGNUM.
95
ENDLOOP.
96
if control-mestyp eq c_mestyp.
97
CALL FUNCTION 'FUNCTION_EXISTS'
98
EXPORTING
99
funcname           = c_func
100
EXCEPTIONS
101
FUNCTION_NOT_EXIST = 1.
102
IF syst-subrc IS INITIAL. "Anwendungssystem
103
perform call_transform
104
tables list_container_create
105
using control.
106
ENDIF.
107
endif.
>>>>>
INSERT EDID4 FROM TABLE LIST_CONTAINER_CREATE.
109
Aufruf des Badi's für das Anwendungsmapping einzelner Felder
110
perform call_badi tables list_container_create
111
using control
112
ident.
113
perform call_insert_badi tables list_container_create
114
using control
115
ident
116
changing maxsegnum.
117
118
free list_container_create
119
FREE_RETURN = 0.
120
ENDIF.
121
122
insert status records
123
124
SYN_ERROR_IN = ' '.
125
CNTR_STATUS = 0.
126
REFRESH LIST_STATUS.
127
CLEAR LIST_STATUS.
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
2
SY-TABIX
1
SY-DBCNT
1
SY-FDPOS
0
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
CPIC and RFC Control
SY-MSGTY
SY-MSGID
SY-MSGNO
000
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
Active Calls/Events
No.   Ty.          Program                             Include                             Line
Name
13 FORM         SAPLEDI1                            LEDI1F09                              108
F09_IDOC_INSERT_WITH_NUMBER
12 FUNCTION     SAPLEDI1                            LEDI1U19                               33
EDI_DOCUMENT_CLOSE_CREATE_TAB
11 FUNCTION     SAPLEDIR                            LEDIRU01                              273
IDOC_INBOUND_WRITE_TO_DB
10 FORM         SAPLEDIN                            LEDINF01                              457
ONE_IDOC_STORE
9 FUNCTION     SAPLEDIN                            LEDINU05                              234
IDOC_INBOUND_ASYNCHRONOUS
8 FORM         SAPLEDIN                            LEDINV05                               19
IDOC_INBOUND_ASYNCHRONOUS
7 FORM         SAPMSSY1                            SAPMSSY1                              254
XAB_RUN_DRIVER
6 FUNCTION     SAPLSXAB                            LSXABU01                                9
RFC_RUN_XAB_DRIVER
5 FUNCTION     SAPLERFC                            LERFCU01                               59
ARFC_EXECUTE
4 FUNCTION     SAPLERFC                            LERFCU02                              229
ARFC_DEST_SHIP
3 FORM         SAPLERFC                            LERFCV02                               28
ARFC_DEST_SHIP
2 FORM         SAPMSSY1                            SAPMSSY1                               69
REMOTE_FUNCTION_CALL
1 MODULE (PBO) SAPMSSY1                            SAPMSSY1                               30
%_RFC_START
Chosen variables
Name
Val.
No.      13 Ty.          FORM
Name F09_IDOC_INSERT_WITH_NUMBER
CONTROL-MESTYP
USERCLONE
554544444222222222222222222222
53523CFE5000000000000000000000
C_MESTYP
FIDCCH
444444222222222222222222222222
694338000000000000000000000000
SY-XFORM
IDOC_INBOUND_ASYNCHRONOUS
444454444544545544454445522222
94F3F9E2F5E4F139E382FEF5300000
LIST_STATUS-STAPA2
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
C_FUNC
IDOC_TRANSFORM
444455544544542222222222222222
94F3F421E36F2D0000000000000000
SYST-REPID
SAPLEDI1
5454444322222222222222222222222222222222
310C549100000000000000000000000000000000
SY-UNAME
Q63CLNT140
533444533322
1633CE414000
%_DUMMY$$
2222
0000
SY-MSGV1
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
SYST-SUBRC
0
0000
0000
ALE_IDOC_TO_APL_OK
62
33
62
LIST_CONTAINER_CREATE[]
Table IT_20[9x1068]
FUNCTION-POOL=EDI1DATA=LIST_CONTAINER_CREATE[]
Table reference: 14
TABH+ 0(20) = 070000008036F5B8000000000000000000000000
TABH+ 20(20) = 0000000E00000014000000090000042CFFFFFFFF
TABH+ 40(16) = 0400002300000CA0000824C401000000
store        = 0x070000008036F5B8
ext1         = 0x0000000000000000
shmId        = 0     (0x00000000)
id           = 14    (0x0000000E)
label        = 20    (0x00000014)
fill         = 9     (0x00000009)
leng         = 1068 (0x0000042C)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000048
occu         = 8     (0x00000008)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 8     (cmpManyEq)
occu0        = 1
collHash     = 0
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0x070000008036F610
pghook       = 0x07000000802D86D0
idxPtr       = 0x0000000000000000
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 16    (0x00000010)
lineAlloc    = 16    (0x00000010)
store_id     = 23    (0x00000017)
shmIsReadOnly = 0     (0x00000000)
>>>>> 1st level extension part <<<<<
regHook      = Not allocated
hsdir        = Not allocated
ext2         = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack     = Not allocated
delta_head   = Not allocated
pb_func      = Not allocated
pb_handle    = Not allocated
LIST_CONTAINER_CREATE
1400000000000511747000000009E1BPADRML                     00000002#èXD63        070TST_QA140_1
3333333333333333333333333333434544544222222222222222222222333333330E54332222222233355555433353
14000000000005117470000000095120142DC0000000000000000000000000000238846300000000070434F11140F1
CONTROL
1400000000000511747640 64        2SAPQ63    LSQ63CLNT140
3333333333333333333333233222222223545533222245533444533322222222222222222222222222222222222222
14000000000005117476400640000000023101630000C31633CE414000000000000000000000000000000000000000
G_MAXSYNERR
1
0000
0001
<%_TABLE_EDID4>
ALE_DISPATCH_ERROR
27
33
27
ALE_IDOC_READY_FOR_APL
64
33
64
%_SPACE
2
0
IDENT
0000000000000001
3333333333333333
0000000000000001
ALE_IDOC_TO_APL_ERROR
63
33
63
No.      12 Ty.          FUNCTION
Name EDI_DOCUMENT_CLOSE_CREATE_TAB
IDENTIFIER
0000000000000001
3333333333333333
0000000000000001
NO_DEQUEUE
X
5
8
SYN_ACTIVE
Y
5
9
IDOC_CONTROL
1400000000000511747640 64        2SAPQ63    LSQ63CLNT140
3333333333333333333333233222222223545533222245533444533322222222222222222222222222222222222222
14000000000005117476400640000000023101630000C31633CE414000000000000000000000000000000000000000
SYNTAX_RETURN
0
0000
0000
INT_EDIDD[]
Table IT_10[9x1062]
FUNCTION-POOL=EDINDATA=G_T_DATA_RECORDS[]
Table reference: 9
TABH+ 0(20) = 0700000080284B80070000008028530800000000
TABH+ 20(20) = 000000090000000A0000000900000426FFFFFFFF
TABH+ 40(16) = 0400000900000AA8000824C401000000
store        = 0x0700000080284B80
ext1         = 0x0700000080285308
shmId        = 0     (0x00000000)
id           = 9     (0x00000009)
label        = 10    (0x0000000A)
fill         = 9     (0x00000009)
leng         = 1062 (0x00000426)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000039
occu         = 8     (0x00000008)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 8     (cmpManyEq)
occu0        = 1
collHash     = 0
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0x0700000080320D90
pghook       = 0x07000000802E1508
idxPtr       = 0x0000000000000000
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 16    (0x00000010)
lineAlloc    = 16    (0x00000010)
store_id     = 17    (0x00000011)
shmIsReadOnly = 0     (0x00000000)
>>>>> 1st level extension part <<<<<
regHook      = 0x0000000000000000
hsdir        = 0x0000000000000000
ext2         = 0x07000000802852A8
>>>>> 2nd level extension part <<<<<
tabhBack     = 0x0700000080284B30
delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func      = 0x0000000000000000
pb_handle    = 0x0000000000000000
NO_IGNORE
2
0
EDI_IDOC_SYNTAX_ERROR_IN
60
33
60
DOCNUM
0000000000511747
3333333333333333
0000000000511747
EXCLUSIVE
E
4
5
SYNCHRONOUS
S
5
3
APL_TESTIDOC_CHECK_OK
55
33
55
FREE_RETURN
0
0000
0000
INT_EDIDD
1400000000000000001000009E1BPADRML                  00000000##XD63        070TST_QA140_17 X00
3333333333333333333333333434544544222222222222222222333333330054332222222233355555433353322533
14000000000000000010000095120142DC0000000000000000000000000000846300000000070434F11140F1700800
SUB_INT_ACK_POSITIVE
14
33
14
G_INSERT_OK
2
0
LIST_CONTAINER_INSERT_TMP[]
Table[initial]
LIST_CONTAINER_INSERT_TMP
0000000000000000000000000                              00000000##
2223333333333333333333333333222222222222222222222222222222333333330022222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
%_ARCHIVE
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
No.      11 Ty.          FUNCTION
Name IDOC_INBOUND_WRITE_TO_DB
PI_DO_HANDLE_ERROR
X
5
8
PI_NO_DEQUEUE
X
5
8
PI_RETURN_DATA_FLAG
X
5
8
PI_RFC_MULTI_CP
0000
3333
0000
PI_STATUS_MESSAGE
000000000000000000000000000000000000000000000000000000000000
2223333333333333333333333333333333333333333333333333333333333332222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
PE_IDOC_NUMBER
0000000000000001
3333333333333333
0000000000000001
PE_INBOUND_PROCESS_DATA
140BAPI                                                  6
3334454222222222222222222222222222222222222222222222222223222222222222222222222222222222222222
1402109000000000000000000000000000000000000000000000000006000000000000000000000000000000000000
PE_STATE_OF_PROCESSING
0
0000
0000
T_DATA_RECORDS[]
Table IT_10[9x1062]
T_LINKED_OBJECTS[]
Table IT_11[0x100]
FUNCTION-POOL=EDINFORM=ONE_IDOC_STOREDATA=LT_LINKED_OBJECTS[]
Table reference: 10
TABH+ 0(20) = 000000000000000007000000802853F000000000
TABH+ 20(20) = 0000000A0000000B0000000000000064FFFFFFFF
TABH+ 40(16) = 0400000900002BB00010249401000000
store        = 0x0000000000000000
ext1         = 0x07000000802853F0
shmId        = 0     (0x00000000)
id           = 10    (0x0000000A)
label        = 11    (0x0000000B)
fill         = 0     (0x00000000)
leng         = 100   (0x00000064)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000190
occu         = 16    (0x00000010)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 2     (cmpSingleMcmpR)
occu0        = 1
collHash     = 0
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = Not allocated
pghook       = Not allocated
idxPtr       = Not allocated
refCount     = Not allocated
tstRefCount = Not allocated
lineAdmin    = Not allocated
lineAlloc    = Not allocated
store_id     = Not allocated
shmIsReadOnly = Not allocated
>>>>> 1st level extension part <<<<<
regHook      = 0x0000000000000000
hsdir        = 0x0000000000000000
ext2         = 0x0700000080285390
>>>>> 2nd level extension part <<<<<
tabhBack     = 0x0700000080285340
delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func      = 0x0000000000000000
pb_handle    = 0x0000000000000000
PC_CONTROL_RECORD
1400000000000000000    30        2          LSQ63CLNT140
3333333333333333333222233222222223222222222245533444533322222222222222222222222222222222222222
14000000000000000000000300000000020000000000C31633CE414000000000000000000000000000000000000000
%_VIASELSCR
0
4
%_SPACE
2
0
L_STATUS
64
33
64
L_ALE_SUCCESS_MESSAGE
B1                  S005                                                  No filters
4322222222222222222253332222222222222222222222222222222222222222222222222246266676772222222222
21000000000000000000300500000000000000000000000000000000000000000000000000EF069C45230000000000
ST_PREVIOUS_PARTNER_DATA-SYNCHK
X
5
8
C_TRUE
X
5
8
SYST-REPID
SAPLEDIR
5454444522222222222222222222222222222222
310C549200000000000000000000000000000000
C_ELEMENT_UNPROCESSED_IDOCS
Unprocessed_IDocs
56776667766544667222222222222222
5E02F353354F94F33000000000000000
ST_PREVIOUS_STATE_OF_PROCE
0
0000
0000
ST_INBOUND_PROCESS_DATA-EDIVR2
6
3
6
SY-MSGV4
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
L_SYN_ACTIVE
Y
5
9
SY-XFORM
IDOC_INBOUND_ASYNCHRONOUS
444454444544545544454445522222
94F3F9E2F5E4F139E382FEF5300000
L_SYNTAX_RETURN
0
0000
0000
%_DUMMY$$
2222
0000
SY-REPID
SAPLEDIR
5454444522222222222222222222222222222222
310C549200000000000000000000000000000000
No.      10 Ty.          FORM
Name ONE_IDOC_STORE
IDOC_NUMBER_IN
0000000000000000
3333333333333333
0000000000000000
STATE_OF_PROCESSING_IN
0
0000
0000
INBOUND_PROCESS_DATA_IN
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
GT_NEW_IDOC_IDENTIFICATIONS[]
Table[initial]
G_LAST_IDOC_NUMBER
0000000000000000
3333333333333333
0000000000000000
SYST-REPID
SAPLEDIN
5454444422222222222222222222222222222222
310C549E00000000000000000000000000000000
CURRENT_CONTROL_RECORD_IN-DOCNUM
0000000000000000
3333333333333333
0000000000000000
CONV_ERROR
2
0
C_TRUE
X
5
8
SY
0000000000000000000000000000000000000000000000000000000000000000000000000000000200000000000000
0002000000010009000000000000000000000000000100000001000000010000000000000000004C00000000000000
STATUS_MESSAGE_IN
000000000000000000000000000000000000000000000000000000000000
2223333333333333333333333333333333333333333333333333333333333332222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
C_IDOC_SELECT_AND_WRITE_TO_DB
5
3
5
SY-REPID
SAPLEDIN
5454444422222222222222222222222222222222
310C549E00000000000000000000000000000000
STATUS_MESSAGE_IN-STAMID
22222222222222222222
00000000000000000000
GT_NEW_IDOC_IDENTIFICATIONS
0000000000000000
3333333333333333222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SPACE
2
0
STATUS_MESSAGE_IN-STAMNO
000
333
000
RET_FLAG
X
5
8
G_RFC_CODEPAGE
0000
3333
0000
RSJOBINFO-JOBSUBRC
0
0000
0000
SY-XFORM
IDOC_INBOUND_ASYNCHRONOUS
444454444544545544454445522222
94F3F9E2F5E4F139E382FEF5300000
SY-LANGU
E
4
5
G_T_DATA_RECORDS[]
Table IT_10[9x1062]
LT_LINKED_OBJECTS[]
Table IT_11[0x100]
CURRENT_CONTROL_RECORD_IN
1400000000000000000    30        2          LSQ63CLNT140
3333333333333333333222233222222223222222222245533444533322222222222222222222222222222222222222
14000000000000000000000300000000020000000000C31633CE414000000000000000000000000000000000000000
%_DUMMY$$
2222
0000
SWO_%OBJID
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
No.       9 Ty.          FUNCTION
Name IDOC_INBOUND_ASYNCHRONOUS
IDOC_CONTROL_REC_40[]
Table IT_3[1x524]
FUNCTION-POOL=EDINFORM=IDOC_INBOUND_ASYNCHRONOUSDATA=IDOC_CONTROL_REC_40[]
Table reference: 3
TABH+ 0(20) = 07000000802D876007000000802D449000000000
TABH+ 20(20) = 0000000300000003000000010000020C000000E0
TABH+ 40(16) = 0400000900001FE0000A249001000000
store        = 0x07000000802D8760
ext1         = 0x07000000802D4490
shmId        = 0     (0x00000000)
id           = 3     (0x00000003)
label        = 3     (0x00000003)
fill         = 1     (0x00000001)
leng         = 524   (0x0000020C)
loop         = 224   (0x000000E0)
xtyp         = TYPE#000136
occu         = 10    (0x0000000A)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 2     (cmpSingleMcmpR)
occu0        = 0
collHash     = 0
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0x07000000802DB9D8
pghook       = 0x0000000000000000
idxPtr       = 0x0000000000000000
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 10    (0x0000000A)
lineAlloc    = 10    (0x0000000A)
store_id     = 9     (0x00000009)
shmIsReadOnly = 0     (0x00000000)
>>>>> 1st level extension part <<<<<
regHook      = 0x0000000000000000
hsdir        = 0x0000000000000000
ext2         = 0x07000000802D88A0
>>>>> 2nd level extension part <<<<<
tabhBack     = 0x07000000802D8710
delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func      = 0x0000000000000000
pb_handle    = 0x0000000000000000
IDOC_DATA_REC_40[]
Table IT_4[9x1063]
FUNCTION-POOL=EDINFORM=IDOC_INBOUND_ASYNCHRONOUSDATA=IDOC_DATA_REC_40[]
Table reference: 4
TABH+ 0(20) = 07000000802D880807000000802D896000000000
TABH+ 20(20) = 00000004000000040000000900000427FFFFFFFF
TABH+ 40(16) = 04000009000020500008249001000000
store        = 0x07000000802D8808
ext1         = 0x07000000802D8960
shmId        = 0     (0x00000000)
id           = 4     (0x00000004)
label        = 4     (0x00000004)
fill         = 9     (0x00000009)
leng         = 1063 (0x00000427)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000138
occu         = 8     (0x00000008)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 2     (cmpSingleMcmpR)
occu0        = 0
collHash     = 0
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0x07000000802E1550
pghook       = 0x07000000802D8860
idxPtr       = 0x0000000000000000
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 16    (0x00000010)
lineAlloc    = 16    (0x00000010)
store_id     = 12    (0x0000000C)
shmIsReadOnly = 0     (0x

Hi Rohan,
Welcome to SDN!
This error means that you're trying to duplicate a record on the DB... check the IDOC number ranges... it might help
Regards
Juan
Please reward with points if helpful

MSSQL 2008 - Database size getting smaller after EHP upgrade??

Hi All,
Did anyone observe the DB size of MSSQL 2008 after EHP upgrade?
In my two system, after upgraded to EHP5 and EHP2 respectively, the database is getting smaller compare to before upgrade, estimated 5-10gb.
EHP upgrade is unlike DBEXPORT, it shouldn't have any reorganization features and so do MSSQL.
Any idea?
Cheers,
Nicholas Chang

> Right after upgrade is smaller and after sgen, db size is bigger than source.
So it's ok.
> As system was upgrade from ECC6 to EHP5 with Central Application, HCM and Finance .... the after upgrade size should bigger than the source even before SGEN. Your kind input is mostly welcome.
If the source system was compiled completely (using SGEN) then you need to compare the sizes of the target system also, otherwise you compare apple with pies.
Another reason may be that index compression was activated:
Note 1459005 - Enabling index compression for SQL Server
You could now upgrade to SQL Server 2008 R2 and apply
Note 1488135 - Database compression for SQL Server
this will save additional space (30 - 50 %).
Markus

In Pages 5.1 how do I change the default spacing after a paragraph? I used to be able to do this with the inspector. I no longer see the option.

In pages 5.1 I was wondering how to change the line spacing after a paragraph.

This is from the online Pages Help . You have the option to the Help in your Pages Help menu
Adjust line spacing
You can adjust the spacing between lines in a paragraph, and change the amount of space before or after a paragraph.
Click in the paragraph whose spacing you want to change, or select one or more paragraphs.
In the Text pane of the Format inspector, click Style.
Click the disclosure triangle next to Spacing, then choose an option from the pop-up menu:
Lines: Choose when the distance between ascenders (parts of letters that extend to the top of the line) and descenders (parts of letters that extend below the line) should stay the same. The space between lines is proportional to the font size.
At least: Choose when the distance between lines should remain fixed (but not to overlap if the text gets large).The distance from one line to the next will never be less than the value you set, but it may be larger for larger fonts to prevent overlapping text lines.
Exactly: The distance between the baselines.
Between: The value you set increases the space between the lines, instead of increasing the height of the lines. By contrast, double-spacing doubles the height of each line.
Click the arrows next to the spacing field to set the amount of space for the option you chose.
To adjust the amount of space before and after the selected paragraph, click the arrows for Before Paragraph and After Paragraph

How to change the default IDOC basic type from CREMAS05 to CREMAS04.

Hi All,
How to change the default IDOC basic type from CREMAS05 to CREMAS04 when sending Vendor Master Data.
When I generate partner profile, the system will add the latest version of IDOC type which is CREMAS05 to the Outbound message. In my project, I'm asked to use CREMAS04.
I want to use BD14 to send master data directly, but the program will generate IDOC using CREMAS05. Is there a way that I can change it to CREMAS04? And also for using Change Pointers, I want to use the report RBDMIDOC, but i have the same problem.
Thanks
Sai Krishna

execute WE20 and edit the outbound parameters
here is a pretty good example: http://documentation.softwareag.com/webmethods/sapr3_gateway/sap231/pages/sapdist.htm
Edited by: Jürgen L. on Sep 7, 2011 9:49 PM

I have change e-mail address after first registration and when I logged in it send new password to my old e-mail address. now I can't use my old profile

I have change e-mail address after first registration and when I logged in it send new password to my old e-mail address. now I can't use my old profile.
and I can't install my old adobe X anymore
what to do?
Mika

Change Account https://forums.adobe.com/thread/1465499 may help
-wrong email https://forums.adobe.com/thread/1446019

(final cut pro x 10.0.9 )After numerous troubleshooting tips, I am still getting the dreadful your disk have ran out of space, your events have moved or permissions have changed. This happened after I moved some files to another drive. They won't relink?

(final cut pro x 10.0.9 )After numerous troubleshooting tips, I am still getting the dreadful your disk have ran out of space, your events have moved or permissions have changed. This happened after I moved some files to another drive. They won't relink eventhough the files are there.

(final cut pro x 10.0.9 )After numerous troubleshooting tips, I am still getting the dreadful your disk have ran out of space, your events have moved or permissions have changed. This happened after I moved some files to another drive. They won't relink eventhough the files are there.

Not allowing changes to payment terms after the AR document is released to accounting

Hi,
Anyone know the best way to not allow a user to change the payment terms after the AR document has been created in AR? This is affecting aging because users are changing the payment terms without permission. What is the best way to control that?
Thank you.
AK

Hi A K
Frequent change in payment terms is something business should introspect. Payment term is decided and agreed upon with customer/vendor during the initial stages.
However from IT perspective, it can be controlled keeping some system controls.
1. Limit the Customer master change transaction to very limited users or to a manager. There should be internal approvals by management for business to make a change. Bring this into force.
2. Regularly run the customer master change reports and provide the trend to management to restrict or limit the changes.
3. Use Change Message control for master data by providing necessary warnings or error messages when master data is changed.
4. In the sales order level, there is every possibility to change the payment term. Based on the user authorization get the payment term field greyed out and provide change access to accounting or to a specific user upon approvals. This is a bit complex process but I feel this brings up controls and stops the process from exploitation.
5. Also activate 'Sensitive fields' KNB1-ZTERM for payment term field in customer master. This brings up another layer of confirmation of change by other users.
6. Another back route, not recommended in all cases, is to subsititute the required payment term during accounting document posting.
Hope it helps.
Thanks,
Sekhar

How to change async to sync after deploying the process.? Thanks

How to change async to sync after deploying the process.? Thanks

you'd need to change the base wsdl, the generated one (_Name.wsdl) and the bpel.file .. and remove the generated classes .. (all in domains/you_domain/tmp/your_process dir)
the wsdl needs to get the output msg to the input msg instead of a callback porttype, the same needs to be in the generated wsdl (don't forget to remove the callback role in plnk session).. and the bpel process needs to have a reply instead of the invoke ..
this is what you would need to do .. BUT, maybe we can find a better solution for you, if you elaborate on the usecase..
during design time this is easier :-)
regards clemens

Behaviour change of synchronous reply after patching to 10.1.3.4

Hi people ,
i have a process like this:
[http://www.jettmedia.com/images/630_syncReply10134Test.jpg]
Normally in 10.1.3.1 , 10.1.3.3.x ; the process will continue after a partial reply, and any fault uncatched in the process would terminate the flow. And any changes to the outputvariable wont change the process response.
But after patching to 10.1.3.4 im having a different behaviour on synchronous process replys ,
The process continues and any uncatched fault AFTER A REPLY its raised to the client, and any change to the outputvariable AFTER A REPLY its changed to the process response .
The worst thing its that is not clear when the response its really sent to the client , ( if i put a wait activity , after the reply, with 1 minute , works as was expected, like in 10.1.3.3 ... )
I read this new features list from oracle
http://www.oracle.com/technology/tech/soa/cab/oraclesoacab-webinar-04-22-08bpel_10_1_3_4_update.pdf
It says that "Faults in a transient process go to the client" , correcting an old problem of lost instances..
I cant find any other documentation explaining this new beahaviour but for my organization its a huge problem afecting , many production processes, on the patched servers. Because i raised faults to leave the instances marked as faulted on the console as a normal procedure on the flows , but now , if that throw its close enough after a reply(with a unknow criteria or number of activities) its raised to the client :S
Thanks for any help , by now the workaround to keep the same behaviour its: WAIT after every reply :S :S !!
Greetings
Dam

Yes its a fire and forget pattern, thanks for the suggestion, il. try it ...
but its difficult to refactor several flows just for patching , you have any idea if this change after upgrade to 10.1.3.4 its normal ? this is an expected beahaviour ?
Thank you very much again

LSMW Vendor Change (XK02) by IDOC CREAMS05?

LSMW Vendor Change (XK02) by IDOC
Hi,
I have below queries for LSMW Vendor Change (XK02) by IDOC
I am using idoc type CREMAS05 for vendor creation , Now i want to update (Change) the vendor using the idoc.
1. will the IDOC type CREMAS05 work for vendor change (XK02) also?
2. when i am executing the LSMW with the IDOC type CREMAS05, it is throughing an error Message no. WY181 "Account group in the IDoc is different " "
Diagnosis
A change to the account group of a vendor master record cannot be made automatically.
The vendor with number 2000000148 currently has account group Z001. However, the IDoc contains account group .
Procedure
Change the account group manually to and then try to edit the IDoc
Please help me.
Thanks,
Babumiya Mohammad
<removed by moderator>
Edited by: Thomas Zloch on Feb 17, 2012

Hi Jürgen L.
Thanks for you answer , Now it is working.
Can you Please help me for CONTACT PERSON (create/ change) upload for vendor using the IDOC type CREMAS05.
which structure is appropriate for CONTACT PERSON in CREMAS05
Thanks in advance,
Babumiya Mohammad

How to block changes in purchase order after purchase release

Dear all
Can u please tell us how to block any changes in purchase order after purchase order is released...
(We don't want any line items addition or quantity addition or any changes once purchase order is released..)We wanted this for a particular purchase order type only
Regards
Sudha

Dear Sudha
Yes it is possible to confiquire your system insuch a way where once if the PO gets final relase then it cannot be changed.Only possiblity that will be available for the user to make chanegs in PO is possible when the final release is to be reset and then make the changes.
Release Indicator: specicfies whether the PO documents is blocked or can be processed for the follow functions.
You can define the release indicators you need for your release procedure:
The Released indicator is used to specify whether messages (PO documents in output format) may be transmitted for a purchase order with this indicator.
The Changeability indicator shows the effect of changes to the PO (a change to a PO may require a new release strategy to be determined, for instance).
By means of the Value change indicator, you can specify that the release strategy is to be re-started if a PO is changed and the value of a PO item thereby increases by a certain percentage (e.g. 10%). Set the Changeability indicator to "4 - Changeable, new release in case of new strategy or value change" or "6 - Changeable, new release in case of new strategy or value change/outputted" and enter a percentage in the Value change field.
And after that you can specify release statuese where you can specify which release indicator/status a PO is to have after having been released via a certain release code.
and after release simulation .
Test for the PO change after final release System will not allow you tomake changes by giving the message that the release indicator doesnot allow you make the changes in PO.
Regards
Sunny

Outbound Idoc after created Invoice document

Hi All,
May i know how to create outbound idoc after invoice document created.
Because i just found out some solution for inbound idoc.
Regards,
Luke

You need to set up the Output type using the NACE tcode and this output type should be configured to trigger the IDOC. Check the below link.
http://www.erpgenie.com/sapedi/messagecontrol.htm
This output type can be linked with the IDOC type in WE20 tcode.
~Srini
Edited by: VaasPal on Dec 22, 2011 8:13 AM

Database history growth not updating after EHP upgrade

Hi All,
We are using SAP ECC 6.0 (731 - SP09 ) & DB2 Fix pack 5 version.Database history growth not updating after EHP upgrade. I have check collector job running fin and DB tab > Configuration > Data Collection Framework > Configuration Collector are in green status.
Please help me to resolve this issue.
Regards,
MK

Hi MK,
You can try few things:
1. Check to collector standard job like SAP_COLLECTOR_FOR_PERFMONITOR should be running succesfully.
2.If you can check to data collector collection interval column , you will find it to be Not Schedule.
Try with Repair all collector.
To make it work properly you have to perform
Data Collection Full
Data Collection Incremental
Hope it helps
BR Vaibhav

Changes to SHPMNT03 Idoc after EHP 5.0 upgrade?

Similar Messages

Maybe you are looking for