Assignment IDX1 port to sender idoc adapter ...

Hi gurus,
I have a big problem and I don't have any idea how to solve it. Please, help me.
I have a non-SAP system, regular SAP ERP and SAP XI and I need to transfer IDocs between them.
There is no problem to send IDoc from ERP to XI and forward it to non-SAP system. Unfortunatelly communication in opposite direction doesn't work. XI is not able to receive IDoc sent from non-SAP system because appropriate metadata can not be found in IDX2 cache.
In configuration of communication channel for sending IDocs to non-SAP (receiver idoc adapter) I selected IDX1 port that is directed to the ERP and it's worknig fine. I can send IDoc from XI to non-SAP.
But in configuration of communication channel for receiving IDocs from non-SAP (sender idoc adapter) is not possibility to determine any port. Does exist a way how to force sender idoc adapter to use some specific IDX1 port?
Thank you in advance for every reply!
Regards,
Zbynek

The IDocs are sent from non-SAP system by means of tRFC. Connection type of the RFC destination is type T (TCP/IP) and activation type is Registered Server Program.
If we sent the IDoc directly into SAP ERP (where the IDoc Type is known) everything is fine
Edited by: Zbynek Kabrt on May 19, 2009 8:59 PM

Similar Messages

Why do we require Receiver IDoc Adapter wen Sender IDoc Adapter is not req?

Hi All,
We require Receiver IDoc Adapter( if the receiving System is R/3 and uses IDoc) but when sending BS uses IDoc, Sender IDoc Adapter is not required since it resides in ABAP Stack. So, can anyone explain me as why do we need to configure Receiver IDoc adapter?

Hi,
Both the sender and receiver IDoc transmission is done by the RFC communication channel.
In case of the sender IDoc, partner profile configuration in the sender system will tell for a particular IDoc type which port should be used. This port will have the details of the RFC channel to be used to deliver the IDoc.
However, in case of SAP XI/PI system we don't configure partner profile and hence we need a way to tell which port & RFC destination should be used to deliver the IDoc and hence we define a receiver aggrement and adapter. This is just used as a reference at rutime and unlike the other adapter, this receiver IDoc adapter doe's not process any message over Adapter engine.
Hope this helps...!!!!
~SaNv...

Why no sender idoc adapter .

hi,
while configuring idoc to file ......... why we are not using sender communication channel or configuring sender idoc adapter ..............
thanks in advance,
jp.

The main use of a sender adapter is to convert the input format into an XI supported XML format. Once this is done, the sender agreement appends the header with the sender details. In the case of IDoc adapter, you would not require a sender agrrement or a sender channel for the following reasons
1. The adapter resides on ABAP stack hence the integration server takes care of the IDoc to XML conversion without requirement for adapter.
2. The business system that is sending the adapter has already been assigned to a technical system which normally acts as an Integration server.
3. In the system, you fill in the adapter specific identifiers where you define under the IDoc adapter, the Logical system name and the R/3 client and the number.

Doubt in Sender IDoc Adapter

Hi Gurus
I have doubts regarding the sender IDoc adapter.The sender IDoc adapter is present by default and we do not create manually. the qos of this is EO by default.
How can we change the QOS of the sender IDoc adapter? do we have to maitain any settings on the R/3 side, please explain??
thanking you

Dear Abhinav,
Check my comments in this forum thread:
[IDOC Serialization|Re: IDOC Serialization in PI]
Regards
Praveen K

Steps required for Sender IDOC adapter PI 7.0

Hi all,
My basis guy has installed SAP EHP1 for PI7.0 for handling the idoc packaging(sending idocs in packs)...
Please can any one let me know the further settings required in PI after it has been installed...
and even when i open the sender IDOC in comminication channel in ID i am able to see only 3 options
Transport prtocol, message protocol,Adapter engine...
But i am not able to see the other fields...
Can any one help me...
Thanks and Regards,
sridhar

Hi Michael,
Thanks for your reply..
I searched for the docs in many ways.. but couldnt find proper information regarding the IDOC packaging with sender IDOC adapter and steps required...
Could you please let me know if i can get the book in Singapore since our project, because almost 90% interfaces are related to IDOC...
And request you if you can share me the steps required in PI to confirgure IDOC packaging for EHP1...
Regards,
Sridhar Reddy
Edited by: sridhar reddy kondam on Jun 15, 2009 4:35 AM

How to configure Sender IDOC adapter

Hi could someone pls guide me on the steps that i need to take to configure IDOC sender adapter..
Are the steps for Sender and Receiver IDOC adapter same other than the fact that sender idoc adapter doesn't need a sender communication channel.
Regards,
Ashish

hi Goyal,
Just check out this link.
How to Configure IDOC
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098
Regards
Sachin

Port Settings for IDoc Adapter

Hi All,
Our scenario is like this ERP -> XI -> File. ERP sends IDoc to XI. I have a couple of questions.
1. In the control part of an IDoc, there's a sender partner number and sender port. What are they used for? As I understand, the partner and port represent the destination of the IDoc instead of the source. Why is there sender port and partner?
2. We need to maintain port using IDX1. Should I set the name of the port to be the same as the sender port of the IDoc?
3. I didn't configure the scenario and the IDoc sender adapter. If the ERP system sends IDoc to XI, can I find it in t-code IDX5?
Best Regards
Jerome

Hi Jerome,
1. Sender Partner and Port : The control record should have sender port and partner number. This will be used by the receiver system (i.e., XI system). Because, receiver system should know from which system this IDoc is coming using Sender Partner number. This partner number should be same as Logical system name in Sender Business system which is configured in SLD.
The sender port should be SAP<Sys-id of sender system>
and sender partner number should be <sys-id of sender>CLNT<client number of sender>
2. The port created in IDX1 will be used for importing IDoc's metadata in XI system from R/3. IDoc metadata is needed by IDoc adapter to convert incoming IDoc to IDoc-XML format.
It is mandatory to have same name for Port in IDX1 and sender port of the IDoc's control record.
3. I think the IDoc wont be listed in IDX5 if scenario and IDoc adapter are not configured. IDX5 displays inbound and outbound IDocs in the IDoc adapter.
Regards,
Uma

RE:SENDER IDOC ADAPTER

Hi ,
why don't we crate a communication channel for idoc on sender side,but when we go for receiver side we create communication channel .
please let me know how an idoc converted in to idoc-xml while transfer to integartion engine from sender side.( with out idoc adapter on sender side)

hi prateek,
The communication at sender also passes through the Idoc adapter.
with our configuring idoc adapter on sender side, how can an idoc passes through idoc adapter, is this because idoc adapter resides in abap stack.
can u briefly describe how can an idoc convert in to idoc-xml before comming to integration engine.
if idoc adapter is on abap stack then
in case of file to idoc
why we go for idoc adapter . (con't the process same as reciver side) .
please give brief explain to each of my questions.

Sender IDOC adapter for SAP 3.1H system & XI 7.0

We are on XI 7.0 and XI would receive a IDOC message from SAP 3.1H system.
I need to import IDOC's in imported objects in integration repository but I cannot see any IDOC under the IDOC node. I am able to see the RFC's. Do we need to do extra steps with SAP 3.1H version for IDOC adapter?
Thanks in advance for help!
Mrudula

Ahmad,
This thread is for sender RFC adapter. I am able to see the all the RFC's but not IDOC's from Integration repository for imported objects from SAP 3.1H version.
Thanks!
Mrudula

IS SENDER IDOC ADAPTER NECESSARY?

Hi,
I read somewhere that to send IDOC from one R/3 system,we need not to create any sender IDOC communication channel,bcoz while creating it we dont specify any technical details.
Is it true?
Why dont we need any sender IDOC channel?

Hi,
no you don't NEED it
but it's a good practise to create it
with a sender agreement
(if your SP allows that)
as in the future there might be some
additional features which you will be able to use
with that
BTW
use the directory wizard to find out
if it will be created by defaut or not
Regards,
michal

Sender IDoc adapter

Hi all,
I am trying some Idoc scenarios, and i find the IDoc sender radio button inactive in my system, do we configure the IDOc sender adapter in XI? if so can anybody send me a screen shot of the parameters we configure in the IDOC sender adapter??
thanks in advance..

To add further to my reply.
As long as you have created the following,
RFC destination to XI in the Backend system
Assigned the destination to a port in the backend system
Referenced that port in you partner profile config for the IDOC you are trying to send
Based on the above conditions, you do not need a sender channel for IDOC or a sender agreement for the business scenario.
Also in XI box you set the values in IDX1 to pull the metadata in from the backend system, by specifying the RFC destination from where you want to get the info from.
XI does however need the IDOC metadata to execute the interface, so you can pull this in via IDX2 or in the IR directly.
cheers
sameer

Sending IDoc adapter

Hello Specialists,
we have an issue in our XI production environment (only there). When we receive an IDoc from a Subsystem (Seeburger BIS) via tRFC than the XML-IDoc Structure isn't correct.
The facts:
IDoc Typ: INVOIC02
IDX1 + IDX2 ... The meta data check in IDX2 ok
The problem is here:
correct structure (like IDX2):
We have compared all configuration steps with our QA-Environment (there runs this scenario correctly).
Any ideas?
Thanks in advance
André

Hi Prateek,
yes, we have some custom mappings in Seeburger but exactly the same scenario (inculded the custom mappings) runs in our DEV and QA environment. The first point of view ist SXMB_MONI.
Thanks
André

Sender option grayed out in IDOC Adapter PI 7.1

Hi All,
I have heard of IDOC packaging in the PI 7.1 for which we need to create a sender channel in XI and sender agreement.
but the idoc adapter has the sender selection grayed out. Is there any other configuration which needs to be done.
Rgds
Aditya

Hi,
yes you have missed something - exactly what i am not able to guess.........just check whether the SAP BASIS 7.10 component was correctly deployed in your PI 7.1 system because without EHP1 also, at least you should be able to configure sender IDOC adapter............
maybe you need to do the readiness check of your PI 7.1 system again.........try restarting your PI server completely and then check if there is any error in the startup logs.........if there is no error, then again try to configure sender IDOC comm channel in ID.
Regards,
Rajeev Gupta

User has no authorization to send IDOCS of type

Hi Gurus,
I am sending an IDOC of type OILDEB02 from XI to R/3. I have done the configuration (we20, we21 etc). The message is processing successfully and not reaching the R/3.
When I checked in IDX5, after cclicking the 'transaction id', i see this message.
Caller: XIAFUSER
No authorization to send IDOCS of type OILDEB02.
Do we need to create the XI service users in the R/3 system?
I wanted to know what is missed in this configuration?
Thanks
Kalyan

Bhavesh,
I am using File to IDOC interface.
I have checked all the items you mentioned. Everything is working as expected.
1. The rfc destination and port in the IDOC adapter are the valid ones you have created for the R3 system in Sm59 and IDX1 respectively
***THESE ARE VALID
2. Go to IDX2 and try to manually import the Idoc metadata. See if this is successful.
MANUAL IMPORT IS SUCCESSFUL
3. In the RC destination in Sm59, try a test connection and remote log on.
TEST CONNECTION AND REMOTE LOG ON WERE SUCCESSFUL.
4. Finally check if the user id has the roles mentioned in my porevious reply and if yes, things should work.
I didn't check this on. But there was no error regarding my user id.

After I run the interface, XI is showing the processing successful and the IDOC is not received at R/3.
When I checked in IDX5 in XI, after clicking the transaction id, the message is saying that -
Caller XIAFUSER
Function module: IDOC_INBOUND_ASYNCHRONOUS
Target system: R/3 SYSTEM RFC destination I have created in XI
Status text: No authorization to send IDocs with message type OILDEB
Any thoughts??
Thanks
Kalyan

Idoc adapter- communiccation channel

Hi
When we do an Idoc to file scenario sender communication channel is not required. Because Idoc is the sender adapter. but while doing a File to Idoc case why do we neeed a receiver communication channel. Here also we use Idoc so why use a communication channel ?

Hi,
You do not need A Sender IDOC Adapter. IDoc's are sent directly to XI's Integration Engine and so no need of Sender IDOC adapter and therby Sender Agreement as well.
Yes, the port will be a TRFC port and you will use the RFC destination created in SM59 in this port.
Idoc Metadata gets loaded automatically when your scenario is run. You can also do it manually, by going to IDX2 and probiing the Port and the Basic Type of the idoc whose metadata you want to load.
but when we go for a fileto IDOC the file does not contain a standard structure
for that reason we need to create the receiver IDOC adapter .
pls chk this links
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
if found worth pls do the req
Thanx
Sampath

Assignment IDX1 port to sender idoc adapter ...

Similar Messages

Maybe you are looking for