IDoc scenario - synchronous service

Hey,
I have the following scenario:
SAP system ---(IDOC)-----> PI -------(synchronous service)---> ext. System
but the response of the synchronous service should be:
ext. System ------(synchronous service response)----> PI -----------(server proxy)----> SAP system
That means, the Idoc is coming asynchronous in, but IP then calls a synchronous service. The response of this service call should then be routed over PI to a server proxy on the SAP system.
How can I so that the best way?
Thank you very much!
Michael

Hi Markus,
My JMS receiver channel shows now the following modules:
1     AF_Modules/RequestResponseBean     Local Enterprise Bean     0
2     SAP XI JMS Adapter/ConvertMessageToBinary     Local Enterprise Bean     convert_XI2Bin
3     SAP XI JMS Adapter/SendBinarytoXIJMSService     Local Enterprise Bean     exit
4     AF_Modules/ResponseOnewayBean     Local Enterprise Bean     1
And the following Module configuration parameters:
0      passThrough          true
1      receiverChannel     -
1      receiverParty          -
1      receiverService      -
Are the parameters connected to the right module, or should they be set in the opposite way?
What have you set in receiverChannel/-party/-service?
Thanks in advance!
Edited by: Michael Schmidt on Nov 2, 2010 1:24 PM

Similar Messages

Problem with Sender service in File to IDOC scenario

Hello All,
Am doing a file to IDOC scenario.
I have configured the sending system as a party and added a business component, to the BC attached the service interface and also configured the sender Communication channel(CC) as file.
On the receiving end configured the R/3 system from SLD as the business system and configured the receiver CCl. Can see the R/3 logical system in the Adapter specific identifiers at business system.
Pushing the file get an error "Unable to convert the sender service to an ALE Logical System". But choosing "Take sender from Payload" in the receiver CC is resolving the problem, however the sender partner number remains the same as what I have mapped to the control record in message mapping (which is like hard coding).
My questions are:
1. Am I doing the correct config in terms of the scenario. (like using "Take sender from Payload")
2. I tried using identifiers at the party level to convert the sending system, but nothing seems to work. But sending system remains the same as the constant from mapping.
Suggestions would be very much helpful..
--Prashanth
PS: Have gone through many blogs and posts on the forums, but may be I did not see the correct thread. Apologies if I am asking this again.

Hi Prashanth,
refer the below discussion i think it will solve your problem.
File To Idoc scenario
Thanks

File Service to IDOC Scenario

HI ,
I am trying file service to IDOC scenario and iam getting following error "Unable to convert sender service FilesService_FILE2IDOC to an ALE logical system".
Here file has to be read and IDOC has to be posted in SAP system. Sender is not an SAP system / 3rd Party system ...itz an FILE sender service.
Settings i have done:
In Message Mapping in target IDOC structure i have disabled Control record
In integration directory IDOC Receiver Communication channel i have not selected "Apply Control Record values from Payload".
In receiver determination in header mapping i have put sender sevice "FilesService_FILE2IDOC ".
But still i receive the same error.
I do not want to send control record parameters in Message Mapping .
Pls throw some light on this ....
Regards
Sri

Hi Sridhar,
Regarding your error, below is the answer...
When you create the business system (in the SLD) you assign a "logical system name" or "ALE name". That is used as the ALE name for transporting IDOCs, and the sender system.
You have to also maintain this name in the R/3 System (tx. SALE, WE20), because IDOC will be noted as arriving from that system.
You also told that you dont want to pass the control records value....Do this, just deactivate the control records segments in your message mapping... let me not explain it further.... just check these blogs below for the same,
/people/sravya.talanki2/blog/2005/12/02/manipulating-idoc-control-records-from-payload
/people/michal.krawczyk2/blog/2005/09/01/xi-idoc-adapter--edidc40--demystified
And also 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
I hope this helps you solve your problem.
Regards,
Abhy

Using Service without party in Inbound Idoc scenario

Hi Guys,
Can we use a Service Without Party in an inboud Idoc scenario? I want to create a Business Service without party and use it as a sender service. For the Adapter Specific Identfiers for this service I want to put any arbitrary value for the logical system for Idoc adapter (as there is no business system defined in SLD for this, we cannot get the logical system name from there). Would this work while the Idoc adapter tries to resolve the Sender Service? Would this arbitrary value from the Adapter Specific Identifier be taken for SNDPRN in the Idoc control header?
Regards,
Suddha

Hi,
You can use Business system or Business Service (Service without Party).
If you use Business system then there will be direct linking with SLD while in case of Business Service you will have to manually add the Interfaces to the Business service.
But in case of IDOC sender since communication channel is not required so you can use Business service as well.
Check this link
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/903a0abc-e56e-2910-51a8-9dc616df56eb
PrasHanT

Web Service to IDoc scenario: No receiver could be determined error

Hi. I am working on a web service to IDoc scenario. I am receiving this error:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I've taken the XML message being sent to me and tested the mapping and I've completed the test configuration in the IB. Both work fine. Any ideas? I've been looking into this for a couple of days, so I've been through all the previous posts I could find.
Thank you.
Nicole

hi,
This is not related to receiverdetermination ,whether you creaeted or not.
It is somthing related to receiver systemwhich was configured in Receier determination.
check the target BS is correct or not or the inbound interface.
Did you configured the proper receiver technical system..
OR
Check the Receiver Determination is configured correctly. i.e R/3
Verify all the configurations like SM59, Partner Profile/Logical systems. etc. Also check in SM58 of R/3 system.Make sure that All the objects are activated in the Directory.Refresh the cache.Verify is the business system is pointing to correct R/3 system . Go to Business system/Service->Menu->Adapter specific identifiers in the directory
You can test your configuration with sample
payload.
In ID goto to TOOLS -
> Test Configuration for testing.
Hope in this way you can still find at which point the interface goes wrong.

Idoc to web services scenario

Hi
Can any one send me material for <b>idoc to web services scenario</b> to my mail id [email protected] or any good links to download material
Regards
Pavan

How to Develop a Webservice Using NWDS and SAP XI.30
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5f3ee9d7-0901-0010-1096-f5b548ac1555
How to Set Up a Web Service-Related Scenario with SAP XI
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/befdeb90-0201-0010-059b-f222711d10c0
How to Configure the IDoc Adapter
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098
How to Sample IDoc Scenarios Within XI 3.0
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660

Integration scenarios from scratch: idocs or enterprise service

Hello,
We are starting a SAP PI implementation for a new SAP ECC 6.0 system. The implementation is from scratch, so we don't have to consider any historical issues or decisions. One of the first business processes to be integrated with business partners is the Procure-to-Pay process. The old way of implementing this B2B scenario was with idocs (e.g. ORDERS05 and INVOIC03), but nowadays the enterprise service bundles also contain services for this scenario. Should I choose idocs or enterprise services as a technique to get the information send to SAP PI or send the information to SAP ECC? What are the advantages and disadvantages of both techniques? Does anyone have experience with the implementation of the enterprise services for Procure-to-Pay?
Thanks for your response!
Kind Regards,
Mark

Hello,
We are starting a SAP PI implementation for a new SAP ECC 6.0 system. The implementation is from scratch, so we don't have to consider any historical issues or decisions. One of the first business processes to be integrated with business partners is the Procure-to-Pay process. The old way of implementing this B2B scenario was with idocs (e.g. ORDERS05 and INVOIC03), but nowadays the enterprise service bundles also contain services for this scenario. Should I choose idocs or enterprise services as a technique to get the information send to SAP PI or send the information to SAP ECC? What are the advantages and disadvantages of both techniques? Does anyone have experience with the implementation of the enterprise services for Procure-to-Pay?
Thanks for your response!
Kind Regards,
Mark

Integration scenarios from scratch -- idocs or enterprise service bundles

Hello,
We are starting a SAP PI implementation for a new SAP ECC 6.0 system. The implementation is from scratch, so we don't have to consider any historical issues or decisions. One of the first business processes to be integrated with business partners is the Procure-to-Pay process. The old way of implementing this B2B scenario was with idocs (e.g. ORDERS05 and INVOIC03), but nowadays the enterprise service bundles also contain services for this scenario. Should I choose idocs or enterprise services as a technique to get the information send to SAP PI or send the information to SAP ECC? What are the advantages and disadvantages of both techniques? Does anyone have experience with the implementation of the enterprise services for Procure-to-Pay?
Thanks for your response!
Kind Regards,
Mark

Hi Mark,
here are my 2 cents to your very interesting disussion.
The IDOC was designed to customize EDI data distributions between SAP Systems via messagetypes and transaktioncodes (Vorgangscodes) in the partnerdetermination which itself is mapped (the "Vorgangscode") to functional modules to do "something". The complete customizing of IDOC distribution might sometimes seems to be complex (and we both know it is more than that but it is FULL CUSTOMIZABLE from a consulting point of view.
The Enterprise Service (my personal view multiplied with the last TechEds and RampUp Delta courses) have another focus. An Enterprise Service is (mostly) some entity which is consumable from the outside world such that they are implemented with Request-Response patterns. When you only want to distribute information why will one use something like Request Response Patterns? One could argue to get back any response, any confirmation or something else....but this is also possible with IDOCs and their acks.
Another argument against to use an ES for P2P outbound scenario is, if yet not seen any ES which is triggert while create a purchase order in its related transaction. Is the BADI for such Transaction triggering the ES while the save event has been processed? If you could find out this fact and if the BADI (or some new kind of user exit for transactions) is implemented and fully supported from SAP I would choose the ES in the P2P processs. Otherwise why using the ES instead of the IDOC when using a PI as Middleware which is converting the source message type (ES or IDOC) into its proparitary legacy system format. Please let me know when you found such userexit/BADI for ES.
Please don't missunderstand my point of view, I would really throw away these IDOCS and using a couple of ES instead but what is the fully supported STANDARD from a customizable and manageable point of view. When you are familiar with proxy technology you know how easy to implement, monitor and manageble theses technology is - BUT - you always have to code some (maybe not release independent) proxy method and you maybe have to invest some knowledge for error handling, rollbacks or additional commit works - all of these stuff will be handled (mostly ) by the SAP standard delivered functions.
Last but not least - if there is any standard out there to trigger an ES from a transaction without coding I would rather use the ES instead of the IDOC. If there is no such standard I would discuss the functionality with the customer (if to complex implement an inbound or outbound proxy=ES) or extend the IDOC or use a BAPI (and extend the BAPI if needed) - mostly the proxy will the be the easiest choice if the needed field count is not to much (<30).
So long, let me know about your findings and your decision.
Regards,
Dries

IDoc to JDBC and JDBC to IDoc Scenario

Dear All,
I am working on IDoc to JDBC and JDBC to IDoc Scenario.
I have to send Idoc from SAP to Non SAP system(.NET application) i almost configured in XI but still i don't know when my INTEGRATION will INVOKE how my data will proceed from IDOC to Oracle database(Through JDBC) and in case of revese how and when Data flow will start.
Does anyone have completed STEP by STEP scenario document for this?
How my Idoc will sent to XI?
How XI will pick up data from IDoc?
How XI will Convert data to JDBC and UPDATE in Oracle Database?
And i reverse case(JDBC to IDoc) when my INTEGRATION will INVOKE?
Where and When i can watch my process and data?
How can i test the whole integration?
I AM GETTING ERROR WHILE TESTING CONFIGURATION IN Integration Directory "Error while refreshing the XI runtime cache" and when i check this in SXI_CACHE it gives me error
"Unable to refresh cache "NO_BUSINESS_SYSTEM"
"Error during last refresh to cache"LCR_GET_OWN_BUSINESS_SYSTEM - NO_BUSINESS_SYSTEM"
Please solve all the above problems i will reward u points
thanks,
RP

Hi,
While we working on IDOC to JDBC interface..
We have to deploy JDBC Drivers?
Go through this links,
/people/varadharajan.krishnasamy/blog/2007/02/27/configuring-jdbc-connector-service-to-perform-database-lookups
http://searchsap.techtarget.com/tip/0,289483,sid21_gci1246926,00.html
To install JDBC driver follow the how to guide.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/xi-how-to-guides/how%20to%20install%20and%20configure%20external%20drivers%20for%20jdbc%20and%20jms%20adapters.pdf
Configuration of JDBC Adapter for SQL Server
JDBC Driver = com.microsoft.jdbc.sqlserver.SQLServerDriver
Connection = jdbc:microsoft:sqlserver://hostname:<port>;DatabaseName=<DBName>
UserID and Password.
If the connection is not working find the correct port number.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40b92770-db81-2a10-8e91-f747188d8033
JDBC- X I - R/3 Scenario
/people/bhavesh.kantilal/blog/2006/07/03/jdbc-receiver-adapter--synchronous-select-150-step-by-step
/people/sap.user72/blog/2005/06/01/file-to-jdbc-adapter-using-sap-xi-30
Please check the driver path as mentioned below.
JDBC Driver : sun.jdbc.odbc.JdbcOdbcDriver
Connection:jdbc:odbc:Driver={Microsoft Access Driver (*.mdb)};DBQ=//location of DB table.mdb;
No JDBC driver required.
Receiver JDBC scenario MS access - /people/sameer.shadab/blog/2005/10/24/connecting-to-ms-access-using-receiver-jdbc-adapter-without-dsn
follow this thread
Re: Problem when connecting to MS Access through JDBC Adapter.
SAP Note 850116 has details
/people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change
Configuring the Sender JDBC Adapter
http://help.sap.com/saphelp_nw04/helpdata/en/1d/756b3c0d592c7fe10000000a11405a/content.htm
Configuring the Receiver JDBC Adapter
http://help.sap.com/saphelp_nw2004s/helpdata/en/b0/676b3c255b1475e10000000a114084/content.htm
Idoc Reveiver adapter..
http://help.sap.com/saphelp_erp2004/helpdata/en/b9/c5b13bbeb0cb37e10000000a11402f/content.htm
Thanks,
Satya Kumar
/people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change
Edited by: SATYA KUMAR AKKARABOYANA on May 8, 2008 5:51 PM

Multiple Operations for File to IDoc scenario

Hi all,
I have a file to IDoc scenario where two IdocXML files (one for INSERT and one for CHANGE of Business Object) have to be picked up by file adapter and transfered to SAP System. In respect to the multiple operations PI 7.1 can handle I would like to create one Service Interface for the Business Object and two operations (INSERT and CHANGE).
Unfortunately I am not able to use the operation in the sender agreement, so I can't specify the comm-channel for the operations, only for the interface.
So, can I use multiple operations in a file scenario (respectively in a non Web Service scenario)??
Thanks a bunch,
Manfred

The scenario is pretty easy. I just want two different files to be read by one Comm Channel with one Sender Agreement.
They are both transferred to the same receiver. I just wanted to test one scenario using multiple operations.
In your blog you described that you should not use two operations with the same set of messages (synchronous/asynchronous). In my case both are asynchronous but I already tried it with one being sync and the other one async. Where did you actually get this information, it puzzles me a little since SAP does the same in its preconfigured Enterprise Services as far as I know.
In the Trace for pipeline step Interface determination in SXMB_MONI it says:
<Trace level="1" type="T">...There is no Interface Determination configured for receiver party and receiver service BS_RECEIVER</Trace>
<Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) BS_RECEIVER SI_..._Out</Trace>
<Trace level="2" type="T">...valid InbIf without Condition: SI_..._Out</Trace>
<Trace level="2" type="T">Number of receiving Interfaces:1</Trace>
So it finds the Outbound Interface in Receiver side which is wrong since I specified the Inbound Interface in the Interface determination. Did anyone of you already encounter such a behaviour? I already deleted and recreated all routing objects but without any success.
Thanks,
Manfred

IDocs or Enterprise Services in message exchange between systems

I am trying to get some qualitative and quantitative answers to the comparison of Enterprise Services or IDocs as a choice of interface technology when exchanging messages via PI with external systems.
The external systems are probably going to have their own message format, so this would concern the nature of the interfaces of the ERP system interfaces to the PI system.
I have seen one other posting in this forum related to this, but no definitive answer.
Does anybody have any system performance comparisons using the two technologies, such as message throughput / hour? Not easy to compare I know.
Does anybody have an opinion as to the suitability of Enterprise Services for such a task? Is the technology stable enough to be trusted yet?
When comparing status messages of IDocs, do the Enterprise Services have a similar way of easuly seeing the delivery status of the message using the Enterprise Service?
Would anybody or has anybody actually been brave enough to use Enterprise Services in this way yet?
Are Enterprise Services appropriate for mass messaging?
All answers very much appreciated!
Kind Regards,
Tony.

Hi Michal,
Thanks for the reply. I try to respond to your questions precisely:
if you want to compare IDocs to services then I assume
we're talking about async services right?
(and most services - just like bapis - are sync messages)
so you compare two different things
Yes, I know. What if the message scenario was asynchronous, and you chose not to handle the response message of the Enterprise Service? You could still do that, right? Then the problem becomes how do you trace the status of the Enterprise Service transaction.
IDocs have the advantage of a status message, and a good message monitoring system, but I am not sure if the visibility of errors seen with Enterprise Services if treated asynchronously would be as obvious. My knowledge of the runtime of the Enterprise Services is currently a bit limited.
The whole reason for me asking about the use of Enterprise Services is that there are so many now that could be used for message exchange, if they were suitable for the task.
Also, what about creating Asynchronous/Synchronous bridges in PI to handle the response message? Then the response is always traceable, correct? Even if the customer doesn't want the response message, the content could always be found in the PI message monitor.
Additionally, there is a transaction in ERP that wraps a BAPI into an IDoc (don't have a system in front of me at the moment and cannot recall the transaction, maybe OM69 or something similar). Now, that is taking a synchronous 'service' (the BAPI), and converting it into an asynchronous IDoc. So if this is such a bad idea, why do SAP provide the transaction? Therefore, by extension, wouldn't it be possible to do the same thing for Enterprise Services, at least from a philosophical point of view? I mean, why would SAP imply you could do this for one kind of synchronous service (the BAPIs) but not others (the Enterprise Services)?
if you're talking about migrations etc I don't believe services
will be used with LSMW but BAPIs are on the other hand
No, I was talking about high volume message scenarios, sorry for the ambiguity. I guess if the performance of Enterprise Services is comparible to that of well written BAPIs, the answer is 'yes', correct?
Kind Regards,
Tony.

Error in File to IDOC Scenario

Hi,
I have File to IDOC scenario.
I am getting error in sender file channel.
"Conversion initialization failed: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Mandatory parameter 'xml.keyfieldName': no value found "
Although I have used this parameter in content conversion 'xml.keyfieldName' (for each sub structure and defined a key field).
Despite of this error in sender channel I am receiving the message in XI.
But in XI also it throws error :
"Unable to convert the sender service PG_TOM_CEEMEA_RU_SFA to an ALE logical system"
Any help on this ?
Thanks,
Vikas

Hello Vikas,
I am getting error in sender file channel.
"Conversion initialization failed: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Mandatory parameter 'xml.keyfieldName': no value found "
Although I have used this parameter in content conversion 'xml.keyfieldName' (for each sub structure and defined a key field).
Check your flat file structure whether the key field you have chosen is appropriate and also recheck the FCC details whether you have assigned the value for the key field i.e. keyFieldValue.
"Unable to convert the sender service PG_TOM_CEEMEA_RU_SFA to an ALE logical system"
regarding the above error refer this
https://wiki.sdn.sap.com/wiki/display/XI/Unable%20to%20convert%20Sender%20system%20to%20ALE%20logical%20system
Regards,
Prasanna

JDBC to Idoc scenario - change of logical system name

Hi,
I have a JDBC to idoc scenario that worked. Now i had to change the logical system name from my sender system from ABC_123 into ABC123 in the SLD (Business System - Integration - Logical System name). I did so and also refreshed my Cache.
Afterwards I started the process, but it failed in the Receiver system. The idoc is correct expect of the partner name. My receiver system expect ABC123 - as I changed in the SLD - but PI send ABC_123.
If io look in SXI_CACHE - Services my Business System still got the "old" name (ABC_123).
Did i miss something resp. how can i load the current configuration from SLD?
Thanks in advance
Michael

Hi Michael,
Again Import the changed logical system in the Integration directory of you PI system.
And check the scenario (Sender Agreement, Receiver agreement ) what system they are reflecting.
If they are showing old system then you have to replace the business system in all the scenario.
Edited by: Rajhans Abhay on Jan 7, 2010 3:14 PM

File to IDOC scenario-no messages in SXMB_MONI

Hi all,
   I know this is asked so many times ,I checked some links but couldn;t find out the gap where it happened.
I am doing a File to IDOC scenario through XI mapping.
I am not getting any messages in SXMB_MONI.
When I check Communication Channel monitering in Runtime Workbench, it shows processing successfully, then it should generate messages in SXMB_MONI and intimate whether the scenario created is correct or not right!
Please help.
My scenario goes like this:
Sender : Business service(Some file location)
Used File adapter for sender communication channnel.
Receiver : Business system(SAP R/3)
Used IDOC Adapter for receiver communication channel.
One more thing is,do I need to create logical system for Business service also?If so, where do I maintain it?(In SAP R/3 or in XI system?)
Till now,I maintained my XI system as logical system in WE20 and I didn't create any logical system for business service in any system.Does it create main problem?

Hi , I am able to poll the files from file location now.and I am receiving IDOC into SAP R/3 with status 56.I already created partner for file path as a logical system and assigned inbound parameters with respective message type . Even the status shows :
An inbound partner profile could not be found with the following key:
/LSDEMO/LS//DEBMAS////
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
I already manitained following data and there is one record in EDP21.
SNDPRN = LSDEMO
SNDPRT = LS
SNDPFC = LS
MESTYP   = DEBMAS
MESCOD = space
MESFCT = space
TEST = space
EVCODE   = DEBM
SYNCHK = X
METHOD = space
USRTYP = space
USRLNG = space
INMOD = space
DCART = space
And please let me know whether I have to maintain outbound parameters also for my partner in XI system.I didn't see any difference even I maintained it.
And my IDOC takes another port rather than I mentioned in my SNDPRN(sender port) of my IDOC control record in message mapping.Let me know whether it's mandatory to maintain port name with SAP<XXX>convension,because IDOC in R/3 is picking the port with that naming convension.
Edited by: Jaya on Feb 26, 2010 10:17 AM
Edited by: Jaya on Feb 26, 2010 10:27 AM

Reg:file to idoc scenario

In a file-xi-idoc scenario i created a business service for legacy
system and a business system for R/3 receiver system
i didn't assign logical system for the sender business service
and assigned a logical system for the reciver business system
so while maintaining partner profile in the R/3 system
i have to give partner no:
partner type:
here the problem is my sender business service i didn't assign any logical system,and it is not of LS type
so then what do i need to give in the above two fields?
answers required briefly

Hello,
you know this pdf:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c09b775e-e56e-2910-1187-d8eba09c7a4a
Could be helpful.
Regards
Patrick

IDoc scenario - synchronous service

Similar Messages

Maybe you are looking for