on 02-15-2006 4:42 AM
Iam trying to post IDoc(cremas03) with File --> XI --> Idoc Scenario.
I got message processed successful in SXMB_MONI.
However on ECC5.0(R/3) I got Idoc status 56.
EDI: Partner profile inbound not available
Message no. E0337
Diagnosis
An inbound partner profile could not be found with the following key:
/T20CLNT400/LS//CREMAS////
This involves the key fields of table EDP21:
-SNDPRN partner number of sender
-SNDPRT partner type of sender
-SNDPFC partner function of sender
-MESTYP logical message type
-MESCOD logical message code
-MESFCT logical message function
-TEST test flag
Procedure
Please check the inbound partner profiles.
Execute function
On IDOC Display (We02) I found following info:
Technical Short Info
Direction : 2
current status: 56
Basic type: cremas03
Message type: cremas
Partner No: T20CLNT400
On Idoc control Record:
Typeinfo tab:
Basic Type: CREMAS03
Message Type: CREMAS
Partner Tab:
Recipient
Port: (Spaces)
Partner No: ID3CLNT550
Partner Type: LS
Sender
Port: SAPSXI
Partner No: T20CLNT400
Partner type: LS
Tech Info:
Sap rel : 640
On Partner Profiles:(WE20)
ID3CLNT550 ( in this case receiver) was defined as Logical Sytem and Inbound message type CREMAS
Would someone please guide me what to do as Iam learner of XI.
Thanks a lot
Hi ,
Please check in Tcode BD64 :
Environment --> Generate Partner profile
whether it is successfully generating the parner
profile
or
Goto Tcode : WE20 partner profile and check the
inbound parameters like "process code" .
Shikha
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Here it is.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Adapter
-->
- <SAP:IDocOutbound xmlns:SAP="http://sap.com/xi/XI/Message/30">
<SAP:TABNAM>EDI_DC40</SAP:TABNAM>
<SAP:MANDT>400</SAP:MANDT>
<SAP:DOCREL>640</SAP:DOCREL>
<SAP:DOCNUM>0000000000046232</SAP:DOCNUM>
<SAP:DIRECT>2</SAP:DIRECT>
<SAP:IDOCTYP>CREMAS03</SAP:IDOCTYP>
<SAP:CIMTYP />
<SAP:MESTYP>CREMAS</SAP:MESTYP>
<SAP:MESCOD />
<SAP:MESFCT />
<SAP:SNDPOR>SAPSXI</SAP:SNDPOR>
<SAP:SNDPRN>T20CLNT400</SAP:SNDPRN>
<SAP:SNDPRT>LS</SAP:SNDPRT>
<SAP:SNDPFC />
<SAP:RCVPOR>SAPECC</SAP:RCVPOR>
<SAP:RCVPRN>ID3CLNT550</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
<SAP:RCVPFC />
<SAP:TEST />
<SAP:SERIAL />
<SAP:EXPRSS />
<SAP:STD />
<SAP:STDVRS />
<SAP:STATUS />
<SAP:OUTMOD />
<SAP:SNDSAD />
<SAP:SNDLAD />
<SAP:RCVSAD />
<SAP:RCVLAD />
<SAP:STDMES />
<SAP:REFINT />
<SAP:REFGRP />
<SAP:REFMES />
<SAP:CREDAT>0000-00-00</SAP:CREDAT>
<SAP:CRETIM>00:00:00</SAP:CRETIM>
<SAP:ARCKEY>BAA624009F6311DA8AD3003048805A88</SAP:ARCKEY>
</SAP:IDocOutbound>
Following data was defined in receiver system, Client 550
Inbound parameters:( With we20)
-
PartnerNo: ID3CLNT550
Type: LS
Inbound parameters:
Partner Role : LS
Message Type: CREMAS
Process Code : CRE1
Trigger immediately
-
PartnerNo: ID3CLNT550
Partner Type: LS
Inbound parametrs:
Partner role: <---- blank here ..does this matter ?
Message Type: CREMAS
Process Code: CRE1
Trigger immediately
-
here is right Partner profiles defined in rceiver system. Aplozise for confusion:
Following data was defined in receiver system, Client 550
Inbound parameters:( With we20)
-
PartnerNo: ID3CLNT550
Type: LS
Inbound parameters:
Partner role: <---- blank here ..does this matter ?
Message Type: CREMAS
Process Code : CRE1
Trigger immediately
-
PartnerNo: T20CLNT400
Partner Type: LS
Inbound parametrs:
Partner role: LS
Message Type: CREMAS
Process Code: CRE1
Trigger immediately
-
Thanks
Try creating a partner profile for the receiving system with the same name that's there in the ID(BusinessSystems-Adapter specific attributes)which could solve the problem sometimes.
Vasanth.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Your Error shows that your idoc was added incorrectly
probably you check your partner profile in the receiver system which should have the same message type as in sender outbound profile.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ram,
It looks like your Idoc is added with errors(status 56) in the backend.
To fix your problem, get the added Idoc Number using TR.code WE05, go to Tr.code WE19(Test Tool for Idoc Processing).
This Test Tool also allows you to edit and debug the data. Edit the control record(EDIDC)and change the values and process it again. This way you will know where the problem is.
Hope this helps.
Regards,
Sam Raju
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.