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
Similar Messages
-
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
ZbynekThank 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... -
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 PMHi
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 -
*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 INVALIDDear 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 -
EWA report for non-abap systems
Hi Gurus,
Good day.
I would like to ask, what are the steps that I'm going to do when configuring an EWA report for non-abap systems i.e portal. Do Ineed to install SMD agents on my non-abap systems and connect to diagnostic agent of solman?
Or do I need to install wily introscope agents on my non-abap systems and connect to diagnostic agent?
It is both? Which one?
It would be also great if you can provide me links/documents in relation to my queries.
Please do note that the current version of solman system is 7.1
Thanks in advance for the help
VirgilioHi Virgilio,
To generate an EWA report for Java stack system,
you need to do following:
1. install smd agent (diagnostics agent) on Java stack system
you can install this agent standalone, details see note 1234384.
The installation Guide is also attached in note 1234384.
2. finish Initial Config and Basic Configuration in solman_setup for
solman system, the setting about Enterprise Manager is also included
in these configurations, please ensure EM is running properly.
3. start managed system configuration for the EP system in solman_setup
after selecting the system type 'Java', please finish all steps as
suggested in which step. The Step 'Wily Introscope Configuration' is to
install Introscope Agent which is used for Java stack system. More infor
please read the installation Guide of Enterprise Manager and note
797147.
4. You should be able to see data in Wily Introscope and Workload
analysis via
Root Cause Analysis->End-to-End Analysis->select the system->Workload
Analysis
5. If the EP system is added in a solution, the EWA task for this system
should be shown up in solman's SDCCN.
Also check note: 976054"
Thanks
Regards,
Vikram -
EWA on Non-ABAP System with Solution Manager EHP 1
Hi Experts,
We have recently updated our solution manager from SP Stack 16 to EHP1 (sp 18). we are now planning to set up EWA for non-abap components (EP 7.0). however, the only SAP note that i have been able to find is "976054 - Availability of EWA for Non ABAP components" but this is only limited up to SP 17. I have not been able to find any guides relating to EWA thru Solution Manager EHP1.
I would greatly appreciate if anyone can refer any documents or SAP notes that would enable setting up EWA for non-abap components thru Solution Manager EHP1.
We have also gone through the note 1332428, but we have'nt found it useful. We are still struggling to generate EWA report on Non-ABAP system.
Looking forward to your kind help.
Thanks and Regards,
Sarthak SyalHi Sarthak,
Good!!
Please do the following:
1) include the system in the Solution and scheduled the EWA session.Logical component should refer to the Non-ABAP System with no ABAP instance as relevant under the SID definition in SMSY-systems.
2) Is the Non -ABAP ( assuming its java) has the Software component defined and is mentioned as relevant under the SID with the component name and type.
3) Having said that SMD - Root cause Analysis functionality is configured-> check whether you are getting the Details for the Non-ABAP systems in the analysis Tabs of Root Cause Analysis.
This should be good to go. Wait for the session to get completed.
Thanks,
Jagan -
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 -
How to setup EWA for non-ABAP system with SM 4.0 ?
Hi, we are running SM 4.0 with the support-stack 06. I have set-up a solution for monitoring which includes a NW04 WebAS 6.40 Java only system. Has anyone set-up EWA reports for this type of non_ABAP system who can advise of the steps necessary for this ?
It seems like you need to define RFC destinations for where the monitored system data should be collected from , but there doesn't appear to be anywhere to do this for non-ABAP systems ?
I have looked at Note 738676 - Service Data Download for Non-ABAP Components but it hasn't helped and it seems to be SDCC specific, rather than SDCCN.
Thanks.Hi Andrew,
we are just developing it, at the moment you have the following option, your java system has to send by ccms agends its data to an ABAP 640 system or higher, there you can see its alerts in ccms, then you have to make both system available in SMSY. Then important you have to assign the java system as a system component, then we collect also the java data and shows them in the EWA of the ABAP system. There for go to the main instance tab and set a java main instance to relevant and assign your java system.
This is the old, available standard solution. At the moment we develop it also for java stand alone.
I think it will be available with the new ST-SER in autumn
Regards,
uDo -
Hi,
We are planing to implement EWA for Java systems. Currently EWA is active for all ABAP systems. Do we need Wily Introscope in order to setup the EWA for non-ABAP systems? Or just we can use the SMD to generate EWA reports for Java systems?
Any idea?
Thanks,
KrisThanks Paul
We are on SM 7.0 EhP1. But I see following info in note 976054. It says data sources for EWA are different on 7.0 EhP1, does it mean we don't need wily from 7.0 EhP1 onwards?
Data sources in Solution Manager Diagnostics up to SP17 used for EWA for non-ABAP components analysis are:
- Introscope (SAP Note 797147),
- Garbage Collection (SAP Note 1079125) and
- Portal Activity Reporting (SAP Notes 936612 to know how to activate PAR and 914791, 1075276 to configure SQL
Command Console).
Starting with Solution Manager 7.0 EHP1 (SP18) the data sources are:
- Solution Manager BI for performance data
- Configuration and Change DB(CCDB) for configuration data
Thanks,
Kris -
Roles for Testing ChaRMs for Non-Abap Systems
Hi,
Can you please suggest what all authorizations are required for Testing the ChaRM functionality for non-abap systems
Thanks in advance
Regards,
Reddihi
check the link
Check the Configuration guide for the prerequisites. -
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 -
EWA reports for non abap systems
Hello gurus,
I am facing a problem with configuration of EWA reports for SAP NW Portal.
I have already configured EWA for abap systems, and those are running good on weekly basis. but i have problem with configuration of reports for java systems.
So far, i have installed an SMD agent and CA on my EP-satellite system. I have also configured and SMD server on my Sollution Manager and registered the SMD agent on SMD server and installed Willy Introscope on SMD server.
I am using a central SLD which is running on different host as Solution Manager. I did all the configuration (smsy_setup, configuration of sld_data_supplier etc... )
I have also created the system in SMSY, matched the smsy with SLD (data source SLd)and assigned Logical component to java system.
>>> But when i want do define data collection in the SMD for Gargage Collection (task in scheduler) i cannot see host of my portal system in the SMD.
In the SMD i can see just the abap systems for which the EWA are being already generated.
(i have done also configuration>>connecting managed sytem to the SMD, but i still cannot connect my Portal system to SMD)
Do you have any idea, what i have done wrong?
My solution manager is running on Sap NW 7.0, SPS16,
Sattelite system , EP SPS 19
Thank you very much for your points!!Hello Jagan,
I was following the enclosed guide from the note: 976054, but it doesn't help to solve my issue.
And when i want to permorm the setup for the managed systems,(http://<host><port>/smd -> diagnostic setup->managed systems ->setup wizard) i can not see there my Portal systems, just the abap systems.
Do you have any idea?
Thanks,
Best regards
Slavomir -
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,
santoshJust 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. -
Hi,
I posted this thread at the Solution Manager forum.
I need to confirm what i understood there.
I want to monitor portal (Non ABAP) components in Solution Manager 3.2 .
I was advised that it is not possible in Solman 3.2 and i have to upgrade it 4.0.
Could anyone please confirm this.
Juan , Awaiting your comments.
Others are welcome too.
Regards,
Ashish .A. PoojaryHi,
You have to install solman diagnositic tools to monitor stand alone java stack, But if you want to monitor java stack of abap+java then you have to first register the ccms agent through visual admin. Then you can add the java stack as logical component. But 4.0 has be the better options.
There are many posts in the forum so for adding the java stack .
Regards,
Vamshi. -
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.
Maybe you are looking for
-
High memory usage when rendering
Hi. Using a new cs4 system: I start a new 1080i project. I dynamically link to a new AE file. Within the AE file I put one 4mb jpg running over 20 seconds, and save. Back to Ppro, I put the AE comp on the timeline. At this point, Task Manager shows t
-
Entity bean with another class as primary key generator class
Hi All, I have a CMP entity bean in which I generate the primary key using my own class know as unique id generator. I use it in ejbCreate method in the following manner public Long ejbCreate(HospitalData hospitalData) throws CreateException{
-
Hi, I'm trying to create a new class called Questions, which has two properties (type and condition). The action script is saved in the folder myComponents under the project. When I compile the Main app, I get the following error message: "1172 Defin
-
Oracle 10.2.0.4 downgrade to 10.2.0.1 easiest way ?
Hello all, I would need to downgrade my database ( 10.2.0.4 ) to the previous 10.2.0.1 , is there a simple way or is it really teidious. Much appreciated
-
Is possible to run a windows (windows XP) in a MAC OS ?
My computer have two partitions (mac os Leopard, Windows XP) My computer boots on Mac OS. How to run a windows (Windows XP) in Mac OS. I need to have Mac OS and a windows with Windows XP. Best regards RV