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

Similar Messages

Solution Manager System Monitoring for non SAP system

Dear Support,
I have configured the CCMS Agent (SAPCCMSR) for non-SAP system (Windows 2008R2).
The system information (e.g. CPU, Memory, Disks etc) has already showed in RZ20 of Central Monitoring system (e.g. Solution Manager).
How can I do to configure to display these information in the Alert Inbox tab on System Monitoring Workcenter?
Best regards,
Fan Hung

Hi,
Have you defined and added corresponding logical systems for the respective satellite systems?
Here is the sequence of steps you've to do:
in SMSY:
1) Define server, DB, Systems
2) Generate READ, TMW, TRUSTED RFCs to the satellite systems
3) define logical systems and assign the satellite system to it
in Solution_Manager:
1) define new solution
2) add the logical system into the solution
If these steps are successful, you should be able to see the satellite system in SYSTEM MONITORING in Solution_Manager.
Have you already done these steps?
After performing these steps:
Solution_Manager>choose relevant solution>operations setup>Solution Monitoring>System monitoring>Activate monitoring> choose the system and activate monitoring.
Your system will then appear.
Does this help any way?

'Error Occured in the Source System' for Non SAP system

Hi Gurus,
We have an Info Package which is getting the data from the Source System 'DOCP' and it has failed due to 'Error Occured in the Source System'.Since the source system is Non SAP system there is no option 'Replicate Data Sources'.So,First I activated the transfer rules by the program and ran the package again .But again the same error occured.
Please suggest me how to proceed for this error for Non SAP Systems?

Hi,
Check the RFC connection in SM59 and reactivate the source system again.
Hope this helps..
Thank you,
S R.

Is it possible for non-sap systems to consume BDOCs without conversion?

Hi All,
I am new to CRM. I use SAP Jco API's to connect to SAP from my java application. Similarly now i want to connect to CRM.
Basically the required is to consume or send BDOC across Java application (non-sap system) and SAP CRM.
1. Is there a way to fetch the BDOC info from Jco API's and then consume them in Java application?
2. I read about XIF adapter in CRM, It says convert BDOC to IDOC.
Can you tell me if BDOC's can be sent out of SAP to non-sap systems as is without convert to IDOC or should it be always i have to convert to IDOC/XML to consume from non-sap systems ?
You quick reply is greatly apprciated.
Thanks,
Sowmya

Hi,
Yes. It is possible.
You can use the standard XML interface for Business Partner in the name space http://sap.com/XI/ABA.
Regards,
Masa

Technical/business system for non-SAP system

Hi,
I want to use a webservice from a non-SAP system.
It is necessary to define a technical and business system in zhe sld for that non-SAP system?
When yes, is this a standalone or a 3rd party system?
Thanx

I want to use a webservice from a non-SAP system.
It is necessary to define a technical and business system in zhe sld for that non-SAP system?
When yes, is this a standalone or a 3rd party system?
you dont need to create Business system in Sld for 3rd party just u need to create business component in id directly.
please refer SCN for how to create Bus.component.

Can proxies be created for non-sap systems

I have a scenario file->XI->jdbc(non-sap system).
Can we create a abap server proxy instead of using jdbc adapter on the receiver side.
thanks
KK

Hi KK,
This might help you
http://help.sap.com/saphelp_nw04/helpdata/en/ba/d4c23b95c8466ce10000000a114084/frameset.htm
Thanks & Regards,
Agasthuri Doss

Configuring EWA for non Abap System

Hello to everybody.
I am configuring EWA in Portal System 7.01and SOLMAN 7.01 too. It's a new installation and i have a question:
- Which is the order to start to configure SMD?
- Is Necessary configure the CCMSR agent?
I configured EWA in a old system that had installed the agents, but they could not to connect to SMD Server.
I Fixed this problem, but now I need configure the SMD since start.
By the way, I'm new configuring EWA for Java
Thanks.
Esteban G.-
Edited by: Esteban Gutierrez E. on Jan 11, 2010 8:48 PM

Hi Sailesh
Here is related blog fr your issue. Hope this will help you.
setup EWA for portal
Thanks
Jignesh

Scenario for interface between a non sap system and a SAP erp

Hello,
I need some help in order to elaborate a interface between a SAP ERP and a non-sap system with the help of a XI system.
   - At first regarding the interface from the non sap system and a SAP ERP :
       the non sap system sends a flat file to the XI system. The flat file contains a row with header data and rows with item data. We were thinking when the file arrives to the XI system, to save the data in a header database and in a items database in XI. is it possible ?
And then to have like a job that reads the database and creates idoc and sends them to the SAP erp and updates the xi header and items database with a flag that means that the records have been sent to the SAP erp.
   -   Regarding the interface SAP erp to non SAP system:
       the SAP erp sends idoc to XI. Then the idocs are transformed into flat file.
Is this scenario possible ?
Do we need any adaptator between the non sap system and the XI ?
Thank you for your help
Christophe

Hi Bontron,
Idoc doesnot support synchronous call. So you can use either proxy or function module and inturn call the idoc from them and send response back to xi. You need to have two scenarios for your design.
Scenario1:   Source File (file adapter) -- xi -- Dump into database tables (Jdbc Adapter)
Scenrio2: Pickup form Database tables (Jdbc Adapter) -- xi -- RFC Adapter ---> This is synchronous call.
Regarding the interface SAP erp to non SAP system
You can send idoc to xi and from there use File adapter to send to the receiving system.
These blogs may help you to some extent:
/people/sap.user72/blog/2005/06/01/file-to-jdbc-adapter-using-sap-xi-30
https://wiki.sdn.sap.com/wiki/display/XI/step%2bby%2bstep%2bRFC%2bto%2bJDBC%2bscenario   (your scenario will be opposite to this)
Regards,
---Satish

Service desk for non-sap (please - any inputs are welcome)

hi all,,
I know how to setup service desk for SAP use. Can some one provide me some tips on using solution manager - service desk for non-sap as well? eg: the company wants to use service desk for normal activities as well, as laptop not working, server down, other system issues etc.
The questions I have are -
1) Any specific structure to be created for the non-sap? The way we use in SAP specific environment is to use "SAP Components" while creating tickets. How can we create tickets for non-sap components? What will be the "responsibility" selection?
2) How about the Ibase? For SAP, the ibase already have the data from SMSY. How can I get data for non-sap systems? Anything is SAP to keep the Asset management data (like entries of laptops, servers etc)
Thanks for all the suggestions !!
JZKALH

Hi
You need to go for service desk XT which is the extension of service desk to manage non sap or IT incidents
Check below link
https://websmp110.sap-ag.de/_solutionmanager
Heterogeous system environments are a challenge for IT-service management in any company. The associated complex structures and varying forms of media often make it difficult to realize efficient service processes. With SAP Solution Manager Service Desk - Extended Usage (Service Desk XT), SAP offers a centralized support tool as a single point of access - for service requests and problem tickets related to SAP and non-SAP software.
The Single Point of Access for Support
SAP Solution Manager, which is a standard part of every SAP solution and therefore can be used by all SAP customers, supports users in SAP relevant service requests. The standard function of the service desk is restricted to service requests.
With Service Desk XT, SAP provides an extended support tool, which can be also used for general service requests, for example regarding IT or telecommunication equipment.
This priced add-on does not require additional interfaces to third-party products - the same service requests are used for SAP and non-SAP applications. This simplification is a benefit for your employees.
This solution has been created with IT service providers in mind, especially those which work within a company and currently do not have an IT-service desk application in place or would like to replace an existing system.
Also,
check this link
pg(46)
https://websmp205.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700000147532009E
Pg 52 onwards
https://websmp205.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700000059742008E
https://websmp205.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700000548652007E
Hope it helps
Regards
Prakhar

Regarding the Service Registry in SAP PI 7.1 and non SAP System ....!

Hi All ,
I need to know answers for the below Question ...hope to get some answers frm Experts ....
1) How to publish service from non-SAP systems?
2) How to use discovered service in the Service Registry for consumer/provider scenario? With some examples.
Thanks in Advace ...!
Regards ,
Aziz khan .
Edited by: Aziz khan on Sep 16, 2009 11:43 AM

Hi,
1) How to publish service from non-SAP systems?
Publish Service is nothing but making WSDL of that service available. For that you need to Publish the WSDL of the web Service to UDDI. For Non SAP system, Lik .net , Java they have there oun APIs to do so. U can search on net to get it.
For Ex. below link.
http://www.startvbdotnet.com/web/publish.aspx
2) How to use discovered service in the Service Registry for consumer/provider scenario? With some examples.
Once you discover the services, you get the WSDL of that Service. Then You can import this WSDL in IR and you it.
See the below links.
http://help.sap.com/saphelp_nw04/helpdata/en/43/ce993b45cb0a85e10000000a1553f6/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/EN/26/9e97b0f525d743882936c2d6f375c7/frameset.htm
Shweta

NON-SAP Systems in IBASE

Hello,
i have maintained ibase entries for non-sap systems as discussed in an other thread, the entry looks like this:
NSI 000000000 001
and then i put the same entry in the identification tab, but when i go to the work center and try to open a message under this system just after pressing the button to create the notification the following message shows up:
You have not selected a system
I have also maintained SMSY with non-sap system but the problem keeps on taking place.
I really would appreciate some help here, usefull answers will be rewarded.
Many thanks in advance.
Marcos

Check this
http://help.sap.com/saphelp_sm40/helpdata/en/45/37bd3d4beb6d7be10000000a114a6b/content.htm
and morever for steps with screenshot
check
http://www.sappro.com/downloads/NonSAPsystems.pdf
hope all the doubts for creating the same are solved
Regards
Prakhar
Edited by: Prakhar Saxena on Jun 30, 2010 7:27 PM

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.

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

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

Steps of EDI is used to transfer IDOC from R3 system to non sap system

Hi Experts,
Can you provide me Steps to configure EDI is used to transfer IDOC from R3 system to non sap system?
Full points will be assigned.
Thanks in advance!
Sapna

Hello,
         The EDI Configuration required to be done for Transfering IDoc to non SAP System is.
1. First of all, we need to identify the Transaction Data which is required to be Transfered to external System.(Ex: Sales Order Data or Shipment Data or Delivery Related Data).
2. Secondly, Identify the IDoc Type & Message Type. IDoc Type can be found in Transaction WE30 & Message Type Can be explored in Transaction WE81.
3. After that, assign the IDoc Type to Message Type in WE82.
4. Identify the Selection Program (Outbound) which is generally a Function Module in the Form of IDOC_OUTPUT_<Message Type>. Example, if the Message Type is ORDERS, the FM will be IDOC_OUTPUT_ORDERS.
5. Assign the Function Module to a Process Code in WE41 (Process Code for Outbound).
6. Configure Port Definitions in WE21 for which the RFC destinations are to be maintained in Transaction SM59.
7. Maintain Partner Profiles for the Outbound Message Processing in WE20.
8. Last, but not the Least, we need to Focus Mainly on Message Control Configuration which is nothing but maintaining the Output Type for the Outbound IDoc to be Triggered for the Sales Order Application or Delivery Application.
   i. In Message Control Configuration, we'll maintain
      a. Condition Tables
      b. Access Sequences
      c. Output Types
   ii. To Create the above elements, we can go to SPRO Transaction and do the same depending on the Application Area such as Sales / Shipping / Logistics Execution etc.
   iii. For Output Types & Access Sequences, we can go to the Transaction NACE or VK01 in which we'll maintain the Output Types / Access Sequences & Condition Records.
   Please note that all the above steps may not be needed if we are using some of the Standard Elements provided by SAP such as Message Type, Process Code, IDoc Type & Selection Program as many of the Standard SAP Applications have their own Elements for different Application Areas.
   For example, if you want to send an Order Confirmation IDoc when the Sales Order is saved, you can use the Message Type ORDRSP, IDoc Type ORDERS05 & Selection Program as IDOC_OUTPUT_ORDRSP.
   However, Message Control Configuration is the Key Factor and is required for all the Applications as per the Customer's / Client's Requirements.
Hope the above procedure was clear.
Thanks and Regards,
Venkat Phani Prasad Konduri

Configuration needed for non-SAP system as Idoc sender

Similar Messages

Maybe you are looking for