IDOC Sender

hi all
Am doing a scenario with Idoc as sender. I ve send the IDoc successfully from r/3 system. But nothing is reaching xi. Is there nythin to be done at xi part. Any port to be created . Please help me

Hi,
For sender case u just need to create RFC destination with that R/3 system on XI box.
Got to tcode SM59 create RFC destination then go to R/3 system resend IDOC and then go to tcode IDX5 in XI and then check if there is any inbound iDOC entry in XI.
If it is there then create port with tcode IDX1 and check IDOC metadata with tcode IDX2.
Thanks.

Similar Messages

IDOC sender: Error in Logical system name?

Hi,
In my current project, the IDOC sender system logical name is P2PCLNT100 but the SLD system name is P2P.
Its an IDOC to proxy scenario. At the receiver system side, the schemeAgencyID is getting populated at P2P and not P2PCLNT100, due to which there is an error on the receiver's side.
Following is already checked:
1. SLD has maintained the proper logical system name for the P2P system
2. The IDOC xml on the XI system has the sender port properly populated as P2PCLNT100
3. I have also debugged the program on the receiver side and fails at a point where it checks the logical system name from the database BBP_BACKEND_DEST.
On the receiver system, the followed error is shown as follows:
- <STANDARD>
<CONTROLLER />
<FAULT_TEXT>An error occured within an XI interface: SLD system P2P is not known Programm: SAPLBBP_BD_MAPPING_SAPXML1; Include: LBBP_BD_MAPPING_SAPXML1F1Y; Line: 96</FAULT_TEXT>
<FAULT_URL />
<FAULT_DETAIL />
</STANDARD>
Thanks in advance for the useful answers.
Sowkhya

Hi,
1. R/3 system's logical system name and SLD business system's logical system name has the same.
Is there a need to have the business system name in SLD to have the same name as R/3 system logical name?? As far as my knowledge goes, business system and logical system need not have the same name. Correct me if in the case IDOC sender scenario is different..
2. SLDCHECK shows following message:
Summary: Connection to SLD does not work
The issue still persists. Will SLDCHECK correct solve the issue?
Regards,
Sowkhya

IDOC send step not running with exception in BPM?

Hello,
hope this is a simple question, but we are running with a problem here which is not answered well in SAP help or sdn. Possibly I didn´t find the right blog.
Situation:
We created a BPM with a send step (IDOC receiver) in a block (after a receive step starting the BPM) (That´s simple so far!).
The send step (async IDOC) in the block is connected in its attributes in field "system error" to an exception branch defined in the same block.
In this except.branch the process should send back to sender system a message via RFC and the last step in this exception branch is to interrupt the proces.
But now we tried to do a test. In this test we modified the receiver address of the send step (IDOC reciver) so that the receiver could not be reached, which results in a system error in SXMB_MONI (Service unavailable).
But this doesn´t work. The BPM starts the send step to the unavailable receiver, SXMB_MONI shows a system error step, but then the BPM continues with the next step after the block without starting the exception branch.
Any idea why the exception branch is not called?
Best regards
Dirk

Hello again,
we are one step further now.
We did the same with an RFC instead of the IDOC send step.
Same result:
The service is not reachable. So the step results in an system error.
But as we could see in the monitoring SXMB_MONI the block with the exception and this send step (RFC) is passed before the step gives back this error!
So it looks like connection problems do not trigger an exception?
Any help is welcome!
Best regards
Dirk

Idoc Sender Configurations

Hi,
Our requirement is to do Idoc to File scenario in which what are all the configurations that are to be done in R/3 and as well as in XI server.
regards,
Kishore

Hi Kishore,
Please go through /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
also i give a quick checklist, chk it out.
1)Create an RFC destination to XI in the sender SAP system using SM59
2)Create a transactional port to XI using the RFC destination created in the above step
3)Create a Partner agreement usign transaction we20 and port using we21 in the sender SAP system
4)Create a logical system using transaction bd54 for the partner agreement created in the above step
5)Select an IDOC using transaction we19 and change the EDIDC header recepient port & LS name
6)Create an RFC destination to the Sender SAP system using SM59
7)Create port to sender system using idx1 in the XI system for the RFC destination created in the above step
8)Create SLD entries(technical and business system) for the sender SAP system.
In IR , import IDOC metadata, create ur target XSD , create ur Message Mapping , Interface Mapping, thats it.
In ID, import ur sender R/3 system & receiver systems, U dont need a IDOC sender CC , so only File receiver CC is reqd. Now create a receiver determination, interface determination & receiver agreement ,activate & ur done.
Use WE19 , select an IDOC and do an outbound processing and u shud see the IDOC in XI.
Rgds
joel
Edited by: joel trinidade on Feb 23, 2009 2:44 PM

IDOC sender system settings

Hi,
I am trying to do the settings for the idoc sender system the steps i have completed are..
1) sm59..maintain a rfc destination from idoc sender to the integration server.
2) we21..created a tRfc port with the rfc dest from step1.
step 3 is where i am stuck...
3) we20....to maintain the partner profile and partner number...there isint enough info in the xi config guide..
any pointers..would be appreciated.
Regards
Ravi

ALE settings.
SAP XI1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP XI towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
In SLD System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name.

Idoc sender issue

Hi,
I have an issue in Idoc sender scenario.
The flow is Idoc to BPM to Flat file.
Idoc is triggered from R/3 system via RFC port. It enters XI which is visible in Moni. But data is not there.
Which transaction to use to trace Idoc in XI?
I can see the Idoc successfully sent in we02 from R/3 system. But no data in Moni in main message or attachment.
Regards,
Anirudh.

Hi
Go through following ALE step, check whether you missed any of these steps:
Steps for ALE settings:-
Steps for XI
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the R3 system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto IDX1.
     Create a new port.
     Give the port name.
     Give the client number for the R3 system.
     Select the created Rfc Destination.
Step 3)
     Goto IDX2
     Create a new Meta data.
     Give the Idoc type.
     Select the created port.
Steps for R3.
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the XI system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto WE21.
     Create a port under transactional RFC.(R3->XI)
     Designate the RFC destination created in prev step.
Step 3)
     Goto SALE.
     Basic settings->Logical Systems->Define logical system.
     Create two logical systems(one for XI and the other for R3)
     Basic settings->Logical Systems->Assign logical system.
     Assign the R3 logical system to respective client.
Step 4)
     Goto WE20.
     Partner type LS.
     Create two partner profile(one for XI the other for R3).
     Give the outbound or inbound message type based on the direction.
Step 5)
     Goto WE19
     Give the basic type and execute.
     fill in the required fields.
     Goto IDOC->edit control records.
     Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)
     Click outbound processing.
Step 6)
     Go to SM58
     if there are any messages then there is some error in execution.
     Goto WE02.
     Check the status of the IDOC.
     Goto WE47.
     TO decode the status code.
Step 7)
     Not mandatory.
     Goto BD64.
     Click on Create model view.
     Add message type.
Regards
Sami

R/3 to XI manually IDOC sending and problem:

R/3 to XI manually IDOC sending and problem:
I sent IDOC using we19 transaction from R/3 system. After sending it asks me userid and password for XI system. I give necessary UID and PASS. R/3 system says me sucessfully sent.
I check XI (sxmb_moni) but there is nomessage there.
Problem 1: I don't want R/3 ask me UID and password for XI access
Problem 2: I want to see message in XI (sxmb_moni)
Thanks

Hi Cemil,
>>>>After sending it asks me userid and password for XI system. I give necessary UID and PASS. R/3 system says me sucessfully sent.
check the RFC destination from R3 to XI (SM59)
you will find the right one from your port (We21)
you can also check step by step procedures
for IDOC - XI in my book:
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi">Mastering IDoc Business Scenarios with SAP XI</a>
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Message mapping: SOAP Receiver to IDOC Sender

hi,
i have an idoc sent to SOAP receiver. SOAP Response will have only the "Status code" and the "Reason of failure".
IDOC Sender will have the PO Number and the Vendor Name to which we are sending.
The SOAP Response will not have the PO Number and the Vendor Name.
How can i have the Reason of failure, PO Number and Vendor in one message type?
Thanks in advance,
Tirumal

Praveen -
Thanks for the response and appreciate your observation.
Very tight deadlines with the client and have to finish lot of tasks in short time so putting hands in everything.
There are lot of vendors who run their proprietary web services. So cannot change their stuff.
How would i map the SOAP request to the SOAP Response since some information is in one message type and other half of information available in other message type.
I created a SOAP Response Type with the "Reason Code" information.
I created another message type with all the information that i want.
How would i map the SOAP Request to the SOAP Response msg type and the other message type.
Let me know.
Thanks in advance,
Tirumal

Java IDOC_AAE configuration issue in PI IDOC sender channel and in ECC SM58.

Dear Experts,
My configuration scenario is outbound: SAP (IDOC)-------->PI------->AS2 ThirdParty.
SAP PI version: 7.31 dual stack.
First time i have done IDOC_AAE settings done in ECC and PI NWA with the help of below links.
http://scn.sap.com/docs/DOC-34155
http://scn.sap.com/docs/DOC-31398
While sending the DESADV.DELVRY05 standard idoc from ECC to PI i am getting below error in Sender IDoc channel.
Could you please help me on this issue ,I will appriciate you .This is very urgent.
Error in PI IDOC Sender channel : Processing error = Value with name ApplyCntlRecFromPayload not available
and I are getting below error in SM58 ECC system.
Error in ECC SM58: Commit fault: ASJ.ejb.005043 (Failed in component:
Thanks,
Aadi

Hi Aadi,
Please check the below SAP notes
1952406 - "Commit fault" error in SM58 transaction when sending IDOC from backend system to PI sender Java IDOC adapter
1928302 - Possible NullPointerException with IDOC_AAE sender channels processing
reference - Commit fault: ASJ.ejb.005043 (Failed in component: sap.com/com.sap.aii.ad) while sending to PI system
also check the link - http://saphelp.me/commit-fault-asj-ejb-005043/
regards,
Harish

IDOC Sender Adapter and Receiver Adapter

Hi,
Why we don't require IDOC Sender Adapter to communicate with PI and why IDOC Receiver Adapter is required to communicate with SAP ?
Regards,
J Augastine

Hi,
>>>Why we don't require IDOC Sender Adapter to communicate with PI
you're talking about sender and receiver agreements right ?
as this adapter is based on abap stack - with new functionalities of IDOC adapter
require sender agreement
>>>and why IDOC Receiver Adapter is required to communicate with SAP ?
as we need to put the RFC to the destination system somewhere...
Regards,
Michal Krawczyk

Unable to convert partner to IDoc sender partner

In XI 2.0,we are facing a problem while trying to send idoc out of XI to SAP R3 system.We created Business Systems without specifying ALE logical system name,but later we corrected this.
Even then we are getting this error:
<SAP:Code p1="I::000" p2="SRMSUS_BUSS_SYS" p3="" p4="">IDOC_ADAPTER.SENDER_BSI_INCORRECT</SAP:Code>
<SAP:Text language="EN">Unable to convert partner to IDoc sender partner</SAP:Text>
We have created port in IDX1 in XI for R3 system.
Suggest us ?
regards
Vishal

Vishal,
Add your agency and schema values in both party and receiver idoc channel (tab identifiers),
it should be something like
BS_ (your R/3 system system), Schema ALE#KU# (KU if its customer)
Thanks,
Pavan

IDoc adapter inbox: IDoc sender partner is initial

Hi,
I have requirement to read the IDOC flat file and post IDOCs to SAP. As suggested in the following guide I am using report RSEINB00 to post IDOCS. This report basically calls the function module IDOC_INBOUND_FROM_FILE.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/xi-how-to-guides/how%20to%20convert%20between%20idoc%20and%20xml%20in%20xi%203.0.pdf
While executing the IDOC_INBOUND_FROM_FILE I am getting error:
"IDoc adapter inbox: IDoc sender partner is initial".
Please advise.
Thanks
Rajeev Gupta

Hi,
Idoc will be processed in SAP ECC based on the sender details (snprn,sndpor,sndpfc...) of idoc control record..
instead of different partners name sending in the sender details of control record ...pass the value of the PI logical system name in SNDPRN.... (use only one and this is common for all partners...) any how data records of idoc will have the needed partner details...
In SAP ECC you need to have this logical system ...to process the received idocs..
thats it... Hope you got
Regards
Rajesh

Idoc Sender Id

Please help,
What is an IDOC Sender ID.
And where can i get it from SAP.
Thank you.

Hi,
Idocs are basically intermediate documents transmitted between Business Partners like Customer / Vendor, Banks etc.
You can view a Idoc in transaction code WE02. Double click on one of the Idoc record and then click on Control Record. Here you can view the tab Partner. If you click on that you can view the details of Sender like Partner number / Partner type etc.
Thanks
Murali.

Error to IDOC Sender

Dear Experts,
I have a requirement to send error information back to the IDOC Sender. The scenario is IDOC --> PI --> TargetSystem (ASYNCHRONOUS).
If there is an error in processing within SAP PI, then the error should be propagated to the SAP system (IDOC), so that the Business can take note of the error.
As far as I know, we can configure Alerts in SAP PI and in case of an error the recipient will get the alert message. But how to send the error message back to sender in case of an IDOC
I do not want blogs on how to configure alerts in ALRTCATDEF
Thanks.

although I think you mean the person that triggered the IDoc, ie. someone who created a SalesOrder, which was then sent
to PI.
Yes, this is what is required.
With this UserID you can do a lookup in the sender system, to retrieve the email-adress in the User Master Data record.
Then use this email adress to send an alert,
How exactly the lookup will be done? I have a message processing running in SAP PI, suddenly something goes wrong (lets say there is a mapping error) and the processing stops there. Now how to do a lookup (from where)? Configuring a fixed recipient in ALRTCATDEF wont work as we dont know who will trigger the IDOC!
Any reference on how to perform lookup when message fails in XI/ PI will be helpful.
Thanks.

Why IDoc Sender Channel Used in Outbound Scenario's

Hi Team,
In my outbound scenario's ,I never used IDoc sender channel.Only ALE settings I have configured..PartnerProfile,RFC dest,Port etc.
Why can we use Idoc Sender channel? Is it only used for IDocFlat file format OR for normal Idoc's also? If we use Idoc sender Channel , how it is processing - Is it TRFC queues-sm58 ?
Can you give me clear idea on it / suggect any blogs.
Thanks.
Drumi

HI,
In my outbound scenario's ,I never used IDoc sender channel.Only ALE settings I have configured..PartnerProfile,RFC dest,Port etc.
Why can we use Idoc Sender channel? Is it only used for IDocFlat file format OR for normal Idoc's also? If we use Idoc sender Channel , how it is processing - Is it TRFC queues-sm58 ?
we dont necessary to create Sender Communication channel for IDOC and Proxy and http because xi and sender systems(out bound) resides on abap stack and also dont need for any idoc.
The reason is that R/3 can directly send Idocs to XI via ALE layer using RFC destination specified in SM59.
This IDoc after reaching XI is converted in IDoc-XML. This is done when we specify IDoc metadata IDX2 in XI. It is then used in IR for mapping.
Now for the receiver side, when IDoc-XML is created after mapping program run is sent to R/3. Before that, it has to
be converted into IDoc. This conversion is IDoc-XML to IDoc is done by IDoc Receiver adapter.
one case we need to create sender IDoc Communication channel for IDOC packaging concept thats all.
thanks,
Edited by: bhavanisankar.solasu on Dec 16, 2011 7:12 AM

Generic IDoc Sender

I am creating a SOAP/HTTP -> PI -> IDoc scenario. I have it working when I create a sender interface of data type ORDERS.ORDERS05 (or any particular IDoc). I am creating a WSDL and the client uses it to send IDoc data.
Now I am trying to create a generic IDoc sender...one where any type of IDoc can be sent and the sender interface is maybe just a string and conditionally somewhere along the line I will need to determine the IDoc type for the IDoc receiver interface. I am getting various errors (most recently, "unable to find an inbound interface").
Anyone know that this is possible and have recommendations?
Thanks,
Keith
Edited by: Keith Wendel on Sep 28, 2010 7:36 AM

along the line I will need to determine the IDoc type for the IDoc receiver interface.
How are you going to do that?

IDOC Sender

Similar Messages

Maybe you are looking for