Scenario R/3 (Idoc) to XI to (Idoc) JCO External Server (non sap system)

Is this scenario possible ?
We currently have issue with downloading metadata of idoc from external JCO server.
Thanks in advance

Hello Jean-Charles,
Perhaps you can use flatfile instead of JCO connection.
Check this doc: https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/46759682-0401-0010-1791-bd1972bc0b8a
Regards,
Chris

Similar Messages

How to send a IDOC-XML to a non-sap system

Hai Frnds,
Can you give me a hint , if i would like to Convert a IDOC into xml and need to send it to a Non-sap system.And can i use change pointers here...
i have have similar one but it stores in the Front End system only....
waiting for ur replies...

Hi Mr. Jeevan,
And can i use change pointers here..>>>.
i think it wont be useful.. as change pointer only replicates master datas in the target system.
Actually u can use CHANGE POINTER in such cases where When ever changes occur in the field values then idoc triggers automatically and send changed information via ALE to other system.
for example:
u r setting up ALE for material master.
suppose u change material description in one side then change pointers triggers idoc and generate idoc with changed description and send to other end.
main use of change pointers is to track changes and send to other end if there is any changes.
i will suiggest u to follow this....
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e07dcaa0-a92b-2a10-3a96-b3d942bd1539
also see
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
regards
biplab

Configuration needed for non-SAP system as Idoc sender

Hi,
We have a need to connect a non-SAP system which is sending an Idoc to XI. I understand that on the sender side, we need to create a tRFC port from the sender system with the server address of the Integration as the target host?
My question is on the PI side, are the configurations the same as a SAP system, i.e. maintaining the port in IDX1 and getting the metadata in IDX2 or will it be different?

In PI, you will need to create a port in IDX1 with the same port name as the Idoc control record when the Idoc comes from the non SAP system.
As you cannot load the Idoc metdata from your actual source, you will need to copy the Idoc metadata from a actual SAP system or from the port of another SAP system in IDX2
Also, in the Business Service / System, make sure that the logical system name is maintained as per the Idoc control record of the source.
Regards
Bhavesh

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

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

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

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

ALE: Sending IDOC inbound from non-SAP system

Hi
How does one need to setup the SAP system to accept data from an external non-SAP system. Should one setup some sort of conection to trigger an import to SAP?

Hi,
On the SAP side you need to create a partner profile in T.code: WE20 of type LS. And add the message type, idoc type in the inbound parameters section of it.
And you must also specify the partner number you created here, on the IDoc control record.
This link from SAP help, will provide some addition data.
<a href="http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6524507d11d18ee90000e8366fc2/frameset.htm">http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6524507d11d18ee90000e8366fc2/frameset.htm</a>
Hope this helps.
Regards,
Sumant.

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

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.

IDoc adapter with Non SAP systems

SAP XI 3.0 help says:
You can use the IDoc adapter to connect SAP systems (as of release 3.1) and non-SAP systems with the Integration Server using native IDoc structures
What does this mean?
-Naveen.

Hi Naveen,
Let me give a use-case in one of our projects ....we have 2 middlewares in our landscape...webmethods and XI...and in one particular instance there was a need to send an FI IDoc from webmethods to XI and forward it to R/3....
In this case, the webmethods was treated like any other sap system for receiving IDoc into XI(with settings in IDX1)...
Hope this might clarify a little bit...
Thanks,
Renjith

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

Scenario R/3 (Idoc) to XI to (Idoc) JCO External Server (non sap system)

Similar Messages

Maybe you are looking for