Doubt Regarding IDoc Adapter

Dear Gurus,
In IDoc to XML conversion scenarios, we never use Sender Communication Channel because the IDoc adapter sits on the ABAP stack and the conversion is done by the IDoc adaper in the Integration Server.
Then why in case of the reverse scenario , i.e. XML to IDoc conversion we use Receiver Communication channel and the IDoc adapeter explicitly? Why can't that IDoc Adpater that sits on the ABAP stack convert the xml file into IDoc format?

Hi Shweta,
the reason for this is:
The adapter at the inbound channel is located before the Integration Server pipeline and calls this pipeline. The adapter at the outbound channel, however, is called by the pipeline, and can therefore be regarded as part of the pipeline.
The connected systems transfer or receive IDocs through their IDoc RFC interface.
if you check this link:
http://help.sap.com/saphelp_nw04/helpdata/en/ab/bdb13b00ae793be10000000a11402f/frameset.htm
and read the Integration section and try to understand the pipeline flow, as the names are not understandable(viz. receiver determintaion, mapping etc.) in the diagram.
you will get the clarity after reading this..
Sachin

Similar Messages

Doubt on Idoc adapter parameters

Hi ,
      I need one more clarification on Idoc adapter parameters :
1.while configuring for IDOC adapter in communication channel , we have an option
called "APPLY CONTROL RECORD VALUES FROM PAYLOAD" doubt arises here
what actually this mean,and if this check box is ticked what values will be taken from payload and where will be they applied?
                       Plz clarify answers will be definetely rewarded.
                                                                                Regards,
                                                                                Vinod.

Hi vinod reddy ,
If u want to add values to the control record , u have to select the APPLY CONTROL RECORD VALUES FROM PAYLOAD checkbox in the communication channel. When a new communication channel of type IDoc is created, the flag is set by default. If the flag is not set, the
settings comply with XI 2.0
This following websites clearly clarifies u'r doubt with detailed description with fields :
Fields of the IDoc Control Record
http://help.sap.com/saphelp_nw04/helpdata/en/13/95244269625633e10000000a155106/content.htm
Configuring the Receiver IDoc Adapter
http://help.sap.com/saphelp_nw04/helpdata/en/96/791c42375d5033e10000000a155106/content.htm
How to.......Sample IDoc XI Scenarios
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c09b775e-e56e-2910-1187-d8eba09c7a4a
cheers!
gyanaraj
****Pls reward points if u find this helpful

Doubt about IDOC Adapter

Hi all,
i'm using idoc adapter for generating IDOCS from R/3, and my scenario is: IDOC->XI->File. this is working fine, in R/3 i've got partner profiles for diferent vendors(suppliers) and they are configured for create idoc message in R/3 and all this message are caught by XI from my scenario and generate the corresponding text file.
but now suppose that I need another scenario because i need to send purchase orders by mail instead file to some of my vendors in R/3. the scenario would be IDOC->XI->Mail.
for both cases i would use ORDERS05.
i can't undertand how XI knows wich scenario have to use, if there's nothing from R/3 that tells XI which scenario should be used.
thanks, Fabian.

Thanks for responses, I know what should i use to do what i wanted. but i've tried to make a condition in the receiver determination and it's giving me an error saying that 'No receiver could be determined'.
i've searched in other threads and i have seen that utilizes xpath to make conditions
what i have done is add a condition in Configured Receivers as '/p1:ZORDERS2/IDOC/EDI_DC40/RCVPRN = 0000010598'
because depending on the partner, i want to use either one or other adapter (file or mail)
do i have misedd something?

Doubt on Idoc Adapter

Hi
I was going thru the help.sap for IDoc adapter.
Implementation Considerations
Only use the IDoc adapter to integrate SAP systems with the Integration Server if a scenario of this kind suits your requirements.
in
http://help.sap.com/saphelp_nw04/helpdata/en/ab/bdb13b00ae793be10000000a11402f/frameset.htm
what does it really mean. I understand where the idoc adapter is placed and y no sender agreement is req. But this phrase in help.sap is confusing.
Can i take all ur help in understanding this?
thkx
Prabhu

Hi,
IDOC scenarios are used when you have to transfer business data TO or From SAP R/3 . Itz is still the most preferable solution. But if you want ackowledgements to be sent back for ex: a business data back can it be acheived through idoc >? No. That where rfc comes into picture. Itz only effective during assynchronous communication.
I suppose it was in this conext of application of a idoc adapter that was illistrated.
correct me if itz wrong
<b>Cheers,
*RAJ*
*REWARD POINTS IF FOUND USEFULL*</b>

Doubt regarding Sender adapter file content conversion to RFC

Hi Experts,
Below is the my Source and Target XML structure ( i have creaated source structure same as target RFC structure), This scenario is working fine when i give XML file as input. File -> XI -> RFC , xml file is able to update the information in R3.
How should i configure sender file adapter for file content conversion for above structure(in this case input is fixed lenth text), and i could able to change source structure according to our req, without changing target RFC strucuture.
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_HSA_IDNumber xmlns:ns0="urn:passhe.com/UpdateIdNumberISA32">
   <COMMIT_I>X</COMMIT_I>
   <IDENTIFICATION>
      <STUDENT>6500001191</STUDENT>
      <ID_TYPE>FS0030</ID_TYPE>
      <ID_NUMBER>testxml</ID_NUMBER>
      <VALID_FROM>20070421</VALID_FROM>
      <VALID_TO>20091231</VALID_TO>
   </IDENTIFICATION>
</ns0:MT_HSA_IDNumber>
I have configured sender file adapter with FCC like :
Document name as: MT_HSA_IDNumber
Document name space as: urn:passhe.com/UpdateIdNumberISA32
Record structure as: COMMIT_I,1,IDENTIFICATION,1
COMMIT_I.fieldNames : COMMIT_I
COMMIT_I.fieldFixedlengths: 1
IDENTIFICATION.fieldNames: STUDENT,ID_TYPE,ID_NUMBER,VALID_FROM,VALID_TO
IDENTIFICATION.fieldFixedlengths: 12,6,60,8,8
i am getting error like this: even when i change source structure like below metioned:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_HSA_IDNumber xmlns:ns0="urn:passhe.com/UpdateIdNumberISA32">
   <COMMIT>
      <COMMIT_I>X</COMMIT_I>
   </COMMIT>
   <IDENTIFICATION>
      <STUDENT>6500001191</STUDENT>
      <ID_TYPE>FS0030</ID_TYPE>
      <ID_NUMBER>idnumber1</ID_NUMBER>
      <VALID_FROM>20070421</VALID_FROM>
      <VALID_TO>20091231</VALID_TO>
   </IDENTIFICATION>
</ns0:MT_HSA_IDNumber>
Conversion initialization failed: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Parameter 'COMMIT_I.fieldFixedLengths' or 'COMMIT_I.fieldSeparator' is missing Consistency check: no. of arguments in 'COMMIT_I.fieldFixedLength' does not match 'COMMIT_I.fieldNames' (0 <> 1)
Please help me out
thanks
dhanush

Hi Dhanush,
Try giving the Sender FCC this way for the source structure you have mentioned above.
Record structure as: COMMIT,1,IDENTIFICATION,1
COMMIT.fieldNames : COMMIT_I
COMMIT.fieldFixedlengths: 1
Hope this helps.
Thanks and Regards,
Induja

Regarding idoc adapter

hi experts,
Is Synchronous IDOC possible,how.we have to configure?
Regards,
tahir

>
TahirBabu Atther wrote:
> hi experts,
>
> Is Synchronous IDOC possible,how.we have to configure?
>
> Regards,
> tahir
There is nothing called a sync Idoc. IDocs can be configured with acknowledgments but it is not technically a Sync scenario
Note that if what you want is a Orders Idoc being posted and a Orders Response IDoc being expected back, this is actually a Async scenario but if the source is a sync you can make use of a Sync - Async Bridge
http://help.sap.com/saphelp_nw04/helpdata/en/83/d2a84028c9e469e10000000a1550b0/content.htm

Doubt Regarding IDOC generation

IDocs are used for asynchronous transactions: each IDoc generated exists as a
self-contained text file that can then be transmitted to the requesting workstation without connecting to the central database.
where can i see the generated IDOC's in R/3.
whether IDOC will be generated with each and every transaction in R/3.

Hi Govada
prabhu can we find IDOC's date wise
Answer : In WE03 select the date which you want.
Is it compulsary for each transaction in SAP that and IDOC generates... like Purchase Order Creating, Stock maintainance etc.,
Answer: NO not all trancastion create IDOCs
can we check like for purchase order today how many IDOC s are generated
Answer: Yes goto WE02 and give the IDOC name select the date of today you see all
Do we have to configure some thing to generate IDOC or for each bussiness action a IDOC will will be genarated
Answer : We need to configure.
whether every IDOC stores in R/3 if where the IDOCs will be stored in R/3, how can we see the what are all the required feilds for particular segment of IDOC
Answer : IDOC data are stored in database . goto WE30 and see which field are mandotry.
Please Reward points
Regrads
Sreeram.G.Reddy

Doubt Regarding validation of IDOCS

Hi Gurus,
I have some doubts regarding IDOCS.
1. If we are sending a IDOC from XI to R/3, where does we do validations from R/3 side and how do we do that. Suppose if we are sending a Purchase order IDOC form XI to R/3, how to do validations for that particular IDOC for PO number and some other fields from R/3 side.
2. Do we need to do validations in a aABAP Program.
please clarify me these Questions. Thanks in advance..
santosh.

Hi Santhosh,
If you want to do any validations in ur IDOC,then from XI just push the IDOC,dont post it.
(ie)Send the IDOC from XI in status 64 :IDoc ready to be transferred to application.
Once R/3 Received this status then thru your ABAP progream just get this IDOC no: and do the validations then Post the IDOC manually.
Thanks.
Note:Reward Points if you find useful.

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

Doubt regarding ALE SETTINGS in IDOC scenario.

Hi Friends,
        I have some doubts regarding ALE settings for IDOC scenarios, can anyone please clarify my doubts.
For exmaple take IDOC to FILE scenario
The knowledge i got from SDN is --
One need to do at the R3 side is --- RFC DESTINATION (SM59) for the XI system.
                                                   --- TRFC PORT for sending IDOC to the XI system
                                                   --- CREATING LOGICAL SYSTEM
                                                   --- CREATING PARTNER PROFILE
               at the XI side is --- RFC Destination ( For SAP sender system)
                                       --- CREATING PORT for receiving IDOC from the SAP sending system(IDX1).
1. Do we create two logical systems for both Sender ( R3 system ) and Receiver( XI system ) in R3 system itself or in XI system or in both systems we create these logical systems? Is this a mandatory step in doing ALE configurations?
In IDOC to IDOC scenario-------
2. Do we craete two RFC destinations in XI system? One RFC DESTINATION for the Sender R3 system and another RFC DESTINATION for the Receiver R3 System? and do we create RFC DESTINATION for the XI system in receiver R3 system? If not.....y we don't create like this........Please give me some clarity on this.............
3. If we use IDOC adapter ,since IDOC adapter resides on the ABAP STACK ,we don't need sender communication channel ,for the similar reason----
y we r creating receiver communication channel in the case of FILE to IDOC scenario?
4. Can any one please provide me the ALE settings for IDOC to FILE scenario,
                                                                                FILE to IDOC scenario,
IDOC to IDOC scenario individually.
Thanks in advance.
Regards,
Ramana.

hi,
1. Yes, we create two logical systems for both Sender ( R3 system ) and Receiver( XI system ) in R3 system itself and
it is a mandatory step in doing ALE configurations
2. We create 1 RFC destination each in R3 and XI.
    R3 RFC destination points to Xi and
    XI RFC destination points to R3
3 We need to create Communication Channel for Idoc receiver as the receiver channel is always required but sender may not be necessary
4. ALE settings for all IDOC scenarios are same as follows....
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.
BD87 to check the status of IDOC.
In case if not authorized then go to the target system and check in SU53, see for the missing object
and assign it to the user.
SAP r3
sm59(status check)(no message)
WE02(status check)
WE05(status check)
BD87(status check)
Xi
IDx5(Idoc check)
SU53(authorization check)
Reward points if helpful
Prashant

Regarding IDOC in XI

Dear All,
For scenario:
System A (RFC adapter) --> XI --> System B (IDOC adapter).
How should i configure for the partner profile?
1. In System A --> Logical System to System B, and put my message type as outbound.
2. In System B --> Logical System to System A, and put my message type as inbound.
3. or i need to configure in XI partner profile? Logical system A (outbound) and Logical system B (inbound).
Please clear my doubts.
Thanks,
Victor.

Hey,
   For RFC you do not need to make any entries in partner profile.
For IDOC(i.e) in system B create a partner profile as inbound.
Please refer to these steps if any issues.
teps 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.
BD87 to check the status of IDOC.
In case if not authorized then go to the target system and check in SU53, see for the missing object
and assign it to the user.
SAP r3
sm59(status check)(no message)
WE02(status check)
WE05(status check)
BD87(status check)
WE42 process code
WE47 status info.
regards,
     Milan

REG: Error in IDoc adapter outbound processing

Hi All,
      I had a couple of doubts regarding these IDoc's.
1)        I am dealing with the web services to IDoc Scenario. When i am activated my wed services it               is giving an error like
"IDOC_ADAPTER.ATTRIBUTE_BE_NOT_SUPP" and "Only asynchronous processing supported for IDoc adapter outbound processing"
Can any one help me to Solve my Problem
2) How to find out whether the IDoc is of synchronous or Asynchronous mode
    and how to handle the synchronous type of IDoc's
Thanks in advance.
with Regards,
Kalyan Dannapaneni.

Hi Kalyan,
IDOCs are only Aynchronous (EO or EOIO).
If you want to call Synchronious, you will have to find remote enabled function modules (RFCs, BAPIs).
Or you have to use the ccBPM Synch-Async pattern to have an synchronos call passed to an IDoc, waiting for the Acknowledgement. In your situation I would check if a similar BAPI/RFC exists on your Backend SAP system.
Best regards,
Silvia

Receiver AAE IDoc adapter

Hi All,
I have a doubt regarding receiver AAE Idoc adapter. There are three options available in java IDoc adapter namely Default, Manual and From NWA. In Default option, we just need to configure a RFC Destination in NWA but in From NWA option, we need to configure RFC Destination as well as Resource Adapter(JCA Connection Factory). So, I just want to know what is the benefits of using From NWA option over Deafult and what is purpose of configuring Resource Adapter in NWA?

Hi,
see the below link.
http://help.sap.com/saphelp_nw73/helpdata/en/bc/0341dd385945d49eb809c084cf3dea/content.htm
as per this link i should check the checkbox.
Configuring Acknowledgements for a Sender IDoc Adapter (AAE) Locate this document in the navigation structure
Procedure
    Choose the sender communication channel on which you want to enable acknowledgement settings.
    Choose the Parameters tab and then, choose the Ack Settings tab.
    On the Acknowledgement Parameters area, enter the following settings:
        System Ack Ok Requested
        Choose this option to receive XI system acks.
        System Ack Error Requested
        Choose this option to receive XI system error acks.
        Application Ack Ok Requested
        Choose this option to receive XI application acks.
        Application Ack Error Requested
        Choose this option to receive XI application error acks.
        ALEAUD Special Handling Needed
        Choose this option to enable the sender Java IDoc adapter to apply special handling to the incoming ALEAUD message. The adapter replaces the IDoc number of the ALEAUD message with the original IDoc number.
        Initially, the receiver Java IDoc adapter generates a unique IDoc number, which replaces the original IDoc number of the outbound message. This IDoc unique number is referred by the ALEAUD message. However, the ALEAUD message is not converted to an XI Ack message in this case.

ACK send back but which Idoc Adapter

Hello,
I have the following scenario(party):
R3 -> XI -> Http
I am send orders from the R3 via XI to a customer. I'll get an status from the Http-Adapter that I want to send back to the R3. The definition for sending back are all done and fine. I've 2 Idoc-Adapter (Receiver). Adapter A is an old on used in an other scenario and the new on (adapter-B) with the special setting. When I am receiving the ACK from the HTTP-adapter how can I define wich idoc-Adapter has to be used. My problem ist that the adapter A is used which don't have the necessary settings and can't be changed. How/where can I define to use the adapter b for sendign back tke ACK to the R3.
Regards Jami

Hi Jami,
Receiver adapters that run on the Adapter Engine support system acknowledgments if they are requested by the sender. Acknowledgements are triggered when a message is successfully processed by the adapter or if an error occurs while it is being processed. Receiver adapters do not support application acknowledgments. The RNIF and CIDX adapters are exceptions to this rule, since they also support scenario-dependent application acknowledgments. Sender adapters of the Adapter Engine do not request any acknowledgments.
There is a guide to handle idoc acknowledgements, in sap xi. please refer,"how to handel acknowledgements for idoc" at,
https://websmp202.sap-ag.de/nw-howtoguides
Have look at "How To Handle Acknowledgments for IDoc" .
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe
I hope this clears all your doubts.
Regards,
abhy
PS: AWARD POINTS FOR HELPFUL ANSWERS.

XI FILE(FTP) - XI- CRM(Idoc adapter) scenario - restart message

Hello All,
I have scenario as below.
FTP->XI->CRM
The sender adatper is File Adapter, FTP.
Recv. adapter : IDOC adapter.
In CRM, there were middleware settings for idoc processing.
For an interface, in XI, i had a problem in getting a file of 10 Mb in size, so the file is split and i have made the XI sender adapter 'Z_PRICE_NEW20061004*.txt', so it picks all files within 5 mins and i have almost 104 XML messages.
Now the problem is a quite no. of message are ended up with error status in outbouond process in XI.
How can i reporcess the message? As the file is deleted from FTP? i ahve to do anything with the failed message.
A quick help is highly appreciated.
Thanks in advance.
Best Regards,
Jilan Bhasha

Hi ,
This weblog will help you....
/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
sekhar

Doubt Regarding IDoc Adapter

Similar Messages

Maybe you are looking for