Send PO idoc after release
Hi SAP masters,
The requirement is to send PO Idoc to the vendor after the purchase order is relaease. Does anybody know which message type and process code should I use?
Thanks in advance to all.
Fred
Hi,
With the message type ORDERS the Idoc is generated and send to the Vendor after PO is release. Works fine.
The problem I have is that we are using Vendor Managed Inventory VMI and the vendor only can received as a PO confirmation message type ORDCHG (the one that SAP recommends for this functionality).
The message type ORDCHG also works. But the problem with this is that SAP send this message when the PO is created, not when the PO is release. And that is a problem.
One thing I discover is that the message type ORDCHG, with message variant VMI in partner profile, send the Idoc without any Output Message. SAP send the ORDCHG Idoc after received the Idoc which generate the PO in our system (ORDERS). And that is strange that I cannot control when send the PO confirmation Idoc to the vendor through the Output Type determination.
So, I have problems with the two message type ORDERS and ORDCHG. The perfect solution would be send ORDCHG after the PO is release, but that do not work.
Any suggestion?
Thanks.
Similar Messages
-
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 -
Way to Send Purchase order Information to XI after Release?
Hi All,
Can anybody suggest me a way how can I send purchase order information to XI immediately after releasing the PO.May be User exit, Idocs,BTE?
Thanks in advance?
AnilHi,
Since you have to send the Release information to XI.
Best way is to send thru IDOC.
IDOC Type is :ORDERS05
Thanks -
How to send an idoc of lower release to an External RFC server
Hi All,
I am sending idocs from the sap system to an external rfc server(written using Sap RFC SDK).
When an idoc is sent from the Sap system, I receive an IDOC_INBOUND_ASYNCHRONOUS call in the external RFC server with the Idoc data.
Everything works fine with the latest release of idocs. But if I send an Idoc of lower release number, I am getting the data records properly for the lower release(say 640). But the DOCREL field (in the control record- EDI_DC40) always gives me the latest release number(700)
In my partner profile, I specify the Segment release number to 640 and even then I am receiving the value 700 in DOCREL.
What am I missing here? How can I populate the DOCREL field with the appropriate release number?
Any help would be greatly appreciated.
Thanks
PS: Please feel free to move this post to appropriate category, if this is not the one.Serigo,
Thanks for your reply and we are not using XI.
I have defined in the port definition giving the path name refering to unix like /outbound/<system name>/<directory name>. But I dont know how to define for C:\temp\, if I define the same way as c:\temp\ do I need define anything anywhere else ?
Kindly let me know.
Thanks,
Kalikonda. -
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 (0xHi 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 -
Error to send a IDOC from ECC to SUS
Hi,
I am trying to connect to SAP SUS System using HTTP adapter using PI 7.0.The scenario is
ECC ->PI->SAP SRM. I have configured HTTP adapter as the receiver with addressing type as HTTP Destination. I have created a RFC destination of type H pointing to SAP SUS on PI. I have encountered the following error after executing the scenario.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Adapter
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_SERVER</SAP:Code>
<SAP:P1>500</SAP:P1>
<SAP:P2>Internal Server Error</SAP:P2>
<SAP:P3>Error during parsing of SOAP header</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>HTTP server code 500 reason Internal Server Error explanation Error during parsing of SOAP header</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I have configured HTTP receiver with Addressing type HTTP Destination and configured the HTTP destination field with RFC destination(Connection Type H) created on PI. Here my source and target structures are same i.e DELVRY03. I have triggered DELVRY03 idoc from ECC and i am expecting same xml to be sent to SAP SUS but stuck up with the above mentioned error.
Someone know how fix this problem?
Tks,
ErikHI,
As per my understanding to your scenario, You want to send one IDoc from ECC to SAP SUS system using SAP PI.
So i hope you must have configured on all the steps required to Send one IDoc to PI syste, Secondly, are you using any Standard interface in PI to send data to SAP SUS system? If yes, you need to create an HTTP Destination for that system and then you have to create XI Receiver Adapter with that HTTP destination to post incoming message to SAP SUS system.
Your error suggests you are using Plain HTTP adapter to post data to SAP SUS, which is in my understanding is incorrect.
Regards
Aashish Sinha
Edited by: Aashish Sinha on Feb 21, 2011 9:15 AM -
Changing Purchase Reqs after release.
After releasing a Preq (Cost Centre), if we attempt to change it in ME52N everything on the line's display only. So I can't increase the qty for example and send for re-approval (trigger the release strategy). This is normal?
The Changeability indicator in OMGQ for the release indicator (F - released) was blank. I changed this to 4 but neither allow us to change the Preq after realease. Could you maybe advise please? Is it possible to change the req after release, seems odd I can't?Hello,
in customizing for release indicator, you must check also field "Field selection key" which is defined under "Material management --> Purchasing --> Purchase requisition --> Define screen layout at document level". You should check the "Field selection key" assigned to your release indicator: that key defines the mandatory, optional and view-only fields in Purchase documents, and can be linked to a release status.
Hope to be useful.
Best regards,
Andrea -
Adding some code before sending the IDOCs
Hi all,
I have one query. When I am doing some transaction system is generating the IDOC with status 03. Now My requirement is to send this IDOCs to the destination system after checking some conditions. So I want to insert to some code in the ALE configuration, so that it can filter the IDOCs based on my bussiness requirement. This is not simply checking one field, i have to write some logic after that only system should send the IDOC, Can you please tell me how to include the code?
Thanks & Regards,
RaghuHi,
There are two ways you can do it:
1. Using Filters(Tcode BD64) & Convertion rules(Tcode BD55, BD62 & BD79).
<b>Filter:</b>
http://help.sap.com//saphelp_470/helpdata/EN/0b/2a611c507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/12/83e03c19758e71e10000000a114084/content.htm
<b>Conversion Rule:</b>
/people/kevin.wilson2/blog/2005/12/07/changing-fields-in-an-idoc-segment
2. Check for the user-exit or BADI to add your business requirement.
To get the exact solution please add the business scenario.
<b>Note:</b> Reward each useful reply.
Raja T
Message was edited by:
Raja T -
Hi all,
I am doing a test Idoc to File interface. Can anybody tell me how to send an Idoc from R/3? I am trying to send using we19 transaction.
I am selecting basic type and after giving appropriate values, i am clicking on <b>Standard outbound processing</b> button. Now i am getting an error saying: "<b>Port " does not exist in the table of port descriptions</b>." I tried to mention the port and partner profile information in <b>Idoc->Edit control record</b>. But it is still giving the same error.
Can anybody help me with this?
Thanks in advance,
Divija.Divija,
The sener port will be r3's port and receiver port will be XI's port.
In partener prolfile, as you are sending the IDOC from the r3 to XI, the entry will be as an <b>outbound paramter</b>.
Logically, this is how it works, for the R3 , the partner is XI and it is sending it to XI and so, an entry is made in the Outbound side for the same.
Regards,
Bhavesh -
Which program can send SYSTAT01 idoc?
Hi gurus,
Our scenario is SOAP to IDOC(async interface to async interface), and after the inbound processing of R3 side, we want send the processing status back to outer system via PI. It seems ALEAUDIT is not enough for our requirement, because sometimes the key value the outer system sent doesn't appear in the ALEAUDIT01 idoc, so in this case the acknowledment is useless to the outer system. Or I get it wrong? Can we find some user exits in program RBDSTATE?
Then we go to SYSTAT01.It was said this idoc was used in EDI cases, but I don't know which program to send it on the R3 side just like RBDSTATE can send ALEAUDIT01 idoc?
Any help will be appreciated.Hi,
Why cant u make another interface and use this idoc SYSTAT01 -
How to send PO IDOC from SRM server
Hi All,
How to send IDOC, after successful creation of the PO in SRM ?
Please tell me how to configure the SRM system ?
RegardsHi,
See the foll related useful link:
Re: Intercompany process u0096 MM u0096 SD
BR,
Disha.
Pls reward points for useful answers. -
Send/Receive IDOCs (XML) from/to SAP R/3 with XI-SOAP without XI!
Dear SAP specialists,
(BACKGROUND) We are using the Microsoft BizTalk Adapter for SAP 1.0, developed on top of the SAP DCOM Connector (we are using the version 6.20 Patch Nr. 177), with Microsoft BizTalk Server 2002 SP1 in order to send and receive IDOC via the tRFC transport protocol. We are using the Microsoft BizTalk Adapter for SAP 1.0 since February 2002, and today we are exchanging more than 25,000 IDOC/day with this architecture.
When we migrate our SAP R/3 system to the version 4.7 with WAS 6.20, I was very enthusiastic about the possibility of sending the IDOC in XML via the standard HTTP transport protocol, because it would considerably simplify my architecture, i.e. no need of any (expensive) adapter any more! But, I had to realise that the quality of service exactly once will not be there anymore with HTTP as it exists with tRFC. Then, we carry on using the tRFC transport protocol with the adapter.
(QUESTION) But recently, I followed the SAP Course TBIT40 XI Foundations and I learn that:
1. On one hand, the XI-SOAP protocol supports the quality of service exactly once by the usage of a message GUID within the XI-SOAP envelope;
2. On the other hand, all mySAP solutions using WAS 6.20 (or higher) carry a small Integration Engine (with XI-SOAP as the native transport protocol).
Then, my question is: << Is it possible to exchange IDOC (XML) directly with an SAP R/3 4.7 (WAS 6.20) via the XI-SOAP transport protocol using the small Integration Engine embedded into it, with the quality of service exactly once? >>
Many thanks in advance and best regards,
Patrice KrakowHello Patrice
We have same issue. Is it possible to use IDoc (XML) directly with SAP 5.0 with SOAP (HTTP) without XI?
Since your que is three years old, I'm sure you must have found some method for this.
We'll highly appreciate your help.
Regards: Gaurave -
Not working imessage!! Credit card and I can not send imessage than after apple id. There are problems with Apple seeverele?? Thanks!
Before the service reset function. Wait 24 hours to activate imessage.go to the settings and turn off imessage
but that don't change the issue that you will never be able to facetime eachtoher
the appleID is really meant as the handle that identify you it was not meant to be shared
but can see that people may want to do not buy apps more then once -
Change the description of the change request number" in SE10 after release
Hi All
Is there way to change the
"description of the change request number" in SE10
after releasing the change request number?
appreciate your feedback
Thanks you
IverHello
I do not know a way to do it in se10 but a simple program could do the trick.
Include the following code in your program.
update e07t set as4text = 'your new description'
where trkorr = your_cr and langu = 'E'.
Of course you will have to wrestle with the 'moral issue' of directly updating SAP delivered tables
Regards
Greg Kern. -
Issue with the configuration of http xml port for sending the idoc
Hello,
I am planning to send multiple idocs in a single file using http xml port.
Presently I am trying to send a single idoc, but am having the issue.
I am trying to create a RFC for HTTP XML port of type H i.e. HTTP Connection to ABAP System
In the how to guide for - How Tou2026 Send Multiple IDocs Within One XI Message
( https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/30ea2fdf-f047-2a10-d3a2-955a634bde6b )
the following parameters are defined for the path prefix -
RFC destination of type H (HTTP Connection to R/3 System).
Specify the path prefix as follows:
/sap/xi/adapter_plain/
?namespace=< your namespace>
&interface=<IDoc_Type>
&service=<Sender System>
&qos=EO (or EOIO).
I am trying to use the following prefix -
/sap/xi/adapter_plain/
?namespace=urn:sap-com:document:sap:idoc:messages ( this is the standard namespace of SAP for all the idocs)
&interface=DEBMAS05 (Idoc type )
&service=SNDLS100 ( ECC system name )
&qos=EOIO
On testing the RFC connection, I am getting the error of page not found.
Can anyone please give me pointers for the issue.
Regards,
MayankThanks Barry!!!
Now I am getting a different message.
In RFC...it is giving me the following message ->
Status HTTP Response 204
Status Text Body is empty
In case of Idoc, the status is till 02...
the error description for the idoc is --
"When transferring the IDoc by HTTP, the return code with the message '500<SAP:Error><SAP:Category>XIServer</SAP:Category><S' has occurred.
The target address was: http://emgeccsnd1:8001/sap/xi/adapter_plain/?namespace=urn:sap-com:document:sap:idoc:messages&interf
Check whether the IDoc can be sent again.
It is unfortunately not possible to determine automatically whether the IDoc has in fact arrived in the target system and the error occurred afterwards"
I am still not able to resolve the issue.
Regards,
Mayank
Maybe you are looking for
-
Submitting XML Publisher Concurrent Program through PL/SQL
Hi, I am trying to submit a XML Publisher concurrent program through PL/SQL API fnd_request.submit_request. The request gets fired and completes successfully but it doesn't pick up the default template attached to it. Its output is plain XML but expe
-
Hello! I am having a problem with a Pages document that has many footnotes. On some pages the body of the text is blurring into/overlayed with the footnotes. I can find no pattern to this; it is not happening any more frequently on pages with many
-
Swing problem: table is not refreshed when i open it from jdialog
Hi , my situation is this one : 1. i have a swing form. 2. i have created a panel form where i have a drop down list and a table. wich are depndend with each other. When i choose an item to the drop down list the value in the table is changed. 3. i i
-
hi experts, I did system copy solman 701. but I found short dump 'SAPSQL_ARRAY_INSERT_DUPREC' per every hour. I attach part of short dump. =============================================================================== Runtime Errors SAPSQL_ARRAY_INS
-
My granddaughter install candy rush for me and I was playing fine and I do not have a problem when in need to buy life's but it doesn't let me go any further and I enjoy playing with my friends .Iam in level 41 and will like to see if you can help me