ABAP Proxy guide?

Dear all
i am a ABAPer,as abap mapping is done, i am about to test ABAP proxy,
my XI have two client(100, 200) for proxy.
but it is not easy to understand ABAP proxy for me,
even though i've read relevant to ABAP proxy on this site. and i could not follow this.
so is there a sample guide document by step by step?
i will highly be appreciated in advance.
thank you
Y.D

3. Proxies :
Proxies are used for connecting to SAP systems.....
when you design new integration scenarios in SAP systems which are based on Web AS 6.20 or higher.
Proxies support both Synchronous and Async. Connectivity.
and for inbound interfaces are called server proxies.
Prerequisties foe abap proxies:
-register queues in sxmb_adm.
-HTTP destination on SAP system (on which proxy is developed) pointing to XI
system.
- configure your SAP system to act as IE using SXMB_ADM transaction.
>>what are proxies used for and how good they are..
http://help.sap.com/saphelp_nw04/helpdata/en/86/58cd3b11571962e10000000a11402f/content.htm
Refer to these links :
http://help.sap.com/saphelp_nw04/helpdata/en/02/265c3cf311070ae10000000a114084/frameset.htm
abap:
/people/prateek.shah/blog/2005/06/14/file-to-r3-via-abap-proxy
/people/siva.maranani/blog/2005/05/23/communication-between-sap-system-webservice-using-proxies
/people/siva.maranani/blog/2005/04/03/abap-server-proxies
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
regards..
vishal

Similar Messages

Can ABAP proxy to consume WSDL file be run as background job for every10min

Hi all,
I have a requirement where I need to build an interface which gatheru2019s the purchase order details and send to external third party software in their required format (as an XML file).
So I should be the first point of contact and should trigger the interface each time a purchase order is generated.
So I am thinking that I should develop a background job for every 10 minutes which will look for new purchase orders and gathers the information of the purchase orders and send them to external third party software in their required format.
I have gone through all the SAP forums and e-Learning but still I have confusion in regards to how is it possible technically? Can some one guide me with some information on the same.
I have a little bit of confusion and want to know few things.
1)     Should I create a web service or should I consume a web service?
2)     If I need to consume a web service, then can I write an ABAP proxy to be run in background fro evry 10 minutes? I mean can we run ABAP proxy as a batch job in the background?
3)     Is there a difference between consuming an XML file and WSDL File?
Any Help will be highly appreciated.
Regards,
Jessica.

There are two options (as I know) to generate XML file.
1. Use XML TRANSFORMATION to get the XML string based your TRANSFORMATION. You can input your data and get back the XML string. Download this string to a file
Test XML generation program is:
types: begin of ty_data,
       num   type i,
       end   of ty_data.
DATA: itab TYPE standard table of ty_Data,
      la_data like line of itab,
      xmlstr TYPE string.
DO 3 TIMES.
la_data-num = sy-index.
APPEND la_data TO itab.
ENDDO.
CALL TRANSFORMATION ztest_np1
SOURCE table = itab
RESULT XML xmlstr.
CALL FUNCTION 'DISPLAY_XML_STRING'
EXPORTING xml_string = xmlstr.
My ZTEST_NP1 transformation. To create a transformation, click on the transformation in the "CALL TRANSFORMATION ztest_np1" statement. Select Simple transformation type.
<?sap.transform simple?>
<tt:transform xmlns:tt="http://www.sap.com/transformation-templates">
<tt:root name="table"/>
<tt:template>
    <table>
      <tt:loop ref=".table">
        <item>
          <tt:value ref="NUM"/>
        </item>
      </tt:loop>
    </table>
</tt:template>
</tt:transform>
XML string is like:
<?xml version="1.0" encoding="utf-8" ?>
<table>
<item>1</item>
<item>2</item>
<item>3</item>
</table>
To use this option, you have to create a transformation and than use it to generate the XML string.
Check this SAP Help
http://help.sap.com/saphelp_nw04s/helpdata/en/e3/7d4719ca581441b6841f1054ff1326/frameset.htm
2. You can concatenate and create an XML string and download that string into a file.
Regards,
Naimesh Patel

ABAP Proxy Doesnt work in PI 7.0

Hi All,
We have strange problem with ABAP Proxy under PI system
We are getting proxy communication error in PI 7.0 (NOT FROM Business system).
After reading a lot of threads & notes, I performed all the necessary checks, but still no luck.
--> When I click on integration builder from SPROXY T-code it popups correct XI Screen
--> Following parameters are maintained properly
com.sap.aii.connect.repository.name: Server (for example, pwdf0436)
com.sap.aii.connect.repository.httpport: Port (for example, 1080)
com.sap.aii.connect.repository.contextroot: Root (for example, rep)
com.sap.aii.applicationsystem.serviceuser.name: User
com.sap.aii.applicationsystem.serviceuser.pwd: Password
--> All the RFC like AI_RUNTIME_<SID>, LCRSAPRFC & SAPSLDAPI & SLD_UC etc working fine
Following reports are NOT working
SPROX_CHECK_IFR_ADDRESS
SPROX_CHECK_IFR_RESPONSE
SPROX_CHECK_IFR_CONNECTION
Following report execute SUCCESSFULLY
SPROX_CHECK_HTTP_COMMUNICATION
Thanks in advance

Hi Rakesh,
Has the ABAP system been configured as specified in the XI configuration guide (Section on how to configure a business system)?
This would include Integration Engine Configuration in transaction SXMB_ADM, configuration in transaction SLDAPICUST and RFC destinations in SM59.

SOAP error in synchronous scenario for ABAP Proxy with Oracle D/B

Dear Experts,
I am working in Sender ABAP Proxy <====>SAP PI 7.31 JAVA only <====> Oracle Database. My proxy configuration are working successfully.
Apart from that, I have maintained a SOAP sender communication channel under the ECC business system with
Transport Protocol as HTTP
Message Protocol as XI 3.0
Adapter Engine as Central Engine
When I am testing from ECC at Tx SPROXY, I am receiving following error.
com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.adapter.xi.routing.RoutingException: InterfaceDetermination did not yield any actual interface at com.sap.aii.adapter.soap.web.SOAPHandler.processSOAPtoXMB(SOAPHandler.java:746) at com.sap.aii.adapter.soap.web.MessageServlet.doPost(MessageServlet.java:505) at javax.servlet.http.HttpServlet.service(HttpServlet.java:754) at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) at
1. In XI3.0 protocol, I can not select BE but when selected HTTP 1.0 as Message protocol then I can find the BE.
2. No Response message is shown in ECC when testing the message.
3. How do Receiver JDBC adapter for Oracle Database is configured
4. What would be Message Protocol for Oracle Database i.e. XML SQL Format or Native SQL format for Select operation.
Please guide.. All your inputs will be appreciated......
Regards
Rebecca

Dear Indrajit,
Appreciate your inputs.. Yes I have configured all the ABAP proxy configurations and there no question of missing any thing as Tx SLDCHECK in ECC is working perfectly fine.
But still to go, some of the queries needs more input.
1.In ID, i have created a Sender SOAP communication channel with listed details.
Transport Protocol as HTTP
Message Protocol as XI 3.0
Adapter Engine as Central Engine
Is there any parameters which I may be missing from Module tab of Synchronous SOAP Cc ?
2. In the Cc monitoring, the JDBC receiver status shows "Database operation successfully completed" but I could not find any response data from database. The Message monitoring should have 2 messages for 1 trigger, but I could find only 1 message by SOAP only?
Sorry to bother experts...Please answer in sequence...
Regards
Rebecca

IDOC to abap proxy- Receiver Service Cannot be converted into ALE logical

Dear all,
I have idoc to abap proxy -
R3 to SRM scenario.
I am getting the error Receiver service cannot be converted to ale logical system.
I have check the receiver bs SRM_BS , adapter specific attributes ... im getting the logical system ( this is not the problem)
i am using receiver XI adapter
with XI 3.0 as protocol
and http destination with /sap/xi/engine?type = receiver
i can see the data in the moni of receiver SRM system but it shows a red flag
pls help

Hi kiran,
i have checked all the RFC destinations ... seems OK
problem is in SRM moni .. sender service and sender interface are not visible.
trace ::::
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
- 
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine/?type=entry</Trace>
<Trace level="1" type="T">COMMIT is done by XMB !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- 
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="1" type="T">system-ID = SR5</Trace>
<Trace level="1" type="T">client = 300</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = RFCADMIN_SR5</Trace>
<Trace level="1" type="Timestamp">2008-06-01T16:27:03Z CET</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- 
<Trace level="1" type="T">Message-GUID = DD2FF717DAE395F186DF001560A1C7CB</Trace>
<Trace level="1" type="T">PLNAME = RECEIVER</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline = RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Get definition of internal pipeline = SAP_RECEIVER</Trace>
<Trace level="1" type="T">Queue name : XBTR0003</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTR0003</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface *</Trace>
<Trace level="1" type="T">select interface namespace</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--start receiver interface action determination</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface SupplierPortalTradingPartner_CreateOrChange_In*</Trace>
<Trace level="1" type="T">select interface namespace http://sap.com/xi/SRM/SupplierEnablement</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline RECEIVER</Trace>
<Trace level="1" type="T">system-ID = SR5</Trace>
<Trace level="1" type="T">client = 300</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = RFCADMIN_SR5</Trace>
<Trace level="1" type="Timestamp">2008-06-01T16:27:04Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
<Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
- 
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
<Trace level="1" type="B" name="Inbound Framework" />
- 
- <asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
- <asx:values>
<CX_ERROR href="#o3314" />
</asx:values>
- <asx:heap xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:abap="http://www.sap.com/abapxml/types/built-in" xmlns:cls="http://www.sap.com/abapxml/classes/global" xmlns:dic="http://www.sap.com/abapxml/types/dictionary">
- <cls:CX_SY_NO_HANDLER id="o3314">
- <CX_ROOT>
<TEXTID>1F09B73915F6B645E10000000A11447B</TEXTID>
<PREVIOUS href="#o3313" />
<KERNEL_ERRID>UNCAUGHT_EXCEPTION</KERNEL_ERRID>
- <INTERNAL_SOURCE_POS>
<PROGID>496</PROGID>
<CONTID>1564</CONTID>
</INTERNAL_SOURCE_POS>
</CX_ROOT>
<CX_NO_CHECK />
- <CX_SY_NO_HANDLER>
<CLASSNAME>CX_BBPX1_STD_MESSAGE_FAULT</CLASSNAME>
</CX_SY_NO_HANDLER>
</cls:CX_SY_NO_HANDLER>
- <cls:CX_BBPX1_STD_MESSAGE_FAULT id="o3313">
- <CX_ROOT>
<TEXTID>65B8FEB5F43CC949B7CD662AB888ED34</TEXTID>
<PREVIOUS />
<KERNEL_ERRID />
- <INTERNAL_SOURCE_POS>
<PROGID>496</PROGID>
<CONTID>1738</CONTID>
</INTERNAL_SOURCE_POS>
</CX_ROOT>
<CX_DYNAMIC_CHECK />
<CX_AI_APPLICATION_FAULT />
- <CX_BBPX1_STD_MESSAGE_FAULT>
<AUTOMATIC_RETRY />
<CONTROLLER />
<NO_RETRY />
- <STANDARD>
<CONTROLLER />
<FAULT_TEXT>An error occured within an XI interface: Exception occurredE:BBP_BUPA_SUPPLIER:089 -Unable to determine logical system of sender; check your data Programm: CX_BBP_BD_ERROR===============CP; Include: CX_BBP_BD_ERROR===============CM002; Line: 57</FAULT_TEXT>
<FAULT_URL />
<FAULT_DETAIL />
</STANDARD>
</CX_BBPX1_STD_MESSAGE_FAULT>
</cls:CX_BBPX1_STD_MESSAGE_FAULT>
</asx:heap>
</asx:abap>
</Trace>
<Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
</SAP:Trace>
fault message says the sender is not having logical sys...but my sender sys is showing logical system in adapter specific attributes
pls help
points will be awarded

"SOAP:Fault" in scenario with ABAP proxy client

Hello,
I realized the scenario CRM40_Basis620(ABAP proxy client)->XI->File.
XI:
The sender communication channel is a XI adapter (Parameters: HTTP 1.0, XI 3.0, Integration Server, Security profile unchecked, Security level - HTTP).
CRM:
The proxy generation is ok.
SLDCHECK is ok.
All RFC destinations are ok.
APPINT_200_620 for CRM was installed and configured well (I think so, but...).
When I ran the ABAP proxy client on CRM, sxmb_moni(CRM) returned the text for the XML Message (Display-CallIntegrationServer-Payloads-TraceDocument):
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <SAP:TraceHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="1" type="T">system-ID = EST</Trace>
<Trace level="1" type="T">client = 300</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = BABKIN_RA</Trace>
<Trace level="1" type="Timestamp">2007-08-06T13:55:12Z</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- 
<Trace level="1" type="T">Message-GUID = DC4424A659314CF18F500002A541D0E7</Trace>
<Trace level="1" type="T">PLNAME = SENDER</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline = SENDER</Trace>
<Trace level="1" type="T">Get definition of internal pipeline = SAP_SENDER</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTS0004</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message + call qRFC now...</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline SENDER</Trace>
<Trace level="1" type="T">system-ID = EST</Trace>
<Trace level="1" type="T">client = 300</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = BABKIN_RA</Trace>
<Trace level="1" type="Timestamp">2007-08-06T13:55:12Z</Trace>
<Trace level="1" type="T">----
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC">
<Trace level="1" type="T">Get definition of pipeline PID= SENDER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
- <Trace level="1" type="B" name="PLSRV_CALL_INTEGRATION_SERVER">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
- <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-ENTER_PLSRV">
<Trace level="1" type="T">URL for integration server read from global configuration</Trace>
<Trace level="1" type="T">URL= http://SRMDEV.oao.sng:8011/sap/xi/engine?type=entry</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_TECHNICAL_ROUTING_PROPERTY" />
- <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">
<Trace level="1" type="System_Error">HTTP-client: error response= <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"> <SOAP:Header> </SOAP:Header> <SOAP:Body> <SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"><faultcode>SOAP:Client</faultcode><faultstring>Error during conversion of XI message</faultstring><faultactor>http://sap.com/xi/XI/Message/30</faultactor><detail><SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:Category>XIServer</SAP:Category><SAP:Code area="SECURITY">INBOUND_SECURE_LEVEL</SAP:Code><SAP:P1>DC4424A659314CF18F500002A541D0E7</SAP:P1><SAP:P2/><SAP:P3>HTTP</SAP:P3><SAP:P4/><SAP:AdditionalText/><SAP:ApplicationFaultMessage namespace=""/><SAP:Stack>Message DC4424A659314CF18F500002A541D0E7 was sent with ''. Channel configuration, however, requires 'HTTP' </SAP:Stack></SAP:Error></detail></SOAP:Fault> </SOAP:Body> </SOAP:Envelope></Trace>
</Trace>
<Trace level="1" type="System_Error">Exit XMB because of system error!</Trace>
<Trace level="1" type="System_Error">System-Error: HTTP.HTTP_STATUS_CODE_NEQ_OK</Trace>
<Trace level="1" type="System_Error">HTTP status code 500 : Error during conversion of XI message</Trace>
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
</SAP:TraceHeader>
I think the main problem is the parameter "HTTP Security level" for the channel, but not sure.
Does anybody know where to find a solution?
Regards,
Roman

Hi Roman
There is no need for an XI adapter for client proxy.... we only use that for server proxies.
Vaibhav

ABAP Proxy Exception

Hello everybody i have this error in my sxmb_moni of xi for a abap proxy server receiver:
<?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>XIProxy</SAP:Category>
<SAP:Code area="ABAP">DYNAMIC_CALL_FAILURE</SAP:Code>
<SAP:P1>UNCAUGHT_EXCEPTION</SAP:P1>
<SAP:P2>ZFUS_CL_MI_FMGOB_CAT_FONDOS_C1</SAP:P2>
<SAP:P3>EXECUTE_SYNCHRONOUS</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText>Unable to execute the dynamic application call (kernel error ID UNCAUGHT_EXCEPTION, class ZFUS_CL_MI_FMGOB_CAT_FONDOS_C1, method EXECUTE_SYNCHRONOUS)</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
any suggestions?
Regards,
Julio Cesar

Hi
Below is the full details of above links
For link 4196517?
Q) Hi All,
I have got a requirement to raise an exception from existing ABAP Proxy depending on condition. XI consultant created a fault messge type and attached to the inbound interface message type. I have regenerated the ABAP proxy but I cant find any thing in excpetion tab to raise exception.
Please let me know the solution for this.
Answers : 1) Go to Sproxy .
Select the message interface for which you generated the proxy.
Click on the Structure tab. Do you see any Exception Class generated for fault message ?
2) Just follow all the steps defined in the below Blog and you will find the solution.
/people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1
3) I can't find any exception class there in 'Structure' tab. what might be the problem.
4) In SProxy ..under the Message Interface you will see Fault Message Type.
Click on Fault Message Type and check if you can see the fault message type created by xi consultant.
Also ask your xi team to login to IR and re-activate the interface.
5) I can't find any fault message type under Fault Message Type. I will ask my XI consultant to reactivate the interface.
Is this the only problem for this or is htere any other reason for not finding this fault message type in SPROXY.
6) Ideally the fault message type should be visible unless he has defined Software Dependencies and using MT from some other SC.
Even if the fault message type is not visible everything could be all right.
Ask him to check if he selected the fault message type while activating the interface.
Do update us when you get a reply from ur xi team.
7) I have checked with XI admin, he said that he created fault message types in Development Xi but R/3 Development refers to Production XI system in exchange profiles. He asked me to change it to XI development in exhange profile settings. So I am searching info on how to set exchange profiles.
8) The following link will guide you ..
http://help.sap.com/saphelp_nw04s/helpdata/en/c9/7a1041ebf0f06fe10000000a1550b0/frameset.htm
I dont think we need to do any changes in Exchange Profile for proxy communication.
Changing the RFC Destinations (in your R/3 system)- LCRSAPRFC & SAPSLDAPI should solve your problem.
II) For Link :4147406?
Q) Hi All,
We have an ABAP Proxy implemented for posting goods movement and it is calling BAPI function module to post good movement. We have got a requirement that if BAPI returns any error, this error message send back to SAP XI.
data call proxy
Legacy -
> XI -
> SAP R/3(call bapi)
<----
error message
Please let me know how to send the message back to XI.
Answers: 1) Refer the following
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy - ABAP Proxy to File
/people/prateek.shah/blog/2005/06/14/file-to-r3-via-abap-proxy - File to ABAP Proxy
2) you can utilize the fault messages for such an usage -
Ref:
Fault messages -
/people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1
Handling Web Service SOAP Fault Responses in SAP NetWeaver XI -
/people/jin.shin/blog/2007/05/21/handling-web-service-soap-fault-responses-in-sap-netweaver-xi
3) You have to do Fault message implementation in this case...
A no. of exception will be there.For any error proxy will catch the exception and will write it in the fault message...so....from r/3 response will go to Xi as Fault message response in case any error/exception occours......
have look here...
Fault message implementation.
/people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1
4) Please go through it is very useful.
/people/krishna.moorthyp/blog/2005/12/23/monitoring-for-processed-xml-messages-in-abap-proxy --Monitoring for Processed XML messages in ABAP Proxy
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy --ABAP Proxies in XI(Client Proxy)
/people/sap.user72/blog/2005/12/29/service-enable-your-sap-application-component --- Service Enable Your SAP Application Component
5) the file adapter can work only asynchronous, so you cant have a response. You should build two asynchronous messages. File -> proxy inbound and after the bapi call an outbound proxy is called which is sending a second messge to the file adapter.
6) you can define a synchronous scenario which will include request/response messages.
send the response back to XI.
the file adapter supports BE QoS.
http://help.sap.com/saphelp_nw04s/helpdata/en/0d/5ab43b274a960de10000000a114084/frameset.htm
7)I have an interface Z_stock_move(message interface(inbound)) and class z_STOCK_MOVE in that. I have clicked exception tab but not able to add exception there as its not enabled for change.
Please let me know how to add the exception to an existing abap proxy.so that i can raise an exception when bapi call to goods movenment returns errors.
Might be useful to U.

ABAP Proxy Import Structure

ok. Guys and gals I have limited ABAP expierence and have a simple question around loops. I have an ABAP proxy setup that receives an XML file and stores the contents in the INPUT method. The two structures under Item I am working with are I_HEADER and I_ITEM.
I can access the values in I_HEADER with something like the following:
CLEAR w_header.
w_header-guid = v_header_guid.
w_header-description = input-I_HEADER-DESCRIPTION.
w_header-process_type = input-I_HEADER-PROCESS_TYPE.
w_header-posting_date = sy-datum.
now I currently have been testing the proxy with the following for my i_item structure. This is hard coded but I would like to import from the INPUT structure.
CLEAR w_item.
w_item-guid = v_item_guid.
w_item-parent = v_header_guid.
w_item-product = '00000000000000000000000000000000'.
w_item-description = 'Test Item Description'.
APPEND w_item TO i_item.
How would I setup my loop to read the I_ITEM-ITEM table and populate with the imported values instead of hard coded. For instance using this example I would need the values from I_ITEM-ITEM-DESCRIPTION and I_ITEM-ITEM-PRODUCT?
Thank You.

Hi Joe,
You have to use to loops one for header and another for Item details in that header something like this
loop at it_header into wa_header
loop at it_item into wa_tem
endloop.
endloop.

Abap proxy call failed

Hi,
I am trying to call (synchronous mode) from XI 3.0 an ABAP proxy located on a R3 enterprise 4.7 ext 2.00 server.
Unfortunately, when I send the request message with the XI Adapter to the local integration engine using message protocol 2.0,
an error occured on the R3 system:
PROTOCOL.LOOP_IN_MESSAGE_ROUTING
<SAP:ErrorHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
               <SAP:Context></SAP:Context>
               <SAP:Code p1="is.00.hermes" p2="IS" p3="XI" p4="">PROTOCOL.LOOP_IN_MESSAGE_ROUTING</SAP:Code>
               <SAP:Text language="EN"></SAP:Text>
            </SAP:ErrorHeader>
            <SAP:HopList xmlns:SAP="http://sap.com/exchange/MessageFormat" Version="1.0">
               <SAP:Hop SystemName="is.00.hermes" Type="CENTRAL" TimeStamp="2005-08-04T18:11:25Z" WasRead="0">
                  <SAP:MessageInbound>
                     <SAP:Type></SAP:Type>
                     <SAP:AdapterRefId>3.0</SAP:AdapterRefId>
                     <SAP:MessageId>2B1B2E10-0513-11DA-A979-0013216B8075</SAP:MessageId>
                  </SAP:MessageInbound>
                  <SAP:MessageOutbound>
                     <SAP:Type>IENGINE</SAP:Type>
                     <SAP:AdapterRefId>3.0</SAP:AdapterRefId>
                     <SAP:MessageId>2B1B2E10-0513-11DA-A979-0013216B8075</SAP:MessageId>
                  </SAP:MessageOutbound>
               </SAP:Hop>
               <SAP:Hop SystemName="is.00.hermes" Type="CENTRAL" TimeStamp="2005-08-04T18:11:25Z" WasRead="0">
                  <SAP:MessageInbound>
                     <SAP:Type>IENGINE</SAP:Type>
                     <SAP:AdapterRefId>3.0</SAP:AdapterRefId>
                     <SAP:MessageId>2B1B2E10-0513-11DA-A979-0013216B8075</SAP:MessageId>
                  </SAP:MessageInbound>
                  <SAP:MessageOutbound>
                     <SAP:Type></SAP:Type>
                     <SAP:MessageId>2B1B2E10-0513-11DA-A979-0013216B8075</SAP:MessageId>
                  </SAP:MessageOutbound>
               </SAP:Hop>
               <SAP:Hop SystemName="UPG" Type="RECEIVER" TimeStamp="2005-08-04T18:11:25Z" WasRead="0">
                  <SAP:MessageInbound>
                     <SAP:Type>IENGINE</SAP:Type>
                     <SAP:AdapterRefId>2.0</SAP:AdapterRefId>
                     <SAP:MessageId>2B1B2E10-0513-11DA-A979-0013216B8075</SAP:MessageId>
                  </SAP:MessageInbound>
                  <SAP:MessageOutbound>
                     <SAP:Type>PROXY</SAP:Type>
                     <SAP:MessageId>2B1B2E10-0513-11DA-A979-0013216B8075</SAP:MessageId>
                  </SAP:MessageOutbound>
               </SAP:Hop>
            </SAP:HopList>
            <SAP:MessageHeader xmlns:SAP="http://sap.com/exchange/MessageFormat" version="1.0" SOAP:mustUnderstand="1">
               <SAP:From>
                  <SAP:Name>WebServer</SAP:Name>
                  <SAP:Interface namespace="http://adixen.fr/test">DataUserQuery_out</SAP:Interface>
               </SAP:From>
               <SAP:To>
                  <SAP:Name>UPG</SAP:Name>
                  <SAP:Interface namespace="http://adixen.fr/test">DataUserQuery_in</SAP:Interface>
               </SAP:To>
               <SAP:MessageId>2B1B2E10-0513-11DA-A979-0013216B8075</SAP:MessageId>
               <SAP:QualityOfService>BestEffort</SAP:QualityOfService>
               <SAP:TimeSent>2005-08-04T18:11:24Z</SAP:TimeSent>
               <SAP:Direction>Response</SAP:Direction>
               <SAP:Document></SAP:Document>
            </SAP:MessageHeader>
            <SAP:InternalAttributesHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
               <SAP:AdapterInbound>PROXY</SAP:AdapterInbound>
               <SAP:AdapterOutbound>IENGINE</SAP:AdapterOutbound>
            </SAP:InternalAttributesHeader>
         </SOAP:Header>
         <SOAP:Body xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
            <SAP:Manifest xmlns:SAP="http://sap.com/exchange/MessageFormat" xmlns:xlink="http://www.w3.org/1999/xlink" version="1.0">
               <SAP:Payload xlink:href="cid:[email protected]">
                  <SAP:Document>TraceDocument</SAP:Document>
               </SAP:Payload>
            </SAP:Manifest>
         </SOAP:Body>
      </SOAP:Envelope>--SAP_41F726EA34ED2F498C6BA328BAB08C43_ENDcontent-type:text/plaincontent-length:2912content-id:[email protected]
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
         <SAP:TraceHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
            <Trace level="1" type="B">CL_XMS_TROUBLESHOOT-ENTER_PLSRV</Trace>
            <Trace level="1" type="E">CL_XMS_TROUBLESHOOT-ENTER_PLSRV</Trace>
            <Trace level="1" type="T">**************************************************** </Trace>
            <Trace level="1" type="T">*                                                  * </Trace>
            <Trace level="1" type="T">*                                                  * </Trace>
            <Trace level="1" type="T">XMB entry processing </Trace>
            <Trace level="1" type="T">system-ID = UPG</Trace>
            <Trace level="1" type="T">client = 100</Trace>
            <Trace level="1" type="T">language = E</Trace>
            <Trace level="1" type="T">user = YLEBLEVEC</Trace>
            <Trace level="1" type="Timestamp">2005-08-04T18:11:25Z </Trace>
            <Trace level="1" type="T">*                                                  * </Trace>
            <Trace level="1" type="T">*                                                  * </Trace>
            <Trace level="1" type="T">**************************************************** </Trace>
            <Trace level="1" type="B">CL_XMS_MAIN-CALL_UC_EXECUTE</Trace>
            <Trace level="1" type="T">Message-GUID = 2B1B2E10051311DAA9790013216B8075</Trace>
            <Trace level="1" type="T">PLNAME = SENDER</Trace>
            <Trace level="1" type="T">QOS = BE</Trace>
            <Trace level="1" type="B">CL_XMS_MAIN-CALL_PIPELINE_SYNC</Trace>
            <Trace level="1" type="T">Get definition of pipeline PID= SENDER</Trace>
            <Trace level="1" type="B">CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST</Trace>
            <Trace level="1" type="E">CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST</Trace>
            <Trace level="1" type="B">PLSRV_CALL_INTEGRATION_SERVER</Trace>
            <Trace level="1" type="B">CL_XMS_MAIN-CALL_PLSRV</Trace>
            <Trace level="1" type="B">CL_XMS_MAIN-CALL_PLSRV_LOCAL</Trace>
            <Trace level="1" type="B">CL_XMS_PLSRV_CALL_XMB-ENTER_PLSRV</Trace>
            <Trace level="1" type="T">URL for integration server read from global configuration </Trace>
            <Trace level="1" type="T">URL= dest://INTEGRATION_SERVEUR</Trace>
            <Trace level="1" type="B">CL_XMS_MAIN-SET_TECHNICAL_ROUTING_PROPERTY</Trace>
            <Trace level="1" type="E">CL_XMS_MAIN-SET_TECHNICAL_ROUTING_PROPERTY</Trace>
            <Trace level="1" type="B">CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP</Trace>
            <Trace level="1" type="E">CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP</Trace>
            <Trace level="1" type="E">CL_XMS_PLSRV_CALL_XMB-ENTER_PLSRV</Trace>
            <Trace level="1" type="E">PLSRV_CALL_INTEGRATION_SERVER</Trace>
            <Trace level="1" type="E">CL_XMS_MAIN-CALL_PIPELINE_SYNC</Trace>
            <Trace level="1" type="B">CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST</Trace>
            <Trace level="1" type="E">CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST</Trace>
            <Trace level="1" type="E">CL_XMS_MAIN-CALL_UC_EXECUTE</Trace>
            <Trace level="1" type="E">CL_XMS_MAIN-ENTER_XMS</Trace>
            <Trace level="1" type="E">CL_XMS_HTTP_HANDLER-HANDLE_REQUEST</Trace>
         </SAP:TraceHeader>SAP_41F726EA34ED2F498C6BA328BAB08C43_END
I guess the error occurs before the call of my proxy. Can anyone help?
Thanks,
Yann

Hi,
>>>However to be able to process XML messages on 'UPG' I need to activate the service '/default-host/sap/xi/engine'. This service start my local integration engine, correct?
I thought you tried to send messsages from the same WAS local can be set on every client - the same as R3 - right
further reference (XI configuration guide):
<b>Connecting Business Systems with an Integration Engine to the Central Integration Server</b> <-- you have to do all of those steps on your R/3 (SLD, SICF, SXMB_ADM etc.)
>>>>Last question do I need to have 2 different clients on UPG, the one for my local integration engine and the other one for my ABAP proxies? Can they be on the same client?
yes you can send proxies (from r3) to XI from the same client as your R3 system (application system)
no need for a second client on R3 side:)
sorry if I confused you with my response
Regards,
michal
Message was edited by: Michal Krawczyk

Configure ABAP Proxy scenario in PI7.3

Hello Experts,
Can someone please let me know if we have somewhere step by step procedure to configure an ABAP Proxy scenario in PI7.3, I couldn't find How-to guide related to this on SDN.
Thanks a lot.
Best Regards,
Shweta

I dont know abt your installation whether you have java stack alone or both java stack and abap stack.
AAE or local processing:
You can do using soap adapter as transport protocol and message protocol as XI for proxy. This way you can use local processing using AAE. I dont see documents in SDN as of now. But it is pretty simple. Just follow the steps what I mentioned.
Classical processing or abap engine:
Still the same as previous versions.

ABAP Proxy config between PI 7.1 and WAS 6.20

Hi guys,
I'm configuring the Proxy runtime between a PI 7.1 and WAS 6.20 and I'm getting errors at the two last tests of sproxy -> I'm getting - Integration Builder data not understood.
I checked the following:
Everything in sldcheck is ok.
Integration engine configuration as appl sys (LOC).
HTTP connection to IB ok.
No user locked.
SICF services all activated.
The BASIS content imported at PI is 7.10.
Do you know what I'm missing here? Is it possible to do these configs with these releases?
Thanks in advance,
Ricardo.

Hi Ricardo,
I think your Basis component is at lower level, as it is not allowing to go for proxy communication, however for 6.20 and above add-on is not required:
Check with your basis team the following:
The prerequisites to configuration for ABAP Proxy include: (landscape dependent)
1. The business systems should be based on SAP Web AS 6.20 and SAP Web AS 6.20 kernel patch level above 1253
2. You have installed the XI Add-On in each of these business systems as described in the Installation Guide SAP Exchange Infrastructure 3.0
3. The business systems and your central Integration Server are maintained in the System Landscape Directory (SLD).
Sachin
Edited by: Sachin Dhingra on Mar 12, 2009 6:55 PM

Abap proxy settting in business system side

Hi all;
I am trying to activate abap proxy environment at the business system(640) with the web blog document https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/3022. [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken]
but i am still getting "no connection to integration builder" when SPROXY at the r/3(640).
according to some article, i have to maintain exchangeProfile at the r/3 side, but i could not get into business system with 50000port exchangeProfile, but 8000port is available.
so is it right? i have to maintain exchangeProfile at the business system(r/3).
result of some test is below;
1. sldcheck is no problem. - no problem.
2.Check/maintain with report: SPROX_CHECK_IFR_ADDRESS
3.Check with report SPROX_CHECK_HTTP_COMMUNICATION
4.Check with report SPROX_CHECK_IFR_RESPONSE
5.Check with report SPROX_CHECK_IFR_CONNECTION
number 2, SPROXYSET TABLE is empty value
In Exchange Profile http://sapxi.hh.net:50000/rep
In Table SPROXSET
Status OK: Address maintained
number 3, result
HTTP communication functioning
number 4, i got error "HTTP error(return code 400, message "ICM_HTTP_CONNECTION_FAILED").
number 5, i got error "Integration Builder data not understood"
please guide me in order to activate connection to integration builder.
thanks in advance
venjamin

Hi Venjamin -
Can you confirm a few things first:
1. In SXMB_ADM of R/3 goto Integration Engine Configuration. Is Role set up as Application System and do you have a value for Corresponding Integration Server? If so, please paste that value here.
2. In SM59, for the HTTP destination pointing to your Integration Server, what is the result of your connection test? You should be getting something like "HTTP/1.0 500 Empty HTTP request received" at the top.
3. Also in SM59, do your test connections work for both LCRSAPRFC and SAPSLDAPI?
4. Is your R/3 system a unicode system or non-unicode system? Have the LCRSAPRFC and SAPSLDAPI destinations on both the abap and j2ee side been configured accordingly?
By the way, there is no exchangeProfile for R/3...
Regards,
Jin

ABAP Proxy to XI scenario with no Receiver

Hi,
I am working on a scenario where R/3 sends a request to XI through ABAP Proxy and expects response synchronously. I am calling a UDF Java function within a mapping to get response, so there is no receiver, per se.
Can someone guide me how to map this scenario?
REQUEST_DT: Field1, Field2
RESPONSE_DT : Resp_Field1
Grpahical Mapping: Pass Field1, Field2 to a UDF function which populates Resp_Field1. This Resp_Field1 is sent back to R/3 synchronously for the Request.
I hope someone can help me.
Thanks
Venkat Viswanathan

Hi ,
check these links also...
/people/rashmi.ramalingam2/blog/2005/06/25/an-illustration-of-java-server-proxy
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/a068cf2f-0401-0010-2aa9-f5ae4b2096f9
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f272165e-0401-0010-b4a1-e7eb8903501
sekhar

ABAP Proxy Exception / Fault Message

Hi All,
I have got a requirement to raise an exception from existing ABAP Proxy depending on condition. XI consultant created a fault messge type and attached to the inbound interface message type. I have regenerated the ABAP proxy but I cant find any thing in excpetion tab to raise exception.
Please let me know the solution for this.
reward points are available.
-Venkat

Hi Venkat,
The following link will guide you ..
http://help.sap.com/saphelp_nw04s/helpdata/en/c9/7a1041ebf0f06fe10000000a1550b0/frameset.htm
I dont think we need to do any changes in Exchange Profile for proxy communication.
Changing the RFC Destinations (in your R/3 system)- LCRSAPRFC & SAPSLDAPI should solve your problem.
Regards,
Sumit

How to find contents of ABAP proxy message

we are using an ABAP proxy to send data including a document number from SAP to PI when a document is received on our SAP ERP system.
it is possible under certain conditions that the proxy will not be processed, but the document has. I want to be able to check the messages sent to PI to ensure that all the data has actually created a proxy message. How can I, if it is possible, find the data within the messages so I can determine if the whole process has completed OK.
Put another way how do we know what data is in a message as listed under transaction SXMB_MONI ? The GUID in this transaction appears to relate to table SXMSPMAST but how can I find the information contained within that message so I can then link the message with the original document and then if necessary call the proxy again for that document ?
Colin
Edited by: Colin Heap on Oct 22, 2009 5:16 PM

The problems I mentioned above seem to have been down to the xml messages themsleves rather than the coding found from Ravis' link however I made a few changes to the code to add more flexibility in the search parameter and also a TRY - ENDTRY to deal with the problem of abends when the SAP cannot interpret the message contents.
please refer to the original BLOG ( Super Message Monitor for SAP XI ) by Alessandro Guarneri at the link in Ravis' post.
I have then made the following changes. Please note that the field names used in my code are slighlty different to the original code to fit in with local coding practice however I think it will be easy for a programmer to interpret the changes
1. Selection Screen 850 has been changed to use a SELECT-OPTION for the payload value. In Alessandros' code this is in INCLUDE ZXIMONI_RSXMB_SEL_MSG_SEL.
* Super selection screen -------------------------------------------------- BEGIN
TABLES: idxsndpor, idxrcvpor.
SELECTION-SCREEN BEGIN OF SCREEN 0850 AS SUBSCREEN.
SELECTION-SCREEN COMMENT 5(40) text-S98.
* IDoc
SELECTION-SCREEN BEGIN OF BLOCK idoc WITH FRAME TITLE text-s16.
* Sender
SELECTION-SCREEN BEGIN OF BLOCK idoc_snd WITH FRAME TITLE text-s14.
SELECT-OPTIONS: s_snum FOR idxsndpor-idocnumber NO INTERVALS,
                s_styp FOR idxsndpor-idoctyp    NO INTERVALS.
SELECTION-SCREEN END OF BLOCK idoc_snd.
* Receiver
SELECTION-SCREEN BEGIN OF BLOCK idoc_rcv WITH FRAME TITLE text-s15.
SELECT-OPTIONS: s_rnum FOR idxrcvpor-idocnumber NO INTERVALS,
                s_rtyp FOR idxrcvpor-idoctyp    NO INTERVALS.
SELECTION-SCREEN END OF BLOCK idoc_rcv.
SELECTION-SCREEN END OF BLOCK idoc.
* Payload
SELECTION-SCREEN BEGIN OF BLOCK xp WITH FRAME TITLE text-s30.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT (30) text-x01 FOR FIELD p_xpath.
PARAMETERS: p_xpath TYPE text256.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT (30) text-x02 FOR FIELD s_xvalue.
PARAMETERS: p_xvalue TYPE text256 NO-DISPLAY.
SELECT-OPTIONS s_xvalue for p_xvalue.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN END OF BLOCK xp.
SELECTION-SCREEN END OF SCREEN 0850.
* Super selection screen -------------------------------------------------- END
I'm having trouble entering the next piece of code for INCLUDE ZXIMONI_RSXMB_CUSTFILTERS so will enter it in the next post.

ABAP Proxy guide?

Similar Messages

Maybe you are looking for