Problem in IDoc XML Port Configuration

Hi All,
I'm trying the XML port scenario as per the blog /people/stefan.grube/blog/2006/09/18/collecting-idocs-without-using-bpm
The problem is the output XML file contains all the IDocs, not the exact number what we specify in the report RSEOUT00. For example if I specify 5 as Max No.Of IDocs for that report, the output file should have only 5 IDocs and not all which are waiting in the ALE layer. Is that correct? Or am I missing any configuration?
Thanks,
Joe.

Hi Ravi,
I've used the option EDI_PATH_CREATE_DATE_TIME for the filename (Function Module Description). So it should create new files for every execution. Correct?
Actually, I had given the Max IDocs no to 3 (scheduled every hour) and executed 7 Idocs from WE19 expecting 2 files and 1 IDoc in the ALE Queue. But all 7 of them were written to the file.
Thanks,
Joe.

Similar Messages

Query about IDOC XML Port

Hi,
I'm trying out the blog https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/4443. [original link is broken] [original link is broken] [original link is broken] But, I don't see any advantage of using this as it's like appending the file (because each IDoc xml will have it's own start and end tag). Please clarify.
Thanks in advance.
Regards,
Joe.

Hi Joe,
In that case, the root node's occurances should be changes from 1:1 to 1: unbounded.
In general, the idoc's minimum and maximum occurances will be 1.
You have to download the XSD of the standard IDOC and edit the root node occurances to:
xsd:element name="IDOC" type="ORDERS.ORDERS05" minOccurs="1" maxOccurs="unbounded"
then upload the new XSD as external definition.
Then use this external definition as the source structure in the mapping.
Regards,
Ravi

Splitting multiple IDoc XML files into single IDoc messages for R/3

Hi all. I have a problem splitting IDoc XML files coming in to XI. I currently have an interface that takes in single store sale IDoc transactions (type WPUBON01) in an IDoc XML file. I then have some complex graphical mapping on the IDoc before sending to R/3 via the IDoc adapter. This works fine. However, we now wish to include multiple sales in one file i.e. many WPUBON01 IDocs. I could use message splitting to do this BUT the mapping is so complex, I do not wish to have to change it to enable the processing of many IDocs in one file instead of just one.
What I want to do: have one mapping splitting a multiple IDoc XML file into single IDoc messages and then another taking these single messages as before and performing the mapping. I cannot find a way to do this in one interface; the main problem I'm having is getting XI to split the multiple IDocs into many single IDoc messages within XI itself. I'd be very grateful for any advice on the best way to do this.
Thankyou.
Stuart Richards (Halfords, UK)

Bhavesh,
Thanks again for a clear explanation... I'm moving forwards but still struggling. I've been on this all afternoon today (after a break on other things) and just cannot get my message to split properly (though the SOAP adapter problem I had earlier is now fixed!). If my initial IDoc XML file contains this format:
<WPUBON01><IDOC>....</IDOC>
<IDOC>....</IDOC>
<IDOC>....</IDOC></WPUBON01>
.. I'm not sure what the cardinaility on the first message mapping and interface mapping should be. I'd have thought the source interface would be 1 and the target would be 0..unbounded but this isn't working. I'm trying different things but I get different errors each time. Currently, I have the above cardinality in my first interface and I'm passing in the following data:
<WPUBON01><IDOC><EDI_DC40><TABNAM>EDI_DC40</TABNAM><MANDT /><DOCNUM /><DOCREL>620</DOCREL><DIRECT>2</DIRECT><IDOCTYP>WPUBON01</IDOCTYP><MESTYP>WPUBON</MESTYP><MESCOD>ST6</MESCOD><SNDPOR>WPUX</SNDPOR><SNDPRT>KU</SNDPRT><SNDPRN>0518</SNDPRN><RCVPOR /><RCVPRT>KU</RCVPRT><RCVPRN>0518</RCVPRN><REFINT>00000003832292</REFINT></EDI_DC40><E1WPB01 SEGMENT="1"><POSKREIS>0518</POSKREIS><KASSID>29</KASSID><VORGDATUM>20071029</VORGDATUM><VORGZEIT>160633</VORGZEIT><BONNUMMER>1001</BONNUMMER><KASSIERER>100</KASSIERER><CSHNAME> </CSHNAME><BELEGWAERS>GBP</BELEGWAERS><E1WPB02 SEGMENT="2"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="3"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="4"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="5"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="6"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="7"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="8"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="9"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="10"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="11"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="12"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="13"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="14"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="15"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="16"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB06 SEGMENT="17"><VORZEICHEN></VORZEICHEN><ZAHLART>PTCS</ZAHLART><SUMME> </SUMME><KARTENNR /><ZUONR>1001</ZUONR></E1WPB06></E1WPB01></IDOC><IDOC><EDI_DC40><TABNAM>EDI_DC40</TABNAM><MANDT /><DOCNUM /><DOCREL>620</DOCREL><DIRECT>2</DIRECT><IDOCTYP>WPUBON01</IDOCTYP><MESTYP>WPUBON</MESTYP><MESCOD>ST6</MESCOD><SNDPOR>WPUX</SNDPOR><SNDPRT>KU</SNDPRT><SNDPRN>0518</SNDPRN><RCVPOR /><RCVPRT>KU</RCVPRT><RCVPRN>0518</RCVPRN><REFINT>00000003832293</REFINT></EDI_DC40><E1WPB01 SEGMENT="1"><POSKREIS>0518</POSKREIS><KASSID>29</KASSID><VORGDATUM>20071029</VORGDATUM><VORGZEIT>160634</VORGZEIT><BONNUMMER>1002</BONNUMMER><KASSIERER>100</KASSIERER><CSHNAME> </CSHNAME><BELEGWAERS>GBP</BELEGWAERS><E1WPB02 SEGMENT="2"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="3"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="4"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="5"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="6"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="7"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="8"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="9"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="10"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="11"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="12"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="13"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="14"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="15"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="16"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB06 SEGMENT="17"><VORZEICHEN></VORZEICHEN><ZAHLART>PTCS</ZAHLART><SUMME> </SUMME><KARTENNR /><ZUONR>1002</ZUONR></E1WPB06></E1WPB01></IDOC><IDOC><EDI_DC40><TABNAM>EDI_DC40</TABNAM><MANDT /><DOCNUM /><DOCREL>620</DOCREL><DIRECT>2</DIRECT><IDOCTYP>WPUBON01</IDOCTYP><MESTYP>WPUBON</MESTYP><MESCOD>ST6</MESCOD><SNDPOR>WPUX</SNDPOR><SNDPRT>KU</SNDPRT><SNDPRN>0518</SNDPRN><RCVPOR /><RCVPRT>KU</RCVPRT><RCVPRN>0518</RCVPRN><REFINT>00000003832294</REFINT></EDI_DC40><E1WPB01 SEGMENT="1"><POSKREIS>0518</POSKREIS><KASSID>29</KASSID><VORGDATUM>20071029</VORGDATUM><VORGZEIT>160634</VORGZEIT><BONNUMMER>1003</BONNUMMER><KASSIERER>100</KASSIERER><CSHNAME> </CSHNAME><BELEGWAERS>GBP</BELEGWAERS><E1WPB02 SEGMENT="2"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="3"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="4"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="5"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="6"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="7"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="8"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="9"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="10"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="11"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="12"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="13"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="14"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="15"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="16"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB06 SEGMENT="17"><VORZEICHEN></VORZEICHEN><ZAHLART>PTCS</ZAHLART><SUMME> </SUMME><KARTENNR /><ZUONR>1003</ZUONR></E1WPB06></E1WPB01></IDOC></WPUBON01>
In the message monitor, I get a chequered flag. Great. However, I get the dreaded error 500 in the SOAP receiver comm channel:
SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
Exception caught by adapter framework: SOAP Error
Delivery of the message to the application using connection AFW failed, due to: SOAP Error.
Any ideas as to what this might be?! I'm getting there.... if I get a solution out of this, I promise to write the blog myself!
Cheers
Stuart

Issue with the configuration of http xml port for sending the idoc

Hello,
      I am planning to send multiple idocs in a single file using http xml port.
Presently I am trying to send a single idoc, but am having the issue.
I am trying to create a RFC for HTTP XML port of type H i.e. HTTP Connection to ABAP System
In the how to guide for - How Tou2026 Send Multiple IDocs Within One XI Message
( https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/30ea2fdf-f047-2a10-d3a2-955a634bde6b )
the following parameters are defined for the path prefix -
RFC destination of type H (HTTP Connection to R/3 System).
Specify the path prefix as follows:
/sap/xi/adapter_plain/
?namespace=< your namespace>
&interface=<IDoc_Type>
&service=<Sender System>
&qos=EO (or EOIO).
I am trying to use the following prefix -
/sap/xi/adapter_plain/
?namespace=urn:sap-com:document:sap:idoc:messages ( this is the standard namespace of SAP for all the idocs)
&interface=DEBMAS05 (Idoc type )
&service=SNDLS100 ( ECC system name )
&qos=EOIO
On testing the RFC connection, I am getting the error of page not found.
Can anyone please give me pointers for the issue.
Regards,
Mayank

Thanks Barry!!!
Now I am getting a different message.
In RFC...it is giving me the following message ->
Status HTTP Response     204
Status Text     Body is empty
In case of Idoc, the status is till 02...
the error description for the idoc is --
"When transferring the IDoc by HTTP, the return code with the message '500<SAP:Error><SAP:Category>XIServer</SAP:Category><S' has occurred.
The target address was: http://emgeccsnd1:8001/sap/xi/adapter_plain/?namespace=urn:sap-com:document:sap:idoc:messages&interf
Check whether the IDoc can be sent again.
It is unfortunately not possible to determine automatically whether the IDoc has in fact arrived in the target system and the error occurred afterwards"
I am still not able to resolve the issue.
Regards,
Mayank

Can't run form from Form Builder 10g - Port configuration problem?

Hi,
I have installed the Database (10.2.0.1.0) and the Developer Suite (10.1.2.0.2) on two Linux machines (Red Hat Enterprise Linux ES 4 Basic).
If I enter the frmservlet-URL manually everything seems to be fine.
In one case I enter http://127.0.0.1:8890/forms/frmservlet, in the other http://127.0.0.1:8889/forms/frmservlet; in BOTH cases I get eventually a dark square and the status bar says "Applet oracle.forms.engine.Main started".
HOWEVER, if I create a simple form with Form Builder and click on the Button with the green traffic light ("Run Form"), the form runs only on the machine where frmservlet listens on port 8890.
On the other machine (frmservlet configured to listen on port 8889) Firefox pops up, the URL "http://127.0.0.1:32979/6dOrpwghCqnp8PhMT7KVT533m3IaArqFbPqPBOztZXWYSsNy" gets called, and nothing else happens. The screen displays the string "ORACLE FORMS." and the status bar says "Waiting for 127.0.0.1...", and it stays like this forever.
I assume this is a port configuration problem, but I don't have a clue where to start.
Any suggestions how I should proceed are greatly appreciated.
Thank you very much in advance!

Hi Frank,
Thank you for your reply.
I doublechecked my configuration.
In the dialog Edit --> Preferences --> Runtime the Application Server URL is set to "127.0.0.1:8889/forms/frmservlet".
However, when I attempt to run the form, the URL "http://127.0.0.1:33140/W2dwbV9eXS2fPkuKlxNhCxFWdEihwDviat2uV7ycrSotqwDN" gets called.
The screen displays the string "ORACLE FORMS." and the status bar says "Waiting for 127.0.0.1...", and that's it.
I wonder how the port number 33140 got selected. Interestingly, this time it is a different number; last time it was port 32979. In fact, the port number seems to change each time; I tried again and now it is 33189.
I will now try to set the port number for the frmservlet to 8890.
I choose Edit --> Preferences --> Runtime and set the application server URL to "127.0.0.1:8890/forms/frmservlet".
I stop the container, open /home/oracle/OraHome_1/j2ee/DevSuite/config/default-web-site.xml and change the port number to 8890:
<?xml version="1.0" standalone='yes'?>
<!DOCTYPE web-site PUBLIC "Oracle Application Server 10g XML Web-site" "http://xmlns.oracle.com/ias/dtds/web-site.dtd">



<web-site port="8890" protocol="http"
display-name="Oracle Developer Suite 10g instance of Oracle Containers for J2EE Web Site">

     
     
     <default-web-app application="default" name="defaultWebApp" root="/j2ee" />

<web-app application="forms" name="formsweb" root="/forms" />


<web-app application ="reports" name="web" root="/reports" />
<web-app application = "reports" name="demo" root="/repdemo" />
     
     <access-log path="../log/default-web-access.log" />
</web-site>
I restart the container, start Form Builder, connect to the database, and open my test form.
When attempting to run the form, the URL "http://127.0.0.1:33437/Pl0n3ky9vmU5z37A7ScBnQhsGwq3jwuzJpgTAKWPMOYIzT8K" gets called (again a new port number, apparently picked radomly within a certain range) and nothing happens: "Waiting for 127.0.0.1...".
However, when I enter the URL http://127.0.0.1:8890/forms/frmservlet I do (eventually, after confirming that I trust the certificate etc.) get a darc rectangle and the status message "Applet oracle.forms.engine.Main started", which tells me that my setup can't be that far off target.
Here is the output of netstat:
[root@localhost ~]# netstat -anp --tcp
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:32769 0.0.0.0:* LISTEN 2779/rpc.statd
tcp 0 0 0.0.0.0:23910 0.0.0.0:* LISTEN 5269/java
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 2759/portmap
tcp 0 0 0.0.0.0:1521 0.0.0.0:* LISTEN 4265/tnslsnr
tcp 0 0 0.0.0.0:113 0.0.0.0:* LISTEN 2983/xinetd
tcp 0 0 127.0.0.1:7830 0.0.0.0:* LISTEN 4429/spamd --port 7
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 2928/cupsd
tcp 0 0 0.0.0.0:9240 0.0.0.0:* LISTEN 5269/java
tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 3002/sendmail: acce
tcp 0 0 0.0.0.0:8890 0.0.0.0:* LISTEN 5269/java
tcp 0 0 0.0.0.0:32795 0.0.0.0:* LISTEN 4231/ora_d000_orcl
tcp 0 0 127.0.0.1:1521 127.0.0.1:32817 ESTABLISHED 4265/tnslsnr
tcp 0 0 127.0.0.1:32817 127.0.0.1:1521 ESTABLISHED 4209/ora_pmon_orcl
tcp 0 0 127.0.0.1:33425 127.0.0.1:1521 ESTABLISHED 5298/frmbld
tcp 0 0 127.0.0.1:1521 127.0.0.1:33425 ESTABLISHED 5311/oracleorcl
tcp 1 0 80.133.127.83:33485 209.132.177.100:443 CLOSE_WAIT 4060/python
tcp 1 0 80.133.127.83:33484 209.132.177.100:443 CLOSE_WAIT 4060/python
tcp 1 0 80.133.127.83:33494 209.132.177.100:443 CLOSE_WAIT 4060/python
tcp 1 0 80.133.127.83:33520 209.132.177.100:443 CLOSE_WAIT 4060/python
tcp 0 0 80.133.127.83:33529 209.132.177.100:443 ESTABLISHED 4060/python
tcp 0 0 80.133.127.83:33528 209.132.177.100:443 ESTABLISHED 4060/python
tcp 1 0 80.133.127.83:33460 209.132.177.100:443 CLOSE_WAIT 4060/python
tcp 1 0 80.133.127.83:33470 209.132.177.100:443 CLOSE_WAIT 4060/python
tcp 0 0 :::22 :::* LISTEN 2968/sshd
tcp 0 0 ::ffff:127.0.0.1:33437 :::* LISTEN 5298/frmbld
tcp 697 0 ::ffff:127.0.0.1:33437 ::ffff:127.0.0.1:33439 CLOSE_WAIT -
tcp 348 0 ::ffff:127.0.0.1:33437 ::ffff:127.0.0.1:33440 CLOSE_WAIT -
[root@localhost ~]#
The question remains: Where do those port numbers come from?
Regards,
jme

Port Configuration EDI/IDoc

Please anybody can explain me in detail Port Configuration for EDI/IDoc(T Code WE21).
please explain how can i create new port.
it's urgent please.
thanks
RP

rp
check the following links
http://help.sap.com/saphelp_47x200/helpdata/en/af/7e844367c24d4a950df3205052769d/frameset.htm
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm

ALE IDOC to XML IDOC scenario using XML port

Hi,
I am working on ALE IDOC to XML IDOC scenario using XML port . The requirement is to place a XML IDOC on the application server using ALE IDOC scenario ( output type is created in NACE which is ALE enabled ).
Can anybody help me on the steps.
Regards
Kumar
Moderator message: please search for available information/documentation.
Edited by: Thomas Zloch on Sep 8, 2011 6:01 PM

U can give a try as follows.
In the Partner Profile of Sender R/3 system,
Give the Receiver Party P_Party in the PartnerNo. Give the 'Business Partner' as logical System type.
In XI, Party Definition of P_Party
Give the following Alternative Identifier
Agency -   Sender R/3 Business System
Scheme -   ALE#GP
Value    -    P_Party

Orders IDOC XML File Size Problem

Hi,
I am generating an XML through XML port using IDOC. But I am getting on 3 KB XML file, so that a lot of Data is truncated. How I get the complete XML file.

Hi Raghu,
have a look at the XLSX file generated by Excel, you'll see that it's simply a zipped file. So you can't do it with a transformation, but you need CL_ABAP_ZIP class. I advise you to look at the abap2xslx project ABAP code (currently 3.0) to see how it works.
Best regards,
Sandra

Problems of Port Configuration while upgrading from 4.0B to ERP 6

Hi all,
We are upgrading a system from 4.0B to ERP 6. Will there will be any problems from port configuration side? If any please tell what they might be.
thankyou.

Hello,
We have upgraded from 4.6C to ECC6.0 and did not have any port config issues.
Things to look for:
- RFC destinations, do they still work
- directories used in File type ports, are they still there (they should be)
Hope this helps a bit
Regards
Greg Kern

Posting Idoc from XML port to FTP

Hello Experts,
I have a business case, where the xml generated from and xml port has to be posted on to an FTP. Presently we are doing it manually by getting the xml from CG3Y T-Code and posting it on to FTP manually. Is there any way for posting the Idoc.xml directly on to the FTP, without our intreaction?
Can this be done by customizing the ALE config,s? Or we need to wirte an ABAP code?
Another concern is that every time, I generate an IDoc, the previous IDoc is over written. Can this process, changed so that the previous dosent get overwritten insted it creates a new xml, every time we tigger and Idoc.
Thanks,
Suma

Hi Suma,
To FTP the IDoc.xml you can use shell script which will FTP the IDocs to the FTP server. This shell script can be scheduled on the application server at OS level to be executed at a given frequency (say every 10 mins).
The other way of doing this is maintain the shell script details in the Outbound Trigger of the XML File port and set the radio button in partner profile to Start Subsystem in Outbound parameters tab. This will make the shell script to be executed after the IDoc is written to the XML File port.
If you are not intersted in writing shell scripting, you can directly use the HTTP xml port. This is very easy to use and you can have tight integration. When ever an Idoc is triggerd this will direclty send it accross the HTTP server and from you can make use of it. On any tomcat you can create a HTTP server. If you are using Websphere product as integraion then, it is directly proived by IBM. I suggest you to go for the HTTP rahter doing it on XML Port.
You have a disadvantage for XML port that ever time you generate an Idoc it will be over written. So there is chance that you may miss some of the Idoc's.
Thanks,
Srikanth

Port configuration problem

After updating Safari, my "port configuration" does not recognize the built-in ethernet option and I can't connect to the internet using Safari. Everything else works properly - Any suggestions?

Hi Jim, and a warm welcome to the forums!
Are you saying that it doesn't show at all in Network>Show:>Network Port Configurations?
If you haven't yet try this...
Safe Boot from the HD, (holding Shift key down at bootup), it will try to repair your Disk Directory while the spinning radian is happening, so let it go, run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, when complete reboot.

Problem with the error at DIO port configuration

I am working on the design of a model of a computer controlled Fuel Injection system using Gasoline Direct Igniton technology. I am using PCI-6025E as my data card and SCB-100 Connector block. My application is to get the digital input from the shaft encoder and the solenoids[acting as Inlet and exhaust valves]get actuated according to the VI. When I am trying to run the program theres an error 10001 occured at DIO port configuration. The statement is as" The error occured at the input string, the arrangement or ordering of the characters in the string is not consistent with the expected ordering". I checked the shaft encoder[S5S-50]pin out connections using an oscillograph and the voltages are as expected. Please let me
know the possible areas where I can figure out the error.

Maruthi;
You are probably using VIs that are not supported by that DAQ device. That DAQ device of yours only allow unstrobed digital updates, meaning that the digital lines will be updated by Software calls.
Since you probably need high speed/accuracy on your digital updates, you would be better served by using the PCI-6534 instead.
Hope this helps.
Filipe A.
Applications Engineer
National Instruments

Idoc-xml to Idoc

Hi,
Sender is a 'party' which generates an Idoc. Some of the fields from this idoc has to be fetched by XI and passed to the receiver R/3 system.
Requirement :
Party -
> Idoc-xml -
>XI--> Idoc--
> R/3
(XI - Adapter Sender) ( IDOC Recevier Adapter)
1) what are the initial setting to be done in Xi & R/3 systems?
2) Any authentication details of the party is needed? ( as the XI sender adapter doesn't have many parameters to eneter in comm channel)
Also, here party is an 'R/3 system', who sends the data as an Idoc.
3) How should i convert the idoc to Idoc-xml? In other words how would i create my source DT,MT and MI ?
Appreciate Ur comments,
Thanks,
Raggy

Hi,
Here are the answers pointwise.
1) what are the initial setting to be done in Xi & R/3 systems?
Initial settings are Port and partner configuration in both XI and R/3 systems. You have to configure the RFC destication also.
2) Any authentication details of the party is needed? ( as the XI sender adapter doesn't have many parameters to eneter in comm channel)
Also, here party is an 'R/3 system', who sends the data as an Idoc.
Why are you using XI - adapter???any specific reason?
If party is an R/3 system then you can use IDOC adapter and if not then you can use FILE adapter to pick up the IDOC-XML file.
3) How should i convert the idoc to Idoc-xml? In other words how would i create my source DT,MT and MI ?
You do not need to convert the idoc to idoc-xml. IDOC adapter will do it automatically.
IDOC will act as a MT and also as a MI.
Hope it clarifies your doubts.
Br,
Madan Agrawal

Problem while reading XML file from Aplication server(Al11)

Hi Experts
I am facing a problem while reading XML file from Aplication server using open data set.
OPEN DATASET v_dsn IN BINARY MODE FOR INPUT.
IF sy-subrc <> 0.
EXIT.
ENDIF.
READ DATASET v_dsn INTO v_rec.
WHILE sy-subrc <> 0.
ENDWHILE.
CLOSE DATASET v_dsn.
The XML file contains the details from an IDOC number , the expected output is XML file giving all the segments details in a single page and send the user in lotus note as an attachment, But in the present output after opening the attachment i am getting a single XML file which contains most of the segments ,but in the bottom part it is giving the below error .
- <E1EDT13 SEGMENT="1">
<QUALF>001</QUALF>
<NTANF>20110803</NTANF>
<NTANZ>080000</NTANZ>
<NTEND>20110803<The XML page cannot be displayed
Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later.
Invalid at the top level of the document. Error processing resource 'file:///C:/TEMP/notesD52F4D/SHPORD_0080005842.xml'.
/SPAN></NTEND>
<NTENZ>000000</NTENZ>
for all the xml its giving the error in bottom part , but once we open the source code and if we saved in system without changing anything the file giving the xml file without any error in that .
could any one can help to solve this issue .

Hi Oliver
Thanx for your reply.
see the latest output
- <E1EDT13 SEGMENT="1">
<QUALF>003</QUALF>
<NTANF>20110803</NTANF>
<NTANZ>080000</NTANZ>
<NTEND>20110803</NTEND>
<NTENZ>000000</NTENZ>
<ISDD>00000000</ISDD>
<ISDZ>000000</ISDZ>
<IEDD>00000000</IEDD>
<IEDZ>000000</IEDZ>
</E1EDT13>
- <E1EDT13 SEGMENT="1">
<QUALF>001</QUALF>
<NTANF>20110803</NTANF>
<NTANZ>080000</NTANZ>
<NTEND>20110803<The XML page cannot be displayed
Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later.
Invalid at the top level of the document. Error processing resource 'file:///C:/TEMP/notesD52F4D/~1922011.xml'.
/SPAN></NTEND>
<NTENZ>000000</NTENZ>
E1EDT13 with QUALF>003 and <E1EDT13 SEGMENT="1">
with <QUALF>001 having almost same segment data . but E1EDT13 with QUALF>003 is populating all segment data
properly ,but E1EDT13 with QUALF>001 is giving in between.

Problem with IDoc scenario - IDocs do not aarive to XI

Hi guys!
I have a problem with IDoc->XI->File scenario. Colleagues send IDocs from R/3 and they are not in the XI. In R/3 they look like if they were correctly sent, however, I can not see them in sxmb monitor. BUT, when they send them again explicitly from R/3 (t-code WE19), they arrive...
REALLY strange...
Any suggestions?
IDX2 metadata loaded.. I think, all needed settings are done.
Question - do I need to set up LS in XI ABAP part?
Thanx, Olian!
P.

Hi Olian ,
just check if u have followed all the following steps
SAP XI
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2) a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
In SLD System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name
Regards,
AshwinM

Problem in IDoc XML Port Configuration

Similar Messages

Maybe you are looking for