Error in Call Adapter (IDOC- XI- FILE)

Hello,
i have got the following error message in the integration engine monitoring in the "call adapter" part:
td {font-family : Arial, Tahoma, Helvetica, sans-serif; font-size : 14px;} A:link A:visited A:active HTTP response contains status code 503 with the description Service Unavailable XML element Envelope missing in SOAP message header (SAP XI Extension)
What is the AFW application?????

Hi Christian,
Have a look at the following thread, it might be useful
XI Server Malfunction:Error in Receiver Adapter
Regards
Suraj

Similar Messages

File-IDoc scnario : Error in call adapter

Hi Experts,
I have developed File to IDoc scenario. And getting the following error in "Call Adapter" pipeline step. I have mapped the control record values in IDoc like Sender Partner, no, port and same for receiver.
Have created:
In XI: RFC destination to connect to ECC (sm59)
Port for the above RFC sestination (idx1)
In ECC: New logical system for source file system (BD54)
Partner Profile for Source (we20)
Also in Receiver_IDoc_CC, checked options for 1. Apply control record values from payload 2. Take Sender and Receiver from Payload
<?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_IDOC_RUNTIME</SAP:Code>
<SAP:P1>Transaction IDX1: Port SAPEAQ_100, client , RFC destination contain errors</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: Transaction IDX1: Port SAPEAQ_100, client , RFC destination contain errors</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Please tell me if i am doing any mistake.
Br,
Nilz

Hi,
Adding to Björn
Check the Port ( Tcode - idx1 ) Port SAPEAQ_100 & Select the Business System where you declared IDOC adapter -go to - Service and check whether you have mentioned the right Logic System,System ID & Client.
Cheers
Agasthuri Doss

Error during variable substitution: idoc to file

Hi Friends,
I have a got a issue which is Idoc to file scenario.
Iam getting the following error.
Attempt to process file failed with com.sap.aii.adapter.file.configuration.DynamicConfigurationException: Error during variable substitution: com.sap.aii.adapter.file.varsubst.VariableDataSourceException: The following variable was not found in the message payload: date_processing
Could you please tell me waht could be the reason for the same?
as per my analysis, I observed that the field date_processing has been declared

Hi Sandeep ,
If the variable date_processing refers to an element in XML schema, Please check if you have added the prefix payload: to the information under Reference.
The reference then comprises a pseudo path description in the form of a comma-separated list with the schema namea,na,nameb,nb,....
Where namea,nameb,... corresponds to the element name and na,nb,... corresponds to the occurrence of the element name at the respective level in the document.
The description begins at the root of the document and ends at the respective element.
Also please check
Re: Variable substitution
Regards,
Jyoti

Error in call adapter in SXM_MONI

<?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_IDOC_RUNTIME</SAP:Code>
<SAP:P1>MSGGUID 7F8BECB520324BBE088BED6BB02D6CE8: Tag found instead of tag IDOC BEGIN=</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error: MSGGUID 7F8BECB520324BBE088BED6BB02D6CE8: Tag found instead of tag IDOC BEGIN=</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
i am getting this problem in my error analysis.please suggest what could be the issue.
thanks

Hi,
Check the following things:
1.Try importing the Metadata of the IDOC again in IDX 2
2.You might be trying to post multiple IDOC and you need to changed the occurance to 0..unbounded for IDOC as mentioned in the Blog /people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change
Regard,
Srinivas

Error in Call Adapter step

Hello,
We have RFC --> HTTPS scenario.
The RFC Destination of type G is created in XI and the connection test is working fine.
When I run this scenario, sometimes I get following error:
com.sap.aii.af.ra.ms.api.DeliveryException: XIAdapter:ATTRIBUTE_CLIENT:.
Error in sxmb_moni in Call Adapter Step:
<?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="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_CLIENT</SAP:Code>
<SAP:P1>400</SAP:P1>
<SAP:P2>ICM_HTTP_CONNECTION_FAILED</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP client code 400 reason ICM_HTTP_CONNECTION_FAILED</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
However sometimes it works fine.
Please help to resolve this.
Thanks in advance,
Hetal

Hello Hetal,
Can you please elaborate more on the scenario. if it is a RFC -> PI -> SOAP scenario please check if you are using the correct target URL in your Receiver Comm. Channel. Also check if the backend service could be unstable due to network load.
Thanks.
Kiran

Error in Call Adapter

Hello,
We have RFC --> HTTPS scenario.
The RFC Destination of type G is created in XI and the connection test is working fine.
When I run this scenario, sometimes I get following error:
com.sap.aii.af.ra.ms.api.DeliveryException: XIAdapter:ATTRIBUTE_CLIENT:.
Error in sxmb_moni in Call Adapter Step:
SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_CLIENT</SAP:Code>
<SAP:P1>110</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP client code 110 reason</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
However sometimes it works fine.
Please help to resolve this.
Thanks in advance,
Beena.

Thanks Swarup.
The HTTPS connection is used from XI to third party. XI is not receiving HTTPS request.
Still do I need to enable HTTPS on web dispatcher?
The runtime workbench has following error:
Received XI System Error. ErrorCode: ATTRIBUTE_CLIENT ErrorText: ErrorStack: HTTP client code 110 reason
Transmitting the message using connection http://<dispatcher host>:<http port>/sap/xi/engine?type=entry failed, due to: com.sap.aii.af.ra.ms.api.DeliveryException: XIAdapter:ATTRIBUTE_CLIENT:.
Thanks,
Beena.

Error in TRFC for IDoc to File scenario while sending IDoc

Hi,
Configured of 'IDoc to file' scenario is completed. Executed a stand alone program to post IDocs to XXI system using a RFC destination with required previleges.
Outbound IDoc has status successful, but it is blocked in the source system and can be viewed in TCode: SM58 (Transaction RFC). The error status is set as ':00'.
When I tried menu item 'Edit>>Execute LUW', I got the status message as 'Function module does not exist or EXCEPTION raised'.
For your information, User used in RFC destination is communication user with SAP_ALL profile(in XXI system).
Can anybody help me out in resoving the error?
Regards,
Suraj Kumar

Hi,
Thanks for your reply.
It is successfully tested and FYI as the user specified in RFC Destination is a communication user in destination system (XI), it does not have remote logon.
Hope I am clear.
Please let me know, if you need any further information.
Regards,
Suraj

Error in Call Adapter stage

Hi
I am trying to post to the ECC system using XI Adapter. I get this error at the Call Adapter stage
URL http://host:port/sap/xi/engine call was terminated because the corresponding service is not available.
Here the host is the server name of the ECC QAS and port is the ABAP port in SMICM
How do I solve this error?
Regards

Shabarish,
I guess I got the problem though I don't know how to solve it !
Well, when I type this link in the IE, http://host:port/sap/xi/engine?type=entry, where host is the ECC QAS and port is the HTTP port maintained in SMICM, I get the same error that I get in the SXMB_MONI of the PIQ.
Service cannot be reached
What has happened?
URL http://host:port/sap/xi/engine call was terminated because the corresponding service is not available.
Note
The termination occurred in system ERQ with error code 403 and for the reason Forbidden.
The selected virtual host was 0 .
What can I do?
Please select a valid URL.
If you do not yet have a user ID, contact your system administrator.
I think this error has got nothing to do with the service users in PI and it has something to do with the ECC QAS server.
Regards

Error at Call Adapter stage

Hi.
We are experiencing an error at the 'Call Adapter' stage of the pipeline. It seems as if the message is unable to move from the integration engine to the adapter engine with this 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="INTERNAL">CLIENT_SEND_FAILED</SAP:Code>
<SAP:P1>500</SAP:P1>
<SAP:P2>Internal Server Error</SAP:P2>
<SAP:P3>(See attachment HTMLError for details)</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error while sending by HTTP (error code: 500, error text: Internal Server Error) (See attachment HTMLError for details)</SAP:Stack>
<SAP:Retry>A</SAP:Retry>
</SAP:Error>
The HTML dump says u2013
java.lang.NullPointerException:
        at com.sap.engine.interfaces.messaging.spi.transport.TransportHeaders.setHeader(TransportHeaders.java:169)
        at com.sap.aii.adapter.xi.ms.XIMessage.prepareToReceive(XIMessage.java:1437)
        at com.sap.aii.adapter.xi.ms.XIMessage.prepareToReceive(XIMessage.java:1122)
        at com.sap.aii.adapter.xi.ms.XIEventHandler.onRequest(XIEventHandler.java:791)
        at com.sap.engine.messaging.impl.spi.ServerConnectionImpl.request(ServerConnectionImpl.java:237)
        at com.sap.engine.messaging.impl.core.transport.http.MessagingServlet.doPost(MessagingServlet.java:417)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
        at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:163)
        at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:82)
        at com.sap.engine.services.servlets_jsp.server.servlet.AuthenticationFilter.doFilter(AuthenticationFilter.java:124)
        at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:74)
        at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:425)
        at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:289)
        at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
        at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:376)
        at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:85)
        at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
        at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:160)
        at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
        at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67)
        at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
        at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
        at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
        at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
        at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
        at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
        at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
        at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
        at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
        at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
        at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
        at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:309)
        at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:222)
        at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
        at java.security.AccessController.doPrivileged(Native Method)
        at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:152)
        at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)
This occurred after an SLD update. Does anyone know how to fix this issue?
Thanks
Regards
Riaz

Hi guys
1. Sender - Backend ERP (ECC) calling enterprise service, Receiver - SOAP Web service. Both are business systems internal to the network
2. Both sender and receiver are Business systems which are registered in the SLD.
3. This interface was previously working, until the LSD was updated, then it began.
4. PI 7.10
5. All the scenarios which use this type of communication (Proxy to SOAP) are failing at the same stage
I have also logged an OSS call with SAP and they are currently looking at the issue.
Regards
Riaz

Error in call of IDOC adapter

Hi!
I am facing with very strange IDOC error in adapter call.
Can some one help me to solve this problem please?
- <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_IDOC_METADATA</SAP:Code>
<SAP:P1>I::000</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Fehler: I::000</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Thank you very much!
regards
Thom

I hope you have loaded the IDOC Metadata in IDX2?
Please check the SAP Note 940313 the problem C in this Note (Below are content)
c) Error message: "::000"
Solution:
This error occurs if the central XI system tries to load the IDoc metadata from the sending system by RFC.
There may be several different reasons for the failure of the metadata import, the error is not transferred in full by tRFC completely, and this results in the error message above.
User cannot log onto sending system
User/password/client is not correct or the user is logged due to too many failed logons.
      Activities in sender system ABC:
      Transaction SM21 contains entries for failed logons.
      Activities in the central XI system:
      Determine the sending port from the IDoc control record of the IDoc. If the ID of the sending system has the value "ABC", the value of the sending port is "SAPABC". You will find the RFC destination used for the "SAPABC" sending port with the lowest client in Transaction IDX1. In Transaction SM59, you will find the RFC destination containing the maintained logon data .
User does not have the required authorizations
Activities in the sender system ABC:
      In Transaction SM21, you will find entries relating to authorization problems and more exact details.
      Contact your system administrator and, if necessary, assign the user the required roles in user administration.
IDoctyp/Cimtyp cannot be loaded
Activities in sender system ABC:
      In the sender system, you can check your IDoc types in Transaction WE30 (IDoc type editor) Take note not only of the errors, but also of the warnings.
      The most common errors are:
      - IDoc type or segments not released
      - Segments that no longer exist are listed in the IDoc type
      - Data elements that do not exist in the DDIC are assigned to fields
        in the segment.
      Contact your system administrator and correct these errors in the IDoc type.

Error in call adapter: Sequence already terminated

Hi sdn experts
We get the com.sap.engine.interfaces.messaging.api.exception.MessagingException: Sequence already terminated error when sending data from PI to the JMS adapter. The error occurs in the step u201Ccall adapteru201D on the abap-stack.
We have been through logs and found no more info than the ones above.
The scenario is backend (proxy) -> PI -> JMS adapter.
We use EOIO in the proxy call by lo_prxy_async_messaging->set_serialization_context. If we change this to another value by debugging the message goes through.
I have checked sdn posts - but I could not find one that solved my problem.
Any experience on this issue?

Hi Aashish Sinha
Thank you for your input
1) Duplicate Message: Not the case (canelled all in both IS and AE, send again with same result)
2) Invalid parameters: Can you be more specific?
3) Payload or Message Format: It is correct - the samme message runs through when changing the serialization_context. That is.. when changing the eioi sequense id in debug. Same message and format is succesfull then.
To my mind the EOIO id in the j2ee stack got mixed up. I do not know where to check this. I have checked for locks in the NWA. There are none.
Kind Regards
Martin

Error in SXMB_MONI for Idoc to File Scenario (missing of field plant

Hi SapAll.
here i have got a tricky situation where in a Idoc(Matmas.Matmas05) to file Interface thorugh XI there is an error message raising in sxmb_moni.
to get the conclusion for this error i just copied the message from Sxmb_moni and tried with Message mapping in Design by just pasting there,after all this process iam getting the error message as below
Cannot produce target element /MT_FCI_MATERIAL/fcidataimport/objects/object/extensions/collection[3]/row/fields/PLANTEXT. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd
When i go the mapping program it is defined as
if Matmas.matmas05WERKS(sender) exists then map werks to plant tex(reciver MType)t else map constant with(null value) to reciever(MType).
and the important thing is the here the occurance of field plant text is 1.1.
so iam not sure on why the error was raised in message mapping as every thing is fine.
can any body help in slolving this.
regards.
Varma

if Matmas.matmas05WERKS(sender) exists then map werks to plant tex(reciver MType)t else map constant with(null value) to reciever(MType).
When WERKS's is absent the IF doesn't have a value and hence the whole context gets suppressed which returns the error. What you have configured would work fine if WERKS is there but with no value. Here the case is a bit different. WERKS itself is not coming. Your logic doesn't handle that. Hope you got what I intend to convey.
Correct me if I am wrong but the logic is you need to pass WERKS value to PLANTTEXT if value comes else map a blank constant...right??
If so, why not just use mapWithDefault
WERKS -> mapWithDefault(blank contant) -> PLANTTEXT
This way if WERKS comes teh value would be passed, if comes with blank value blank value would eb passed if doesn't come atall, even then a blank value would be passed.
Regards
Soumen...

TMS error: "Offline Call could not access file as supposed (see.."

i am running an NSP Netweaver on top of Windows 7. when performing RSTPTEST, I get the following error, right at the end. All the other tests are fine.
It looks like an permissions problem with possibly the file system, but i have tried giving all to all.
I have been trying for days to fix this.
if anyone can help, please do.
i have checked log files, and about the only useful one is the SLOG1019 which gives me one line
FATAL No stdout redirectio NSP 0000 20100510080609 BCUSER pc
when i try to distribute the TMS i also get "Transport control program tp ended with error code 0212" again, looks like an authorization error.
i am not a basis person, more developer.
any pointers and help, cheers
Edited by: gingle on May 10, 2010 8:13 AM

Hi gingle,
Meaning of returncode 212 is:
could not access file as supposed (see SLOG for more details)
Is there any error in the corresponding SLOG?
You can find the SLOGxxxx.<SID> under usr/sap/trans/log.
Best Regards
Julia

Error while calling an external javascript file

Hi,
I have added a javascript file into the public_html folder, i have named it main.js.
I have a html file in which i am referring to the javascript externally , this too is in my public_html folder. But the HTML page does not seem to be able to invoke the javascript.It does not even enter the method.
My code is as follows
html file
<head>
<title>untitled1</title>
<script language="Javascript" src=\"\main.js\" type=\"text/javascript\"></SCRIPT>
</head>
<body>
<form name="test" method="POST" action="test">
<input type="button" value="submit" name="submit" onclick="analyze_page()">
</form>
</body>
</head>
main.js
<script language="Javascript">
function analyze_page(){
alert("testing if it works");
</script>
(2)
Secondly, I also have a servlet in a package com.oracle.prod, what is the path I should give in the servlet <SCRIPT> tag so that the javascript is accessible while the page gets rendered

Hi Kart,
Try to do:
<script language="Javascript" src="<c:out value="${pageContext.request.contextPath}"/>main.js" type="text/javascript"></SCRIPT>
In that way you can access the context path of your application.
So, another thing that I noted is \" it's unecessary if you are editing directly a jsp/html file.
Afonso

Error in calling servelt from html file

Hi All,
In my application
Servlet class looks like this:
import java.io.IOException;
import java.io.PrintWriter;
import java.util.Iterator;
import java.util.List;
import javax.servlet.ServletException;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
public class SelectBeer extends HttpServlet {
     public void doPost(HttpServletRequest request, HttpServletResponse response)throws ServletException, IOException {
     response.setContentType("text/html");
     PrintWriter out =response.getWriter();
     out.println("Beer Selection Advice<br>");
     String c= request.getParameter("color");
     out.println("<br>Got beer color"+ c);
     BeerExpert be = new BeerExpert();
     List list=be.getBrands("amber");
     Iterator it = list.iterator();
     while(it.hasNext()){
          out.print("<br>try:"+it.next());
}The XML file as follow:
<?xml version="1.0" encoding="ISO-8859-1"?>
<web-app version="2.5"
     xmlns="http://java.sun.com/xml/ns/javaee"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
     http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd">
<servlet>
    <description>This is the description of my J2EE component</description>
    <display-name>This is the display name of my J2EE component</display-name>
    <servlet-name>HelloWorld</servlet-name>
    <servlet-class>HelloWorld</servlet-class>
</servlet>
<servlet>
    <description>This is the description of my J2EE component</description>
    <display-name>This is the display name of my J2EE component</display-name>
    <servlet-name>SelectBeer</servlet-name>
    <servlet-class>Test/SelectBeer</servlet-class>
</servlet>
<servlet-mapping>
    <servlet-name>HelloWorld</servlet-name>
    <url-pattern>/servlet/HelloWorld</url-pattern>
</servlet-mapping>
<servlet-mapping>
    <servlet-name>SelectBeer</servlet-name>
    <url-pattern>SelectBeer</url-pattern>
</servlet-mapping>
<welcome-file-list>
    <welcome-file>index.jsp</welcome-file>
</welcome-file-list>
</web-app>The html file as follow:
<html><body>
<h1 align="center">Beer Selection Page</h1>
<form method="POST"action="Test/SelectBeer">
     Select beer characteristics<p>
     Color:
     <select name="color" size="1">
          <option>light
          <option>amber
          <option>brown
          <option>dark
     <select>
     <br><br>
     <center>
          <input type="SUBMIT">
     <center>
     </form></body></html>but after running the form.html i am geeting Selelctbeer is unavailable?
Could you please explaing if i am missing anything?
Regards,
Divya

hi,
make sure that the class is in the package TEST.
manik;

Error in Call Adapter (IDOC- XI- FILE)

Similar Messages

Maybe you are looking for