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,
<i>The communication at sender also passes through the Idoc adapter.</i>
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 <b>file to idoc</b>
why we go for idoc adapter . (con't the process same as reciver side) .
please give brief explain to each of my questions.

Similar Messages

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

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...

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

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

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.

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

Idoc to file scenaro ( sending IDOC as it is to NON-SAP)

Hi Experts,
I am doing idoc to file scenario.
I am having SAP R/3 system with 3 clients(100, 200 & 300), IDOC is comming from SAP R/3( any one of the client)
In this is scenario, I am sending IDOC-XML as it is to the NON-SAP system.
I heard that, i can do in 3 ways. those are
1. Without any repository objects: you can go ahead with No interface mechanism on the target side.
2. Without message type: create a message interface whose message type would be idoc itself
3. With message type: export the IDOC as xsd file and re import the xsd file as an external definition.
If i go without IR objects,Please tell me whether i need to create Interface objects(i.e. DT,MT & MI) & Mapping objects (MM & IM) or not for the reciever.
MY ASSUPTION:
step1: I will import the IDOC into IR.
step2: Directly i will go to the ID without desiging any object in IR ( is it ok).
Is my assuption or correct or not?, please tell me.
So please tell me the entire scenario how to achieve this.
Please help in this issue.

Hi Laxmi
1. Without any repository objects: you can go ahead with No interface mechanism on the target side.
-- Not Possible
2. Without message type: create a message interface whose message type would be idoc itself
-- No need for the Message Interface for IDOC. You will directly import the IDOC and do the Mapping
3. With message type: export the IDOC as xsd file and re import the xsd file as an external definition.
-- This is Possible. you are export the IDOC as XSD File and reimport the same. so there is no difference. If you are going to change the IDOC Structure then this is possible.
Here I am sending some links which are useful for IDOC to File Scenario. Please go thru the links given below..
While doing an IDOC -> XI -> File scenario, The Points to noted are:
1. You dont need a DT, MT or a message interface for the IDOC as it itself acts as the Message Interface.
2. You import the IDOC and use the same in your mapping.
3. In this configuration note that you dont have a sender agreement as you dont have a sender IDOC adapter.
If it is that you wanted to send an IDOC from XI (File to IDOC) , then in this case:
points 1 and 2 will remain, but the 3 will not. You will need a sender agreement for the file and a receiver agreement for the IDOC.
IDOC -> File scenario ref:
IDoc-XI-File scenario
File -> IDOC ref:
File to IDOC
To be able to trigger your IDOC from the SAP ISU system, you will have to set the partner profile in we20. Select your Business System (mostly under Logical system) and then create Outbound entries for whichever IDOC you want to trigger.
You define your basic type also in your partner profile settings, Please go thru the following links to get a better idea about partner profile:
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b833243d711d1893e0000e8323c4f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b7cd343d711d1893e0000e8323c4f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/32/692037b1f10709e10000009b38f839/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/5e/b8f8bf356dc84096e4fedc2cd71426/frameset.htm
Also, I would suggest that you go through this blog by michal if any issue arises,
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
I hope this answers your query.
Award the POINTS if it is useful **
Cheers
Vasu

HELP Sending IDOC

Hi,
I want to send an IDOC but get the following error message:
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_WRONG_INTF</SAP:Code>
<SAP:P1>MYSEND</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>IDoc Interface MYINTERFACE konnte nicht interpretiert werden</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Another thread says that the problem is that the Inbound interface doesn't match the namespace urn:sap-com:document:sap:idoc:messages
and that it would be necessary to name the interfaces the same as the IDOC type (here: COND_A.COND_A02). From which software component can I import the namespace???
Any help will be appreciated, kind regards,
Heiko
PS: Is there a blog about this topic?

IDOC -> XI -> File ....
Points to note ...
1. you dont need a DT, MT or a message interface for the IDOC as it itself acts as the Messg. Interface.
2. You import the IDOC and use the same in your mapping.
3. in the configuration note that you dont have a sender agreement as you dont have a sender IDOC adapter.
~~ ShabZ ~~
Opps just noted that you need to sent an IDOC from XI (File to IDOC)
Anyway in this case,
points 1 and 2 will remain, but the 3 will not. you will need a sender agreement for the file and a receiver agreement for the IDOC.
IDOC -> File scenario ref : /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
File -> IDOC -> /people/anish.abraham2/blog/2005/12/22/file-to-multiple-idocs-xslt-mapping (It concentrates on XSLT mapping but also gives an idea about the configuration part.Do go thru that, it might help you.)
Message was edited by: Shabarish Vijayakumar

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

RE:SENDER IDOC ADAPTER

Similar Messages

Maybe you are looking for