ABAP Proxy regeneration

Hi XI experts,
We got the message in SXMB_MONI : 'o implementing class registered for the interface'. and the detail is ABAP interface, request message InvoiceRequest_Out, request message, namespace http://sap.com/xi/SRM/SupplierEnablement/Global. I wen to regenerated the relevant class in SPROXY but still get the message.
Please help.
Jason

Hi,
the ABAP proxy is the addon of SRM component in the system. I cannot remove it and regenerate them.
The question is how do I regenerate them in SPROXY without the warning when using right mouse click and check option.
By the way I have alraady did the abap proxy activation using http rfc and defined rfc also in J2ee server.
Please advice.
Thanks!
Jason

Similar Messages

SAVE_STYLESHEET RC_6 error in ABAP proxy- CRM

Hi,
I developed a POC with just 2 fields in DT,for sender SOAP adapter and reciver ABAP proxy. It is running successfully.
But when i developed a actual scenarios with big structure it is giving the following 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>XIProxy</SAP:Category>
<SAP:Code area="ABAP">STYLESHEET_GENERATION_FAILURE</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Attempt to generate transformation required for rendering/parsing failed (, class , method ) STYLESHEET_GENERATION_FAILURE Attempt to generate transformation required for rendering/parsing failed (SAVE_STYLESHEET RC_6, class ZII_HSBP_IN_MI, method EXECUTE_ASYNCHRONOUS /1SAI/TXS) Attempt to generate transformation required for rendering/parsing failed (SAVE_STYLESHEET RC_6, class ZII_HSBP_IN_MI, method EXECUTE_ASYNCHRONOUS /1SAI/TXS)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
The only difference in both cases is, i developed everything in client 120 for POC. For actual scenario i created proxy class in client 110 and Technical system and everyting is pointing to client 120. Is it causing any problem?
Everyting is fine in XI but in CRM SXMB_MONI i can see the above error...
How to solve this issue.
Message was edited by:
ashok sri

i tired again.. i regenerated the proxy ... but still same problem..
i dont think internal framework problem.. because it worked for other scenario ( test scenario). I think i only messed it up some where.. but i dont know how to find out or how to debug the problem..
I have a doubt on package structure in which i am saving the proxy class.
i created a structuer package( level1) for which i assigned SAPPINT and for all other packages( level2- main package,level3-non main package, level4-non main package)i assigend SAI_SXMS, SAI_TOOLS, SAPPINT. I am saving the proxy class in level4 package. I am not able to assing SAI_SXMS,SAI_TOOLS to structure package. Is it causing any problem???????
any help please...
Message was edited by:
ashok sri

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 upgrade from XI 3.0 to PI 7.1

Hi,
We are planning to upgrade XI 3.0 to PI 7.1
We have couple of interfaces with ABAP proxy, the SAP version is ECC Web AS 640.
What factors do we need to take into account during this upgrade specific to Proxy development?
Thanks
Sachin K

Hey,
>We are planning to upgrade XI 3.0 to PI 7.1
System needs 64 bit OS for PI 7.1 , Will not support 32 bit OS
Customer Adapters and Adapter modules have to be adjusted and redeployed
Java Proxies have to be redeployed because JAVA JVM is installed during upgrade and JAVA JDK not supported at all in PI 7.1
>upgrade specific to Proxy development?
For ABAP Proxy Nothing, If the interfaces does not functions, The regeneration of proxy will do
Cheers
Agasthuri Doss

ABAP Proxy To XI

Hi All,
I hope i can get an answer to lingering problem that we have currently.
We manage to configure to have XI --> ECC 5.0 (through Proxy / XI Adapter)
We have another scenario where we are using ECC 5.0 through ABAP proxy to send messages to XI. However, we are facing the following error message :
<SAP:Code area="INTERNAL">DESTINATION_NOT_FOUND</SAP:Code>
<SAP:Stack>HTTP Destination_Receiver missing (system , transaction SM59)</SAP:Stack>
1. SM59 ECC --> XI HTTP Connection Test is Ok
2. SCIF T-Code. XI services all activated
3. SM59 XI --> ECC HTTP connection test was ok
4. XI --> ECC (via XI Adapter Scenario --This is ok)
5. SM59 - Deleted and recreate the connection
6. Regeneration of the Message Interface in ECC
Thank you
Sulaiman

hi asari,
ABAP proxy objects can only be generated for SAP systems that are based on SAP Web Application Server 6.40.
The proxy generation retrieves the WSDL description of the interface from the Integration Repository using HTTP. The address of the appropriate server is taken from the exchange profile (parameters 1, 2, and 3 u2013 see below). Queries to the Repository are subject to authentication. The user and password for these queries are also taken from here (parameters 5 and 6). Information used to navigate from the ABAP Proxy Generation to the initial page of the Integration Builder is also taken from the exchange profile (parameters 1, 2, and 4).
Example configuration for accessing
interfaces in the Integration Repository (exchange profile)
check link
http://help.sap.com/saphelp_nw04/helpdata/en/86/58cd3b11571962e10000000a11402f/frameset.htm
reward points if helpfull
regards
kummari

ABAP proxy delete reganarate

Hi Gurus,
Can anyone help me in knowing the difference between Regenating an ABAP proxy and Delete-Generate ABAP proxy if datatype/messagetype is changed in the Integration Repository
Thanks
Keerthi

Hi Keerthika,
-->In SPROXY if you generate the Proxy on your Interfaces and if you want to delete the Generated Proxy we can delete it.This is Delete generated proxy.
-->Regeneration of Proxy is nothing but,after generation of Proxy in your SPPROXY on the interface,If any changes made to the Data types or message types or message interfaces,you need to regenerate the proxy to occur the changes in your Proxy .
Thanks

ABAP Proxy generation descrepencies with filed and method...

Hello,
I have two question regarding ABAP Proxies.
The first one when i regenerate proxy for a interface, It is not generating the same filed as before and my ABAP program fails.
I have Internal_organization_Descri -- Now, It is not giving same field rather It is giving Internal_organization_Descr
It is missing 'i'
One more problem is It is chaging method also
Previously it was showing "Sales_order_Sync"
Now, It is showing method as EXECUTE_SYNCHRONOUS
Why It is these proxies behave differently, is there Service Pack dependency.. What is the best way to avoid these descripencies...Pls help
Srinivas

Hi,
Please find the explantion about your doubts on ABAP Proxy.
1. The field names might be changed based on the changes in XI in Data type for this field.
Whenver you will be regenerating the ABAP Proxy, it considers the Message type and internally the Data types that have created in XI. So any changes in these objects may lead to change.
Verify your field names in XI
2. The Method to be used to call ABAP proxy is EXECUTE_SYNCHRON for Synchronous communciation and EXECUTE_ASYNCHRONOUS for async communication. These methods are used in ABAP source code. So please let me know where you had find this method "Sales_order_Sync"
The EXECUTE_SYNCHRON is the proper method.
Let me know if you need any more info.
Refer
ABAP Proxy outbound program - purchase order send
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/abap%2bproxy%2boutbound%2bprogram%2b-%2bpurchase%2border%2bsend
ABAP Proxy inbound program - sales order creation - Community Profiles - Wiki
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/abap%2bproxy%2binbound%2bprogram%2b-%2bsales%2border%2bcreation
Thanks
Swarup

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

ABAP Proxy doesnu2019t Work

Hi all,
We have problem about ABAP Proxy (Inbound). We are using a follow scenario:
Legacy ( JDBC ) -> XI -> ABAP Proxy ( ECC Backend )
Recently The ECC Backend was updated ( only data ) , and since than the ABAP Proxys doesnu2019t work. We tested other Adapter, we used Receiver RFC Adapter, and RFC Adapter worked.
We tried a lot of thinks, we regenerated ABAP Proxys, We activated Proxys, taken Refresh Full CPA Cache, we checked SCIF, SMICM, and we couldnu2019t solved the issueu2026..
Could you help us????
Thanks!!!
Fábio Ferri
SAP Consultant XI/ABAP/Netweaver

Hello,
i think for this scenario..you have used XI adapter.
Check HTTP service number.
It should be same as in:
In SAP R3, Transaction - > SMICM : goto->services -> ..you will find HTTP service number..Use the same in XI adapter.
or
Execute transaction : SPROXY
goto-> connection test.
Regards,
Sreenivas.

ABAP proxy regenration

Hi,
I've got the following problem with ABAP proxy objects (acting as receiver).
We are using XI 3.0 to connect to WAS 6.20.
APPINT 200_620 0006 SAPK-20006INAPPINT SAP Exchange Infrastructure 2.0 Add-On Support Pack.
We have changed the max length size of one tag (leaf in the deep structure) in the message. The new max length is longer than before (was 10 is 12). Proxy was regenerated and activated.
On the ABAP side this field has new size (12).
After sending a message with value 000071108000 in this tag I've got the following error:
<SAP:ErrorHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
<SAP:Context />
<SAP:Code p1="Request Message" p2="CX_XSLT_DESERIALIZATION_ERROR" p3="/1SAI/XS00000000000000000009: 0000000252" p4="Tree Position: abap.values.1.1.2.2.2.14.10 ABAP Classname: CX_SY_CONVERSION_DATA_LOSS Data String: 000071108000">APPLICATIONCALL.PARSE_APPLICATION_DATA</SAP:Code>
<SAP:Text language="EN">Error when handling Request Message; XSLT error: CX_XSLT_have_ERROR: XSLT program and source line: /1SAI/XS00000000000000000009: 0000000252; Tree Position: abap.values.1.1.2.2.2.14.10 ABAP Classname: CX_SY_CONVERSION_DATA_LOSS Data String: 000071108000</SAP:Text>
</SAP:ErrorHeader>
Pls help.
Regards
Artur

Hi Artur,
you can also check if the tables that you've changed
are reflected in transports have you checked that?
there's a report for invoking those changes: SAP note 853554
Let me know if you check it
Regards,
michal

PI system data in the form of .XLS is nto moving to Inbound ABAP Proxy...

hi,
When i execute the ABAP Porxy alone,it is working fine but when the input data is moved from PI system than the data is not reachign to ABAP Proxy.please guide me what cab be done.
thanks,
Deepthi.
Moderator message: duplicate post locked.
Edited by: Thomas Zloch on May 6, 2011 4:41 PM

We have regenerated the proxy in ECC.

Error while activating ABAP proxy object

Hello,
I can see all the interfaces of PI7.0 in my ECC6.0 system.
I am able to create abap proxy object of a interface.
But when I try to activate that I am getting error as
"RFC system error for destination GTADIR_SERVER".
Pl can you suggest. appreciate quick help in this.
thanks in advance,
Sharada

Hi,
For more details take a look at note: [1063482 - Creating Dictionary objects - RFC error GTADIR_SERVER|https://service.sap.com/sap/support/notes/1063482]
It is written that: Message SGSUB 104 is not an error message, but is merely irrelevant information for customers. You can continue to create objects nevertheless.
To get rid of this annoying error you have to implement the corresponding support package.
Regards,
Jakub

Activate abap proxy withou java stack on ECC side

Hi gurus,
Can we activate abap proxy on ECC side if the ECC don't hava java stack? As you know , we need to create two jco RFC provider in Visual Administrator, but without installing java stack, we can't do that. Any ideas? Thanks in advance.

Thanks all.
Solved by using program id of XI system in the RFC of application system.
But we still face the issue in SPROXY. It gave the error "No connection to Integration Builder ".
Then I runned connection test, and found SPROX_CHECK_IFR_ADDRESS and SPROX_CHECK_HTTP_COMMUNICATION
are right, but SPROX_CHECK_IFR_RESPONSE and SPROX_CHECK_IFR_CONNECTION are giving the error "Integration Builder data not understood". Any ideas?
Edited by: xinjiang li on Sep 10, 2010 6:40 PM

SAP PI 7.4 SOAP - ABAP Proxy Synchronous Webservice

Hi Everyone,
I am developing the following scenario:
3rd party makes a SOAP call to SAP (via PI) to determine whether a vendor exists or not in the SAP system. The link for the call is provided by us from the Integrated Configuration.
The request comes in, calls an ABAP Proxy to check if a vendor exists and sends a response back to the SOAP call with a 'Y' or an 'N'.
I've read a lot about various scenarios but I'm having trouble connecting the dots as I'm fairly new to PI. I'd appreciate any help.
I've made the following set-up based on assuming I need separate Service Interfaces for the SOAP Request & Proxy Response
ESR
1. Message Types
     SOAP (MT_SOAP_REQ & MT_SOAP_RESP) - PROXY (MT_PRXY_REQ & MT_PRXY_REQ)
2. Message Mappings
     MM_REQUEST    which maps MT_SOAP_REQ   to MT_PRXY_REQ)
     MM_RESPONSE which maps MT_PRXY_RESP   to MT_SOAP_RESP)
3. Service Interfaces (Synchronous)
    (SOAP Request)
    SI_IN (Inbound Interface)       with Request = MT_SOAP_REQ and Response = MT_SOAP_RESP
   (Proxy Response)
    SI_OUT (Outbound Interface) with Request = MT_PRXY_REQ and Response = MT_PRXY_RESP
4. Operation Mapping
    OM_LOOKUP which maps SI_IN to SI_OUT with Request    (MT_SOAP_REQ to MT_PRXY_REQ)
                                                                    and Response (MT_SOAP_RESP to MT_PRXY_RESP)
I create the ABAP Proxies for each Service Interface. SI_IN contains the required coded method to check if there is a vendor.
I create the webservice and binding for SI_IN in SOAMANAGER
At this point I'm somewhat unsure - what do I need to do for SI_OUT ? Do I need to create a logical port ? how is SI_OUT associated to SI_IN (apart from the Operation) to get the response.
ID
In the Integration Directory I've created a SOAP_SENDER communication channel for System A and SOAP_RECEIVER channel for SAP. For the SOAP Receiver I need to specify a URL - what should this be ? Is it meant to point to the web service for SI_IN in SICF or just to the generic http://host:8000/sap/xi/engine?type=entry
Do I need to use the HTTP_AAE adapter for the receiver instead of SOAP ?
I created an Integrated Configuration for the SI_IN Service Interface with comm channel SOAP_SENDER from System A and SOAP_RECEIVER for SAP backend. I then got the WSDL for this to provide to the 3rd Party to test (via SOAP UI) . Again my concern is how is the SI_IN linked to the SI_OUT to achieve the response ?
I appreciate you taking the time to go through this . Any help is greatly appreciated.
Thanks very much
Gary

I create the webservice and binding for SI_IN in SOAMANAGER
At this point I'm somewhat unsure - what do I need to do for SI_OUT ? Do I need to create a logical port ? how is SI_OUT associated to SI_IN (apart from the Operation) to get the response.
>>>>No need to do anything in SOAMANAGER
Do I need to use the HTTP_AAE adapter for the receiver instead of SOAP ?
>>> No. Soap adapter is fine. Configure your receiver channel as explianed in the below blog (section 4.3)
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/70066f78-7794-2c10-2e8c-cb967cef407b?overridelayout=t…
Again my concern is how is the SI_IN linked to the SI_OUT to achieve the response ?
>>>>Your receiver determination and interface determination takes care of this.(receiver interface & outbound processing tabs in ICo)

How to change default PIRWBUSER password for ABAP Proxy monitoring ?

Hi,
Please advise how to change setting for PIRWBUSER in PI so no need to use master password PI in ECC server.
In the Message monitoring you can have option to monitoring ABAP Proxy transaction in the other SAP Instance. But of course you need to have PIRWBUSER in that target SAP instance.
How to change this configuration for PIRWBUSER for other SAP Instance. because other SAP instance it migh have different password for PIRWBUSER ?
Regards
Fernand

Hello there.
Please check the note below according to your system:
#999962 - PI 7.10: Change passwords of PI service users
#936093 - XI 7.0: Changing the passwords of XI service users
#721548 - XI 3.0: Changing the passwords of the XI service users
Regards,
Caio Cagnani

ABAP Proxy regeneration

Similar Messages

Maybe you are looking for