HowT non-SAP IDoc to XI

Hi! We have scenario, where non-SAP-System will send IDoc-Format to XI.
Design and Configuration in IB is already done and should work.
Hardest part is that a program listens to a RFC-Destination in XI, in other words i created a RFC-Destination which is of type T (TCP/IP) and there is entered a registered program, which runs on the non-SAP-System.
When we test the connection between XI and program everything seems to work. But when we test to send data we get following error:
<i>Code 3 (RFC_SYS_EXCEPTION) reported from RFC interface at RfcIndirectCall(IDOC_INBOUND_ASYNCHRONOUS) with TID=0A5E0F0B3E94470D2F67173F rfc_error_info.message="Transaction IDX1: Port AOQ, client 100, RFC destination contain errors"</i>
Now i don't now which kind of port is meant and also what parameters the external application need to call XI (RFC).
Does someone has a detailed description?!
br

Well ok, changed but where to check the trace file - i am not able to open the log viewer because of this:
Error while loading service Log Viewer
com.sapmarkets.bam.util.BAMRuntimeException: Unable to invoke LogControllerFacadeMBean method: "getMetaDataOfReaders".
changed the runtime environtment (java-version) and restartet VA but nothing changed.

Similar Messages

SAP IDOC - XI - NON SAP IDOC (tRFC)

Hi all,
our scenario is as follows:
1) SAP ERP 2005 send an IDOC to XI (NW04S, 7.0)
2) XI dos nothing, just routing. So no mapping or stuff like that
3) XI should send the IDOc to a non SAP System via a tRFC (registered program id)
a) IDOC can be sent to XI and for test we introduced a file adapter. The IDOC is written to the file system successfully.
b) tRFC is registered connection test ok to the NON SAP System.
c) SLD is maintained with a NON SAP technical and a business system
d) Which adapter to use?
- IDOC Adapter (following 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>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_RCV_SERV</SAP:Code>
<SAP:P1>BS_OS_N_SEEBURGER</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Receiver service BS_OS_N_SEEBURGER cannot be converted into an ALE logical system</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
- RFC Adapter (following 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="OUTBINDING">CO_TXT_ROUTING_BACK_ERROR</SAP:Code>
<SAP:P1>P_OS_EBV_511158_RECEIVER,BS_OS_N_SEEBURGER</SAP:P1>
<SAP:P2>,BS_OS_OSQ_300,,</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error occurred during back-routing Error in communication channel</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
If I set the IDXNOALE the message is succesfully processed but not received by the NON SAP system which is connected to the same tRFC.
I do not know how to set this scenario, any ideas?
Thanks
BR Markus

Hi all,
at first thanks for the fast reply.
I do not use any kind of mapping, so the message should be prozessed through without any changes.
So two questions:
1) Where to set the exactly once, ...?
2) Where to set the return paramaters?
Inside the SLD the logical system name is configured. I had the settings maintained like Sergio wrote it.
I changed my configuration to the following:
- No Party
- No Business System
- Creation of a Business Service with the same Logical System as configured in the Bus of SLD
-> Everything works all right
So I created the scenario with No Party but again with the Bus and everything was all right, so.
I had any error in the first scenario but I do not know which one, too many thing changed during the process of problem solving.
Thanks a lot anyway.
BR Markus

Whether this function module K_DOCUMENT_UPDATE can send IDOC to Non SAP Sys

Hi,
I know function Module K_DOCUMENT_UPDATE can sent IDOC to R/3 systems.
1.Whether this function module can sent the IDOC to Non SAP System?.
2.How to make sure, that the function module can sent IDOC to Non SAP System?.
Please advise.Thanks.
Regards,
Dinesh

Hi Dinesh,
      Inside this function module K_DOCUMENT_UPDATE there is a FM available
CALL FUNCTION 'K_DOCUMENT_SEND'
       EXPORTING
            I_LOGSYS      = LOGSYSTEM
            I_COBK        = COBK
       TABLES
            T_COEP        = LT_COEP
            T_COEPL       = LT_COEPL
       EXCEPTIONS
             This FM is responsible to send IDOCs to the defined logical system LOGSYSTEM. No matter this logica; system is SAP or non-SAP IDOC will be sent. Prerequisite are,
1) RFC connection exist between system
2) Partner profile is configured between the system.
Regards
Ram

Interface between sap to non sap using edi idoc

hello abaper's,
                     i have requirment on creating Interface program for downloading files(PO) from Non-sap system to sap system using EDI Idoc techniques.pls give me a good tips for this requirment..
With Regards
MurugeshRajeev

Hello,
        First of all, we'll need to identify as to what we want to do with the PO Data. For example, If we want to Create Sales Order, there is already a Posting Program available with the Name IDOC_INPUT_ORDERS (FM). This is useful for Creating a Sales Order automatically whenever a PO IDoc is received.
Here is the Information for processing Standard IDoc.
1. WE30 - ORDERS05 - IDoc Type
2. WE31 - Segment Definition for the IDoc Type
3. WE81 - Logical Message Types (ORDERS)
4. WE82 - Assigning the Message Type to IDoc Type
5. WE42 - Define Process Code
6. BD51 - If you want to Code a Custom Function Module,
              then after creating it, you need to register the same
              Function Module in this Transaction Code.
7. WE57 - Assign Message Type / IDoc Type / FM group.
8. WE20 - Partner Profiles
9. WE21 - Port Definitions
Hope this information was helpful.
Thanks and Regards,
Venkat Phani Prasad Konduri

Data elements for IDoc Segments to non-SAP system

Hi,
I need to create IDocs for transferring data to non-SAP system. When I create segmet fields should I create new data elements for all the fields with attributes specific to receiving system? Because there are many fields where the field attributes of SAP system do not match the corresponding fields of receiving non-SAP system.
Thanks in advance!!
Regards,
Sriram

Hi Sriram,
When I create segmet fields should I create new data elements for all the fields with attributes specific to receiving system
Is it custom segments .
Regards,
Madhu.

Idoc b/w sap(r/3) and non sap system .

hi gurus,
how i pass an outbound idoc b/w sap(r/3) and non sap system .
which function module we will use in this scenerio for inbound and outbound idoc both
please guide me with an example .

Hi Pawan,
Non SAP system should have RFC adapter in order to receive and send Idocs from/to SAP.
If this is not your case, you should us a Integrator Middelware with RFC and standard adapters like SAP Exchange Infrastructure.
If for example, your non SAP system is able to process data from flat files you can build next interface: SAP send Idocs to middleware that receive them using RFC adapter, middelware maps Idocs into flat file and send it to a one of non SAP system folder using FTP adapter. Non sap system triggers the flat file into its applications.
Reward points if useful.
Roger

FICA -IDOC for posting the billing data from NON-SAP ISU system

Hi,
Kindly note we are implementing NON-SAP ISU with SAP FICA for the finance implementation. In this context, we ahve identified BAPI for BP and CA. We have decided to go for transaction posting through the transaction FPE1. For this, we are looking for the transaction data IDOC which is CTRACDOCUMENT_ACCOUNT (FICA Posting) in the WEDI. But it seems that it is not yet released. Can anybody help me out for this to either identify the equivalent IDOC or other method to post the data from Banner system (NON-SAP ISU ) system. We are presently not implmenting billing system in SAP ISU, but only FI system

Hi,
you can create the same...
but normal practice what we do is create swc for each system so that it is easy to maintain and easy to extend in the future..
or else follow some conventions if you are just starting the things..
HTH
Rajesh

Receiving IDocs from non-SAP system ...

Hello guys,
I have problem with implementing IDoc-XI-IDoc scenario. The sender system is a subsystem (non-SAP system) sending IDocs but XI is not able to receive them. I thing the IDoc metadata can not be found.
Logical system name of the sender is IF6020DEV. I registered the system in SLD. In Integration Directory I imported the Bussines System IF6020DEV to my scenario and I created communication channel of type Sender IDoc Adapter in it.
In IDX2 I created new port called IF6020DEV and I copied needed metadata into the port. But it doesn't work. Probably I don't do it right because I'm beginner with SAP XI.
Could you give me any advice how to configure XI for receiving IDocs from non-SAP system?
Thank you in advance!
Regards
Zbynek

Thank you very much. The issue described in refered discussion is almost same issue what I'm solving. Unfortunetally the described solution dosn't work for me.
The sender system still returns following error. I know you probably won't understand it because you don't know the subsystem, but maybe you could get some idea what is wrong.
05/29/09 16:09:19.482 idoup2 Logon...
05/29/09 16:09:19.482 idoup2 RfcOpenEx (TRACE=1 CLIENT=110 USER=xxxxxx LANG=D LCHECK=1 GWHOST=xxxxxx GWSERV=3361 ASHOST=xxxxxxx SYSNR=61 PASSWD=<password>)
05/29/09 16:09:19.529 idoup2 Logon RfcOpenEx result=1
05/29/09 16:09:19.607 idoup2 Call to (IDOC_INBOUND_ASYNCHRONOUS) failed (3)
05/29/09 16:09:19.607 idoup2 Handle=1
05/29/09 16:09:19.607 idoup2 key............:
05/29/09 16:09:19.607 idoup2 status.........:
05/29/09 16:09:19.607 idoup2 message........:IDoc-Adapter Eingang: Der Absenderport ist initial
05/29/09 16:09:19.607 idoup2 internal status:
05/29/09 16:09:19.607 idoup2 idoc_upload failed with rc=(3), try(2)
05/29/09 16:09:20.607 idoup2 key............:IDoc-Adapter Eingang: Der Absend
05/29/09 16:09:20.607 idoup2 status.........:EXCEPTION SYSTEM_FAILURE RAISED
05/29/09 16:09:20.607 idoup2 message........:IDoc-Adapter Eingang: Der Absenderport ist initial
05/29/09 16:09:20.607 idoup2 internal status:
05/29/09 16:09:20.607 idoup2 idoc_upload failed with rc=(18), try(1)
05/29/09 16:09:21.607 idoup2 Logoff...

IDOC-- XI-- HTTP (non-sap) 403 Forbidden

Hi guys,
When I execute my scenario IDOC>XI>HTTP (non-sap) URL address Asynchr. The receiver receives the message correctly
but in my XI monitoring the message stands in error mode.
At first sight this is not a big problem because the receiver receives the message correctly
but it would be nice if the message would stand in processed succesfully.
The 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>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_SERVER</SAP:Code>
<SAP:P1>403</SAP:P1>
<SAP:P2>Forbidden</SAP:P2>
<SAP:P3>Service Error</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Http server code 403 reason Forbidden explanation Service Error</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Please don't redirect me to an old topic because I have read all topics and none of them could help me. :s
TIA
Message was edited by: Peter Delve

Hi,
this is the describtion of W3ORG:
The server understood the request, but is refusing to fulfill it. Authorization will not help and the request SHOULD NOT be repeated. If the request method was not HEAD and the server wishes to make public why the request has not been fulfilled, it SHOULD describe the reason for the refusal in the entity. If the server does not wish to make this information available to the client, the status code 404 (Not Found) can be used instead.
May contact web admin.
Regards
Matt

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

HOWTO: Process IDocs To non-SAP receiver

Hi Experts!
Today our SAP R/3 sent the IDoc LOIPRO to non-SAP external system, called O2P.
Now, we would like to send this IDoc (LOIPRO) to XI, and the XI sends the IDoc to the non-SAP external system.
Then, our scenario will be:
Step 1. The IDoc LOIPRO is sent from SAP R/3 to XI
Step 2. Inside the XI, this message is routing and mapping to the
IDoc LOIPRO too.
Step 3. The XI sends the IDoc LOIPRO to the O2P (non-SAP external system).
Well, until Step 2, everything is OK.
But, we are having troubles to create an IDoc Adapter receiver to O2P (external system), because the O2P is a non-SAP system.
So, how can we create the communication channel IDoc Adapter, if the receiver isn't a R/3 system ?
All information will be welcome.
Thanks a lot,
Honorato

HI,
You can achieve this by dealing with the Native IDOC structure via Integration server for Non-sap systems.
In this case you can use the IDOC adapter to receive the IDOCs to Non-SAP system. Its like treating the receiver Non-SAP system as an SAP system only. For this Non-SAP system should be compatible enough and SAP certified to accept the IDOC structures..
Refer similar kind of discussions and reference docs.
Sending and Receiving IDOC from SAP to Non SAP system
http://help.sap.com/saphelp_nw04/helpdata/en/52/16abc2543311d1891c0000e8322f96/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a6524507d11d18ee90000e8366fc2/frameset.htm
Thanks
swarup

Sending IDoc from Non-SAP system to XI

Dear all,
We have a non sap system which needs to send IDoc to XI, Please could you answer my following four questions
1. What should be the values for the following fields in the IDoc control record
e.g. RCVPRN = <logical system name of XI>
SNDPOR
SNDPRT
SNDPRN
RCVPRT
RCVPOR
2. How does XI decide which port(idx1) to be used when it receives an idoc
3. The third party system is a non sap one, so it does not have a client no, so I would assume, I need to use another SAP system as a meta data provider, in that case, how would i tell XI to use that port when it receives IDocs from the non-SAP system ?
4. In what step does XI use the logical system name of the Business system(in SLD)?
Thanks in advance
cheers
danus
Edited by: Chidambaram Danus on Jan 25, 2008 2:21 PM

Hi
there is bit wrong interpretation of the statement
If the sender system is a non-SAP system, the sender service is identified from the logical system name of the sender port.
If the sender system is nonSAP it indicates taht the data is coming to XI from non sap systems such as file, database, webservice etc. to XI and from XI it will pass to sap as IDOC inbound.
For this you need to create the logical system in SAP (receiver) and pass on that value to IDOC header.
You could maintain it in the Business service used for Sender system (nonSAP). here it will be available in the tabs ---> History.
note : IDOC is the concept of data container in SAP, you will not be able to have the IDOCs in non sap systems...
Thanks
Swarup
Edited by: Swarup Sawant on Jan 25, 2008 2:54 PM

Unable to send IDOCs from SAP PI 7.3 system to a NON-SAP system

Hi Experts,
We have a simple file to IDOC scenario in our SAP PI system. There is no mapping as the file is already in the IDOC-XML format.
However , the target system is a NON-SAP system. We are using a TCP/IP RFC destination to connect to it.
Here are the settings we have done,
1) Creates a 3rd party technical system and business system in SLD.
2) We have assigned a logical system name for the business system (LSKABA100).
3) Created a port in IDX1 with the same name LSKABA100 and assigned the TCP/IP RFC destination. The RFC destination is pinging fine.
4) Imported the metadata for the IDOC from a SAP port and copied the same to LSKABA100 port.
5) Created the sender agreement, receiver determination, interface determination and receiver agreement in ID.
When we send the file, there is an error on SM58 transaction of our PI system. It says "RFC_ERROR_SYSTEM_FAILURE: IDocException occurred."
Other than that it does not provide a lot of details.
We have seen this thread and this blog but did not get any break through.
Please help us, if someone has any ideas.
Best Regards,
Ravikanth Talagana

Hi all,
I am not using any SAP Jco user either in my config or in the RFC destination.
What is the user id that needs to have the authorization?
I am using a TCP/IP RFC destination and it does not have any user id/pwd.
There is also, no problem while doing a connection test to the RFC destination.
Best Regards,
Ravikanth Talagana

Send IDOC from XI to an Third Party Non-SAP System

Hello Everyone ,
Is it possible to use XI IDOC adapter to send an IDOC to a Third-party non SAP system . This third-party-system handles IDOCs .
We want to do
SAP -> idoc -> XI -> idoc -> Third Party .
Any response is appreciated . Thanks.

Hi Rahul,
Check this out if it is helpful for your scenario:
[Connections to Non-SAP Systems|http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a6524507d11d18ee90000e8366fc2/frameset.htm]
Regards
Praveen K

*IDOC INBOUND ( NON SAP system - SAP system )*

I am transferring IDOC INBOUND ( NON SAP system ->> SAP system ) by calling SAP standard funtc module IDOC_INBOUND_SINGLE using SAP JCo.
In which I am passing all necessary information in Control Record regarding sender and receiver port/IDOC/segment etc.
BUT help me to clarify my doubt that if i am calling a function and i am able to access SAP FM, then why i have to specify the SAP port/RFC connection at RECEIVER end in WE21.
Whats the Significance if i am calling the FM from same SAP system and configuring the port explicitly in WE21.*
If i don't Specify in we02 i am getting error as EDI : RECEIVER PORT in CONTROL RECORD is INVALID

Dear Sree,
For Basic understanding of IDOC read : saptechnical - Step-by Step ALE IDOC guide ( all necessary TCodes available here )
Kindly let me know your data flow .
In short :
As per my scenario the data flow is from non SAP to SAP i,.e. Inbound processing.
At my non SAP i am calling SAP standard function IDOC_INBOUND_SINGLE using SAP Jco 2.1.
You have to fill all Control Structure EDI_DC40 ( port etc. ) and Table parameter EDI_DD40 ( segment etc. )
Read IDOC status and error in WE02.
Goodluck.
- Aakash

HowT non-SAP IDoc to XI

Similar Messages

Maybe you are looking for