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

Similar Messages

IDOCS: Inbound non-SAP system

Hi
The outbound idocs works fine. I want to create an inbound goods receipt/movement idoc.
Should i rather write RFC to update the SAP system from a non-SAP system ?

Hi,
Your first query...
Should i rather write RFC to update the SAP system from a non-SAP system ?
Always prefer using idocs for posting before BAPI / RFC fucntion module.
As you have mentioned outbound idocs are working fine..which means you are able to create idocs from non-sap system..right? If so you can use same idoc type for posting.
Your second query's answer...
Check out following code for calling BAPI_GOODSMVT_CREATE
You need to code to call function module /BAPI in your posting program as follows..
append the data into the corresponding internal tables and work-area, check for the IMPORT and TABLES parameter in the function module BAPI_GOODSMVT_CREATE.
a.     GOODSMVT_HEADER-DOC_DATE = SYST-DATM
b.     GOODSMVT_HEADER -PSTNG_DATE = RECEIPT_DATE (Input File)
c.     GOODSMVT_HEADER - HEADER_TXT = BATCH ID (Input File)
d.     GOODSMVT_HEADER - GR_GI_SLIP_NO = GOODS_INWARD_NO (Input File)
e.     GOODSMVT_ITEM-MOVE_TYPE = Constant 101
f.     GOODSMVT_ITEM-PO_NUMBER = PURCHASE_ORDER_NO (Input File)
g.     GOODSMVT_ITEM -PO_ITEM = PURCHASE_ORDER_LINE_NO (Input File)
h.     GOODSMVT_ITEM PLANT = From Selection Screen (WERKS)
i.     GOODSMVT_ITEM STGE_LOC = From Selection Screen (LGORT)
j.     GOODSMVT_ITEM -ENTRY_QNT = QUANTITY_RETURNED (Input File)
k.     GOODSMVT_ITEM -NO_MORE_GR = COMPLETE_INDICATOR (Input File). Value X if status = X else space.
6.     Call the function module BAPI_GOODSMVT_CREATE.
7.     Use function module BAPI_TRANSACTION_COMMIT to do the commit work.
append the data into the corresponding internal tables and work-area, check for the IMPORT and TABLES parameter in the function module BAPI_GOODSMVT_CREATE.
a.     GOODSMVT_HEADER-DOC_DATE = SYST-DATM
b.     GOODSMVT_HEADER -PSTNG_DATE = RECEIPT_DATE (Input File)
c.     GOODSMVT_HEADER - HEADER_TXT = BATCH ID (Input File)
d.     GOODSMVT_HEADER - GR_GI_SLIP_NO = GOODS_INWARD_NO (Input File)
e.     GOODSMVT_ITEM-MOVE_TYPE = Constant 101
f.     GOODSMVT_ITEM-PO_NUMBER = PURCHASE_ORDER_NO (Input File)
g.     GOODSMVT_ITEM -PO_ITEM = PURCHASE_ORDER_LINE_NO (Input File)
h.     GOODSMVT_ITEM PLANT = From Selection Screen (WERKS)
i.     GOODSMVT_ITEM STGE_LOC = From Selection Screen (LGORT)
j.     GOODSMVT_ITEM -ENTRY_QNT = QUANTITY_RETURNED (Input File)
k.     GOODSMVT_ITEM -NO_MORE_GR = COMPLETE_INDICATOR (Input File). Value X if status = X else space.
6.     Call the function module BAPI_GOODSMVT_CREATE.
7.     Use function module BAPI_TRANSACTION_COMMIT to do the commit work.
Hope this will help you.
Cheers,
Nilesh

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

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

Stop generation of Inbound IDOC from Non - SAP

Hi Experts,
I have a requirement to update data base PA0105 for Email. The Email is coming for external system (Non SAP), which contains 1 employee in 1 IDoc. If SAP has valid email and same has been passed for external system to SAP via Inbound IDoc, it should not update PA0105. Hence, I am deleting the IDOC segments in Exit "ZXHALU07", before RBDAPP01 is getting called. As per the requirement its working fine.
Question: Is there any way to stop generating the IDOC. If the email ID were same, then IDoc should not generate in SAP. Please provide your valuable reply. Thanks.
Regards,
Ganesh R K.

Hi All,
Scenario:
Need to Create Inbound IDOC in SAP system and receive it from Non Sap system.
Problem:
IDOC is successfully dispatched from Non Sap system(Sender Side) but, it is not received to SAP system(Receiver Side).
At receiver side(in SAP system) all configuration settings are fine (RFC destination is tested with no errors, partner profile are given with the inbound parameters, function module is successfully tested with no errors, distribution model is created etc).
In receiving system(SAP) no IDOCs are generated in We02 after sending the IDOC from Non Sap side.
Can any one please suggest me the reason for the above mentioned problem?
Thank you,
Swetha.C

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

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

FM to recive the Idocs from Non-SAP system.

Hi Gurus,,,,
Is there any FM to recive the IDocs from the outside(Non-SAP) into SAP system.
Thanks In Advance.
Abhi....

hi digvijay
You could refer to this link which has method to convert xml to Idoc:
http://www.wmusers.com/forum/showthread.php?t=9059
Best Regards
Manthan.

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

Sending IDoc to Non-SAP system

Hi Folks,
    I have to send an IDoc to the external system. Kindly let me know the steps to be performed for it.
Reagrds,
santosh

Just to be a little more clear. The step 8 in the previous link.
8. Checking the Partner Profiles.
o       Go to T. Code WE20
o       Expand Partner Type 'Vendor'
o       Select the Partner profile __
o       Double click on Message Type ZCATSTIME in Outbound parmtrs.
o       Check Receiver Port is assigned correctlyo
Check the Basic type as your Basic IDOC object.
Disha.

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

IDOC to Non-ABAP-System

I am trying to send an IDOC to a Non ABAP system. The receiving system consists of an "IDOC Listener" which receives and sends. The RFC Destination for the connection between the PI and that system is type T (TCP/IP). When checking it in SM59 or IDX1 on the PI, everything looks fine - connection works. Still when I try to send a message, the adapter call fails with the message "RFC Destination incorrect". Is it necessary to have a type 3 (ABAP system) connection for the IDOC adapter and if yes, is there any way to bypass this? The scenario works fine if I communicate between a standard R/3 4.7 and the 3rd party system (even with the type T destination) - nevertheless PI is intended to be used in between for monitoring etc. - therefore the direct R/3 <-> 3rd Party scenario is no option for me. Any clues highly appreciated.
Cheers,
Andy

Hi,
>>>Is it necessary to have a type 3 (ABAP system) connection for the IDOC adapter and if yes, is there any way to bypass this?
I did a scenario like this (and the other way round) a year ago and as far as I remember I didn't use RFC dest type 3 .
there is an easy way to find it out - just use IDOC classes from service.sap.com/connectors
(server) in order to check what kind of RFC does it expect - I tested those libraries and they worked with PI
without any issues (and with corresponding RFC dest)
Regards,
Michal Krawczyk

HOWTO: Process IDocs from non-SAP sender

Hi everybody!
I have a small problem with the following scenario:
There is an external, non-SAP system that is able to send IDocs. Those (customer-) IDocs are as of now processed by an R/3 backend. Now this solution has to be migrated to an XI-based scenario:
              IDoc                       mult. IDocs
ext.System ---------> XI Integr. Process ---->-->---> R/3
However, all the documentation I found so far is based on an SAP R/3 sender system - and I can't seem to get the configuration for this particular scenatio right. Do any of you have relevant documentation?
Thanx in advance,
Joerg

Hi,
I have to admit - the scenario is somewhat esotheric. But regarding your questions:
Since there has been a communication before, we have the IDoc metadata in the R/3 backend. Using transaction IDX2 I have been able to load the metadata into the XI system w/o problems.
The external system has a certified SAP IDoc "connector" (as they call it) that is able to post the IDoc data- presumably through JAVA JCo or some other method. The only thing that matters to me is that they are right now sending IDocs to the backend directly - without files or something like that.
Now my <i>real</i> problem is that of receiver determination etc. Everytime I send an IDoc to the business process, the external system gets the error message
[code]
com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE:
No service for system <name of external system>,
client <name of XI client> in Integration Directory.
[/code]
This message occurs although I think I have configured the process correctly. Here I try to supply the pipeline of my process:
[code]
SENDER                RECEIVER                REC.DET.
<XI system>           <business proc.>
    <rec. idoc>           <abstr. itf. inp.> n/a
<external system>     <business proc.>
    <rec. idoc>           <abstr. itf. inp.> n/a
<business proc.>      <R/3 backend>
    <abstr. itf. inp.>    <send idoc>         IDoc
[/code]
(Showing this in HTML is veeerys awkward
But this doesn't seem to work...
Any ideas?
Regards, Joerg

EDI Sales order creation in CRM through inbound IDocs from non SAP system

Hi Friends,
We are having a scenario where we need to create a Sales Order in CRM for a B2B EDI transmission through IDoc. Customer is sending the EDI Transmission of his Sales order , which is passing through PI and then reaching to CRM to create a Sales order.This is the design we need to follow to make it happen,we are initially trying to create an order using WE19 for testing and the details are:
Basic Type - CRMXIF_ORDER_SAVE_M01
Message Type - CRMXIF_ORDER_SAVE_M
Functional Module - APPL_IDOC_INPUTI which is automatically giving a status text as " Function module CRMXIF_ORDER_SAVE has been called successfully", but no sales order is saved in CRM.
We are getting idocs posted successfully with status 53 with the statuses sequence 74, 50 ,64, 62 and 53.Our issue is inspire of the Idoc having status 53 and the FM called successfully we are not seeing the sales order created in CRM.
We are stuck here no sales order is created in CRM.
Are we missing any config. - set up - Prerequisit - Any OSS note need to be applied -- ANy middle ware setting ?
Any help will be greatly appreciated.
Thanks
Vijay

Hi Christophe,
Awesome!!!!!! it worked, You are the best.
I could able to create a sales order in CRM,but below are the valid data I passed in the respective segment fields.Except for first 3 values rest all did not get reflected in teh Sales order.I feel i am missing some qualifiers.
Can you kindly share the IDoc data to be passed in...along with respective segments and fields:
Segment                                                 Field
E101CRMXIF_BUSTRANS     OBJECT_TASK
E101CRMXIF_BUSTRANS     PROCESS_TYPE
E101CRMXIF_BUSTRANS     POSTING_DATE
E101CRMXIF_PARTNER                          PARTNER_NO
E101CRMXIF_PARTNER                RELATION_PARTNER_NO
E101CRMXIF_ORGMAN         SALES_ORG
E101CRMXIF_ORGMAN          DIS_CHANNEL
E101CRMXIF_ORGMAN         DIVISION
E101CRMXIF_SALES             PO_NUMBER_SOLD
E101CRMXIF_SALES            YOUR_REF_SOLD
E101CRMXIF_SALES            PO_NUMBER_SHIP
E101CRMXIF_BUSTRANS_ITEM     ITEM_NUMBER
E101CRMXIF_BUSTRANS_ITEM     ITEM_TYPE
E101CRMXIF_BUSTRANS_ITEM     ORDERED_PRODUCT
E101CRMXIF_PRODUCT_I     PROCESS_QTY_UNIT
E101CRMXIF_PRODUCT_I     PROCESS_QTY_UNIT_ISO
E101CRMXIF_PRODUCT_I     BASE_QTY_UNIT
E101CRMXIF_PRODUCT_I     BASE_QTY_UNIT_ISO
E101CRMXIF_SCHEDLIN_I     ORDER_QTY
Thanks a ton in advance .
Vijay

Sap Xml Idoc Inbound in Sap

Hi all
If I have to receive an Edi message from an external system (for example an Invoice from a vendor), could I get in Sap an Idoc from a flat file formatted as a Sap Xml format?
As Sap Xml format I mean the same structure of an xml file generated in Sap to the Xml file port.
(The sap r/3 system is a Sap Enterprise version)
Thanks in advance
Bye
Carlo
Message was edited by: carlo pergola

Hi
Thanks for the answer.
Regarding the FM IDX_XML_TO_IDOC, I thing that I can't use it directly because I have to write a program, I have to read the Xml file (that is located in a special directory of the operative system) and then use the FM putting xml data in the XML_DATA import parameter.
It's correct?
Bye
Carlo

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

Similar Messages

Maybe you are looking for

IDOC INBOUND ( NON SAP system - SAP system )