Sftp procedure for outbound interface

Hi experts,
i have data in internal table.but here my problem is how to send internal table data to destination using SFTP with RSA key.
pls help me.
regards,
prasad.

Similar Messages

Inbound interface found more than once for outbound interface

Hello everybody,
i have a simple problem.
I build a interface with XI3.0
File to idoc
for each file i need crate 2 idoc.
It's not a problem when Idoc type is different, but in my case i need crate 2 idoc of same type but with a different mapping.
so when i upload the file i have this error:
Inbound interface found more than once for outbound interface
how can i solve this problem? can i force this step?
i thought to create a different idoc type or create the 2 idoc in same mapping , but there is not my favourite solution because in case of error , both idoc will be not created.
any suggestion?
thanks in advance
alex

Hi,
Instead of exporting and changing the occurrence as suggested by Ravi,
use the same Idoc twice in mapping as well as Interface mapping.
Coming to ID part, do every thing as usual.
The only thing to note is instead of using normal Interface determination, use extended Interface Determination.
This will solve your problem. The error will not come again. I'm sure.
Try out and update the thread.
Regards,
Jeevan.

Driver program for outbound interfaces

hi
i am having 5 outbound interfaces for which i need to make a driver program
in my driver pgm i need to make a selection screen which consists of 2 radio buttons
1 . presentation server
2. application server
when we select presentation server all the 5 inerfaces prestation server down load path must execute at a time .
in the same way if we select application server all 5 interfaces application servers must execute
can any one help with sample code
urgent
regards
sachin

Hi sachin,
can you explain a little more about ur req, like what do you mean by "down load path must execute at a time"
Regards
Raj

Java WS Client for Outbound interface

Need to create java web service client for an Outbound Interface in PI. This client will be used in an EJB developed for an inbound interface. Created Web Service client based on WSDL in the same EJB. However, do not know how to configure logical ports in PI 7.1 (not ehp1); when I deployed EJB, I'm not seeing it in Web Service administration screens of nwa.
Would like to configure logical port so that I can change the WS endpoint (url) to a specific instance of PI.
Any help is greatly appreciated.
Thanks

Need to create java web service client for an Outbound Interface in PI. This client will be used in an EJB developed for an inbound interface. Created Web Service client based on WSDL in the same EJB. However, do not know how to configure logical ports in PI 7.1 (not ehp1); when I deployed EJB, I'm not seeing it in Web Service administration screens of nwa.
Would like to configure logical port so that I can change the WS endpoint (url) to a specific instance of PI.
Any help is greatly appreciated.
Thanks

Getting the Data for Outbound Interface

Hello,
I am doing a outbound interface in which i need to take the Economic Order Quantity , Minimum order quantity , Present cost of the item and Prevoius Cost of the Item(Average costing may be used). The Process of Defining the required fields in Oracle is not yet Started as the Implementation is new. If any body have the approximate idea, where can we get the fields(Oracle Tables) it will be helpful. As this is just a Prototype u are welcome to provide the rough data which may change in future once the process is clearly defined .
Expecting the Reply.

Hello Madhav Dhurjaty,
Thanks for the Reply..
Economic order is not available in MTL_SYSTEM_ITEMS_B or TL..
we need to derive by some formula..EOQ = SQRT {[2*(annual demand)*(order cost)]/(annual carrying cost)}
Annual demand is calculated from the forecast we provide when we perform reorder point planning. Order Cost and Carrying Cost can be obtained when defining items (General Planning).
But my concern is how to get the Annual demand...
Awaiting for ur reply..

Using inbound service to produce data for outbound interface

Hi,
with SAP Enterprise services, we have lots of functionnality provided by SAP which we can use to easily get information
without having too much custom development done in the backend.
In our cas for example, we want to use an erecruiting enterprise service to extract data and send it to an external provider in an xml file.
here are the constraints
1) Reduce development as much as possible
2) Use PI to interface with external systems.
3) External system canot initiate the process.
It would be nice to reuse SAP content (Enterprise services) in order to extract the data and replicate it to the external system.
One way to do this would be to have a program which calls the method of the proxy that implements the enterprise service.
Then the program can just call PI to create a file with the contents returned by the method.
This is not an elegant solution ... , I would have liked PI to initiate the call at a specific time and with the response of the call send the xml file to the provider... this seems to be the reverse of what PI does...
I'm sure there are other solutions... any ideas ?
This is more of an extract and transfer scenario with PI...
Thanks.

Hi Thierry,
we want to use an erecruiting enterprise service to extract data and send it to an external
provider in an xml file
Please consider that the Auto generated proxies in Enterprise services are mostly Inbound( to SAP)
and have request and response structure.
When you are bringing PI into picture then you will need to create outbound structures, which you need
to copy.You will face issues with work around as suggested above , the proxies are not editable
and to make it editable you will end up creating a copy which will add more work then reuse.
Also think if the customer wants to enhance few field in the Req/Resp strucutures
(we need to consider this for sure)enhancing the structure is possible using dependencies
but it required costom changes.If you are expecting enhancements then better don't use enterprise services.
As SAP standard is designed to accept request and send response , its always correct to
request third party (consumer) to ask/trigger for data,unlike trying to put PI as triggering agent.
Conclusion:
Regards,
$rinivas
Edited by: Srinivas on Aug 12, 2010 7:27 AM
Edited by: Srinivas on Aug 12, 2010 7:37 AM

QRFC with ALE for outbound interfaces

I'm working on a client that is using ERP 4.7 (R/3). We would like to use the ALE qRFC addition to utilize the serialization concept. In the partner profile, I see a check box that says "queue processing". To our understanding, it enables qRFC with ALE. But how does the function module (FM) MASTER_IDOC_DISTRIBUTE determine which queue naming function module to call from transaction WE85? WE85 is a transaction where you define a function module to set your queue name based on the control record or IDOC. Do you pass the Rule Name from WE85 into the MASTER_IDOC_DISTRIBUTE and thus ALE calls the associated queue naming FM ? If so, what field do you set in the control record?

http://help.sap.com/saphelp_nw70ehp1/helpdata/en/48/05daa0b5133ca0e10000000a42189c/frameset.htm
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/c7/4efe402762ef6fe10000000a1550b0/frameset.htm
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/c2/4356429c69b430e10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/e7/555e3c0f51a830e10000000a114084/frameset.htm
Please go through this link.
This would help you..

Outbound interface using dataset

Hi,
     Please send me example program for outbound interface to maintain file in application server.
Thanks
Ali

Hi,
the code should look like below.
declare:
filepath_name TYPE rlgrap-filename,
internal table itab.
**Populate data to itab.
OPEN DATASET filepath_name FOR OUTPUT IN TEXT MODE ENCODING DEFAULT.
      IF sy-subrc = 0.
        LOOP AT itab.
          TRANSFER itab TO filepath_name .
        ENDLOOP.
      ELSE.
        MESSAGE i001(00) WITH 'Error writing to file in remote computer'.
      ENDIF.
      CLOSE DATASET filepath_name .

Segment creation for outbound Idocs to non-SAP system

Hi,
I need to create a custom idoc for outbound interface to a non-SAP system. Here I need to create segments. So, should I create the fields in the segment with the attributes of fields in non-SAP system or fields attributes should be of SAP system.
For example:
There is a field invoice number which is of 10 Chars in SAP but in legacy it is divided into 2 fields: invoice prefix of 2 chars and invoice no. of 8 chars. Should my segment contain one invoice field of 10 chars or should it be two fields with 2 and 8 chars?
In general, always should the segment fields contain field attributes based on receiving system?
Thanks in advance.
Sriram.

Hi
Should my segment contain one invoice field of 10 chars or should it be two fields with 2 and 8 chars?
I think it shoild be better to have 2 fields, but probably the result will be the same if you send the idoc by a text file, because both informations should be contiguos, I mean if you have file with a record like this:
1234567890
This record can be obtained downloading a segment with 2 fields:
FIELD1 = '12'
FIELD2 = '34567890'.
or single field:
FIELD = '1234567890'.
So it'll be the same for tje target system
In general, always should the segment fields contain field attributes based on receiving system?
It depends on who has to convert the idoc to the right format for the target system
I mean you can create a "SAP" Idoc, so the receiving system will have to convert it to the right format
or
you can send the idoc in the right format, so the receiving system doesn't need to convert it
Max

ABAP-HR OUTBOUND INTERFACE

HELLO EXPERTS,
Plz provide me with any sample code for outbound interfaces in abap-hr as i'm new to this concept.
Thanks,
Naveen Sharma

Dear Naveen,
would you mind checking this site? Perhaps you find some useful information.
<a href="http://erpgenie.com/abaptips/content/view/302/62/">ABAP Inbound/Outbound interfaces iDoc - User Exits</a>
Kind regards,
Zsolt

Outbound interface configuration in ID

Hi Friends,
What configuration I need to do in ID for outbound interface???

I had definied outbound interface but when I am testing the configuration by giving sender service,interface namespace and receiver service, and payload,
its giving error in Interface determination and mapping .
trace file for that is as follows... kindly suggest when the error can be..
Interface Mapping
com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8) at com.sap.aii.mappingtool.tf3.Transformer.checkParserException(Transformer.java:187) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:151) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:118) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:92) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0_0.processFunction(MappingServiceObjectImpl0_0.java:131) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy209.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:284) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:254) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172) Root Cause: com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:157) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) Root Cause: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8)(:main:, row=1, col=8) -> com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8) at com.sap.engine.lib.xml.parser.XMLParser.scanPI(XMLParser.java:2128) at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2776) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2832) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:231) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) -
at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:144) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) Caused by: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8) at com.sap.engine.lib.xml.parser.XMLParser.scanPI(XMLParser.java:2128) at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2776) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2832) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:231) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) ... 4 more com.sap.aii.ibrun.server.mapping.MappingRuntimeException: Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_MSG_ORD_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:73) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:92) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0_0.processFunction(MappingServiceObjectImpl0_0.java:131) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy209.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:284) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:254) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172) Root Cause: com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8) at com.sap.aii.mappingtool.tf3.Transformer.checkParserException(Transformer.java:187) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:151) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:118) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:92) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0_0.processFunction(MappingServiceObjectImpl0_0.java:131) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy209.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:284) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:254) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172) Root Cause: com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:157) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) Root Cause: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8)(:main:, row=1, col=8) -> com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8) at com.sap.engine.lib.xml.parser.XMLParser.scanPI(XMLParser.java:2128) at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2776) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2832) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:231) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) -
at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:144) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) Caused by: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8) at com.sap.engine.lib.xml.parser.XMLParser.scanPI(XMLParser.java:2128) at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2776) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2832) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:231) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) ... 4 more

Creation of one outbound interface for two diferent senders

helo.
i just want to conform ont thing that .
my scenario is two diferent files from 2 diferent business systems are sending to one Rfc.
so i was created only one outbound interface for both senders and one message type bcos the file structure is same for both senders.
so is there any thing wrong in creating only one datatype,message type,message interface for both senders.
waiting for your response.
cheers.
seeta ram.

Hi Ram,
That is perfectly correct when you have two senders and one receiver Scenario and <b>Business Service is different</b>. Then you can use the same Interface.
Just keep in mind that the key for XI to recognise the Right interface is combination of these 3 parameters:
Sender Service, Sender Interface and Namespace. These cannot be duplicated.
When the Message type is same in the sender input data then you can create just one Message Type and One Data type and RFC is anyhow the imported RFC which you need not have to worry.
In Configuration Scenario you need to configure separately the RD, ID, CC and Agreements for the Interfaces.
Hope this answers your query. Let us know if you need anymore clarification
Thanks
Srini

Outbound interface file for the employeesu0092 deduction information from the d

How to Create an Outbound interface file for the employees deduction information from the different Payroll Companies.
Thanks in advance.
Regards
vamsi.

Hi,
The requirement seems to be similar to the one posted in the link https://forums.oracle.com/thread/848476. Please check.

Outbound interface program for downl;oading text file

Hi,
I m working with outbound interface program which downloads text file into application and presentation server upon the selection.
My probelm is
The data format in the text file
Whenever interface sends 1 record to the text file and next record should start continuation to the first record with
seperator like some synbol.
Please tel me posr the sent for this

Hi,
I m working with outbound interface program which downloads text file into application and presentation server upon the selection.
My probelm is
The data format in the text file
Whenever interface sends 1 record to the text file and next record should start continuation to the first record with
seperator like some synbol.
Please tel me posr the sent for this

Problem with Outbound Interface for Party in Standard XI Content for SNC

Hi All,
I am configuring a standard XI Content for SNC, the ASN Processing (DIMP ERP Backend). The provided Integration scenario involves three swim lanes which corresponds to an ERP, SCM and an external system. The external system is as an application component that is designed for B2B communication, i.e. a service with party which is called Supplier.
The first action within the scenario is Create ASN in the Supplier swim lane and send a message to the action "Receive ASN and update inventory(in transit)" within the SCM system swim lane. I have created a sender party that corresponds to the Supplier swim lane and also a receiver party that corresponds to the SCM system. I used the Integration Scenario Configurator to assign services and also all the comm. channel. However, when i try to generate the logical routing objects and collaboration agreements, i get the error message that there was no outbound interface associated with the sender(the external system) defined for the first action. There is no option within the Integration Scenario Configurator on how to assign/define the outbound interface that I want to use for the sender.
I have no idea how to assign the outbound interface to the action for the Supplier swim lane in an Integration Scenario that is from an XI Content. Has anybody configured something similar or come across the same problem? Any info will be much appreciated.
Luqman

Hi,
This could be the problem of confilting namespace or combinations.
in receive action just check that right message interface is configured at Inbound side.
just check any place void ?
1)just check the name as case sensitive.
2)Just check is there interface belongs to right software component.
3)Just check mapping assigned to the right combination or not.
its better to cross check all the component are assigned to right place or not.
****if helpful then rewards points
Regards,
Sumit Gupta

Sftp procedure for outbound interface

Similar Messages

Maybe you are looking for