Debugging ABAP proxy

Hi all,
Can anyone please tell me how to debug abap proxy.
In my scenario i chnaged the code in proxy.(file to r/3)
I want to debug the code which i have changed..According to me it should be debugged in sm50 (testing client), which i couldnt do?
Any Ideas greatly appreciated..
Regards,
smith

Hi Paul,
Checkout these links..
http://help.sap.com/saphelp_nw2004s/helpdata/en/3b/6f5c3c3806af06e10000000a11402f/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/14/555f3c482a7331e10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/81/845f3c31727d59e10000000a114084/frameset.htm
Transaction Code SPROXY
Hope they help you!
cheers,
Prashanth
P.S : Please mark all helpful answers

Similar Messages

Debugging ABAP Proxy code

Hi,
I have problem in ABAP Proxy. When i upload a XML and test the ABAP Proxy code it is working fine, but when i trigger the change from sender, its updating the wrong value in the database.
I checked the incoming and the converted XML, everything is correct and there is no prob in the XI.
Please tell me is there any way to debug the ABAP Proxy during the actual proccessing i,e. when the change is triggered from the sender.
Thanks and Regards,
Arunsri

I've had the same problem before...everything seemed fine but the xml was not updating the desired values - you have 2 choices - 1. Enable the debugging, but if you have a high volume scenario, then it may cause some issues. Also, I am not sure if you plan to do this in production - as you know, debugging in production is a big No-No.
Option 2 is to just take the stream and store it as a file in the OS. This is what we followed and we were able to figure out the issue with the xml. Make sure you write it in such a way that you can turn it off immediately. In our case, it worked fine for all suppliers but one and this one supplier was sending a double spaced character in between, which was causing the issue.
Regards,
Srini

Debugging of inbound ABAP proxy

Please To show the debugging of inbound ABAP proxy, the implementation of the demo scenario is used. The demo scenario is available in any installation WebAS 6.40 or higher.

follow this method and check debugging mode.
Debugging of inbound proxies in WebAS 6.40 or higher
To show the debugging of inbound ABAP proxy, the implementation of the demo scenario is used. The demo scenario is available in any installation WebAS 6.40 or higher.
At first you have to set a break point in the ABAP code. Call transaction SPROXY. Expand the namespace http://sap.com/xi/XI/Demo/Airline, the node Message Interface (inbound) and the interface FlightBookingOrderRequest_In.
Double click on interface II_SXIDAL_FBO_REQUEST and get the view of the proxy object properties.
Double click on the implementing class (ABAP name) and then double click on the method name (this class has only one method).
Now you are in the inbound proxy implementation. Set the break point on the first executable line.
With help of the back button (F3) go back to the transaction SPROXY. Here you choose from menu Proxy -> Test Interface
In the next pop up check the field XML Editor to maintain the payload.
In the next screen apply suitable values or upload the XML payload of the SXMB_MONI (after mapping).
Now the inbound proxy processing should stop at the break point.
If the processing does not stop at the break point, there might be an error in the XML. Check at the result page for error messages.
Debugging of inbound proxies in WebAS 6.20
You set the break point the same way as described above.
To start the proxy test you call the report SPRX_TEST_INBOUND.
As parameters you enter the name of the ABAP interface and the method name of of the ABAP interface and check the parameter Edit Native XML
In the next screen you apply suitable values or upload the XML payload of the SXMB_MONI (after mapping).
Then you click first on save button (F11), then on back button (F3).
Now you should see your debug session. If not, check if the XML is valid. BAPI_GOODSMVT_CREATE to post Goods Movement
The following is an abap program making used of the BAPI function BAPI_GOODSMVT_CREATE to do Goods Receipts for Purchase Order after importing the data from an external system.
BAPI TO Upload Inventory Data
GMCODE Table T158G - 01 - MB01 - Goods Receipts for Purchase Order
                     02 - MB31 - Goods Receipts for Prod Order
                     03 - MB1A - Goods Issue
                     04 - MB1B - Transfer Posting
                     05 - MB1C - Enter Other Goods Receipt
                     06 - MB11
Domain: KZBEW - Movement Indicator
     Goods movement w/o reference
B - Goods movement for purchase order
F - Goods movement for production order
L - Goods movement for delivery note
K - Goods movement for kanban requirement (WM - internal only)
O - Subsequent adjustment of "material-provided" consumption
W - Subsequent adjustment of proportion/product unit material
report zbapi_goodsmovement.
parameters: p-file like rlgrap-filename default
                                 'c:\sapdata\TEST.txt'.
parameters: e-file like rlgrap-filename default
                                 'c:\sapdata\gdsmvterror.txt'.
parameters: xpost like sy-datum default sy-datum.
data: begin of gmhead.
        include structure bapi2017_gm_head_01.
data: end of gmhead.
data: begin of gmcode.
        include structure bapi2017_gm_code.
data: end of gmcode.
data: begin of mthead.
        include structure bapi2017_gm_head_ret.
data: end of mthead.
data: begin of itab occurs 100.
        include structure bapi2017_gm_item_create.
data: end of itab.
data: begin of errmsg occurs 10.
        include structure bapiret2.
data: end of errmsg.
data: wmenge like iseg-menge,
      errflag.
data: begin of pcitab occurs 100,
        ext_doc(10),           "External Document Number
        mvt_type(3),           "Movement Type
        doc_date(8),           "Document Date
        post_date(8),          "Posting Date
        plant(4),              "Plant
        material(18),          "Material Number
        qty(13),               "Quantity
        recv_loc(4),           "Receiving Location
        issue_loc(4),          "Issuing Location
        pur_doc(10),           "Purchase Document No
        po_item(3),            "Purchase Document Item No
        del_no(10),            "Delivery Purchase Order Number
        del_item(3),           "Delivery Item
        prod_doc(10),          "Production Document No
        scrap_reason(10),      "Scrap Reason
        upd_sta(1),            "Update Status
      end of pcitab.
call function 'WS_UPLOAD'
exporting
    filename                      = p-file
    filetype                      = 'DAT'
IMPORTING
FILELENGTH                    =
tables
    data_tab                      = pcitab
EXCEPTIONS
FILE_OPEN_ERROR               = 1
FILE_READ_ERROR               = 2
NO_BATCH                      = 3
GUI_REFUSE_FILETRANSFER       = 4
INVALID_TYPE                  = 5
OTHERS                        = 6
if sy-subrc <> 0.
message id sy-msgid type sy-msgty number sy-msgno
          with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
exit.
endif.
gmhead-pstng_date = sy-datum.
gmhead-doc_date = sy-datum.
gmhead-pr_uname = sy-uname.
gmcode-gm_code = '01'.   "01 - MB01 - Goods Receipts for Purchase Order
loop at pcitab.
itab-move_type = pcitab-mvt_type.
itab-mvt_ind    = 'B'.
itab-plant      = pcitab-plant.
itab-material   = pcitab-material.
itab-entry_qnt = pcitab-qty.
itab-move_stloc = pcitab-recv_loc.
itab-stge_loc   = pcitab-issue_loc.
itab-po_number = pcitab-pur_doc.
itab-po_item    = pcitab-po_item.
concatenate pcitab-del_no pcitab-del_item into itab-item_text.
itab-move_reas = pcitab-scrap_reason.
append itab.
endloop.
loop at itab.
write:/ itab-material, itab-plant, itab-stge_loc,
          itab-move_type, itab-entry_qnt, itab-entry_uom,
          itab-entry_uom_iso, itab-po_number, itab-po_item,
                                              pcitab-ext_doc.
endloop.
call function 'BAPI_GOODSMVT_CREATE'
exporting
    goodsmvt_header             = gmhead
    goodsmvt_code               = gmcode
TESTRUN                     = ' '
IMPORTING
    goodsmvt_headret            = mthead
MATERIALDOCUMENT            =
MATDOCUMENTYEAR             =
tables
    goodsmvt_item               = itab
GOODSMVT_SERIALNUMBER       =
    return                      = errmsg
clear errflag.
loop at errmsg.
if errmsg-type eq 'E'.
    write:/'Error in function', errmsg-message.
    errflag = 'X'.
else.
    write:/ errmsg-message.
endif.
endloop.
if errflag is initial.
commit work and wait.
if sy-subrc ne 0.
    write:/ 'Error in updating'.
    exit.
else.
    write:/ mthead-mat_doc, mthead-doc_year.
    perform upd_sta.
endif.
endif.
      FORM UPD_STA                                                  *
form upd_sta.
loop at pcitab.
    pcitab-upd_sta = 'X'.
    modify pcitab.
endloop.
call function 'WS_DOWNLOAD'
    exporting
      filename                      = p-file
      filetype                      = 'DAT'
IMPORTING
FILELENGTH                    =
    tables
      data_tab                      = pcitab
EXCEPTIONS
FILE_OPEN_ERROR               = 1
FILE_READ_ERROR               = 2
NO_BATCH                      = 3
GUI_REFUSE_FILETRANSFER       = 4
INVALID_TYPE                  = 5
OTHERS                        = 6
endform.
*--- End of Program
Finding the user-exits of a SAP transaction code
Finding the user-exits of a SAP transaction code
Enter the transaction code in which you are looking for the user-exit
and it will list you the list of user-exits in the transaction code.
Also a drill down is possible which will help you to branch to SMOD.
report zuserexit no standard page heading.
tables : tstc, tadir, modsapt, modact, trdir, tfdir, enlfdir.
         tables : tstct.
data : jtab like tadir occurs 0 with header line.
data : field1(30).
data : v_devclass like tadir-devclass.
parameters : p_tcode like tstc-tcode obligatory.
select single * from tstc where tcode eq p_tcode.
if sy-subrc eq 0.
   select single * from tadir where pgmid = 'R3TR'
                    and object = 'PROG'
                    and obj_name = tstc-pgmna.
   move : tadir-devclass to v_devclass.
      if sy-subrc ne 0.
         select single * from trdir where name = tstc-pgmna.
         if trdir-subc eq 'F'.
            select single * from tfdir where pname = tstc-pgmna.
            select single * from enlfdir where funcname =
            tfdir-funcname.
            select single * from tadir where pgmid = 'R3TR'
                               and object = 'FUGR'
                               and obj_name eq enlfdir-area.
            move : tadir-devclass to v_devclass.
          endif.
       endif.
       select * from tadir into table jtab
                     where pgmid = 'R3TR'
                       and object = 'SMOD'
                       and devclass = v_devclass.
        select single * from tstct where sprsl eq sy-langu and
                                         tcode eq p_tcode.
        format color col_positive intensified off.
        write:/(19) 'Transaction Code - ',
             20(20) p_tcode,
             45(50) tstct-ttext.
                    skip.
        if not jtab[] is initial.
           write:/(95) sy-uline.
           format color col_heading intensified on.
           write:/1 sy-vline,
                  2 'Exit Name',
                 21 sy-vline ,
                 22 'Description',
                 95 sy-vline.
           write:/(95) sy-uline.
           loop at jtab.
              select single * from modsapt
                     where sprsl = sy-langu and
                            name = jtab-obj_name.
                   format color col_normal intensified off.
                   write:/1 sy-vline,
                          2 jtab-obj_name hotspot on,
                         21 sy-vline ,
                         22 modsapt-modtext,
                         95 sy-vline.
           endloop.
           write:/(95) sy-uline.
           describe table jtab.
           skip.
           format color col_total intensified on.
           write:/ 'No of Exits:' , sy-tfill.
        else.
           format color col_negative intensified on.
           write:/(95) 'No User Exit exists'.
        endif.
      else.
          format color col_negative intensified on.
          write:/(95) 'Transaction Code Does Not Exist'.
      endif.
at line-selection.
   get cursor field field1.
   check field1(4) eq 'JTAB'.
   set parameter id 'MON' field sy-lisel+1(10).
   call transaction 'SMOD' and skip first   screen.
*---End of Program
u2026u2026u2026u2026u2026u2026u2026u2026u2026u2026u2026u2026u2026u2026u2026u2026u2026u2026u2026u2026u2026
Difference Between BADI and User Exits
Business Add-Ins are a new SAP enhancement technique based on ABAP Objects. They can be inserted into the SAP System to accommodate user requirements too specific to be included in the standard delivery. Since specific industries often require special functions, SAP allows you to predefine these points in your software.
As with customer exits two different views are available:
In the definition view, an application programmer predefines exit points in a source that allow specific industry sectors, partners, and customers to attach additional software to standard SAP source code without having to modify the original object.
In the implementation view, the users of Business Add-Ins can customize the logic they need or use a standard logic if one is available.
In contrast to customer exits, Business Add-Ins no longer assume a two-level infrastructure (SAP and customer solutions), but instead allow for a multi-level system landscape (SAP, partner, and customer solutions, as well as country versions, industry solutions, and the like). Definitions and implementations of Business Add-Ins can be created at each level within such a system infrastructure.
SAP guarantees the upward compatibility of all Business Add-In interfaces. Release upgrades do not affect enhancement calls from within the standard software nor do they affect the validity of call interfaces. You do not have to register Business Add-Ins in SSCR.
The Business Add-In enhancement technique differentiates between enhancements that can only be implemented once and enhancements that can be used actively by any number of customers at the same time. In addition, Business Add-Ins can be defined according to filter values. This allows you to control add-in implementation and make it dependent on specific criteria (on a specific Country value, for example).
All ABAP sources, screens, GUIs, and table interfaces created using this enhancement technique are defined in a manner that allows customers to include their own enhancements in the standard. A single Business Add-In contains all of the interfaces necessary to implement a specific task.
The actual program code is enhanced using ABAP Objects. In order to better understand the programming techniques behind the Business Add-In enhancement concept, SAP recommends reading the section on ABAP Objects.
What is difference between badi and user-exists?
What is difference between enhancements and user-exists? and what is the full form of BADI?
I have another doubt in BDC IN BDC WE HAVE MSEGCALL (i did not remember the > correct name) where the error logs are stored, MSEGCALL is a table or structure.
What is the system landscape?
1) Difference between BADI and USER-EXIT.
    i) BADI's can be used any number of times, where as USER-EXITS can be used only one time.
       Ex:- if your assigning a USER-EXIT to a project in (CMOD), then you can not assign the same to other project.
    ii) BADI's are oops based.
2) About 'BDCMSGCOLL' it is a structure. Used for finding error records.
3) Full form of BADI 'Business addins'.
3) System land scape will be depends on your project
    Ex:- 'Development server'>'Quality server'-> 'Production server'......
List Of User Exit Related to VL01N
I need to some restriction in fields ( Actual GI Date, T-Code:Vl01n ).
How do you find out whcih user exits belongs to VL01n ?
Here is the list of user exit related to VL01N :
V02V0001   - Sales area determination for stock transport order
V02V0002   - User exit for storage location determination
V02V0003   - User exit for gate + matl staging area determination
V02V0004   - User Exit for Staging Area Determination (Item)
V50PSTAT - Delivery: Item Status Calculation
V50Q0001   - Delivery Monitor: User Exits for Filling Display Fields
V50R0001    - Collective processing for delivery creation
V50R0002    - Collective processing for delivery creation
V50R0004    - Calculation of Stock for POs for Shipping Due Date List
V50S0001    - User Exits for Delivery Processing
V53C0001    - Rough workload calculation in time per item
V53C0002    - W&S: RWE enhancement - shipping material type/time slot
V53W0001   - User exits for creating picking waves
VMDE0001 - Shipping Interface: Error Handling - Inbound IDoc
VMDE0002 - Shipping Interface: Message PICKSD (Picking, Outbound)
VMDE0003 - Shipping Interface: Message SDPICK (Picking, Inbound)
VMDE0004 - Shipping Interface: Message SDPACK (Packing, Inbound)

ABAP proxy Debug

Hi Group,
I have one File to File scenarion which using ABAP proxy to upload the table in SAP side.I processed the File and it is showing success status in both SAP side MONI and XI Side MONI ,but corresponding tables not updated,I need to debug the proxy ,can any body suggest.

Hi,
In SAP side SPROXY it is not showing TEST option (It is showing only
Proxy--> Save (disable)
               Check(enable)
                Activate(disable)
                Exit(enable).
Am I looking in the right place

Error in ABAP Proxy generation?

hai pals,
my intention is to push the data from XI to SAPBWSEM system throgh an ABAP PROXY.
       but , here i got an error which i already mentioned in the forum, that is " no connection to integration builder(only local data visible) ".
        i went to the integration engine configuration in "SXMB_ADM" transaction in SAPBWSEM server.
        in sxmb_adm transaction ,the system ask for the "specific configuration data-catagory" like TUNNING , MONITOR,RUNTIME,TRACELOG,DEBUG and RFCADAPTER.
         im little bit confused in choosing the "catagory of configuration data".so can u pls help me in this error.
with cheers.
rajesh

Did you create the RFC Destinations LCRSAPRFC and SAPSLDAPI to point your SLD ? If not do that.
Then create RFC Dest INTEGRATION_DIRECTORY_HMI type H. Look at your XI box and make these 3 RFC Dests.
Then use the following thread to fix your IFR_ADDRESS
Values for table SPROXSET
regards
SKM

ABAP Proxy Structure

Hi,
I have SAP server at sender side, XI is my middleware and two 3rd partyservers on the receiver side.
So,from SAP side data comes through proxy,I would generate a structure which contains the fields required to send the data to both the receivers.But few fields would used to send the data to one server and some fields to another server.
So, once the data is filled,there would be a segreation process internally writeen in proxy to segregate the data.
So, Now can i use the same structure for all the proxies i generate to send the data or should I generate different structures for each and every interface.
Thank you,
Kishore J.

hi,
check the below links, so that u will get complete concept in abap proxies:
/people/sap.user72/blog/2005/12/13/integration-builders-through-proxy-server-part--2
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
/people/arulraja.ma/blog/2006/08/18/xi-reliable-messaging-150-eoio-in-abap-proxies
/people/stefan.grube/blog/2006/07/28/xi-debug-your-inbound-abap-proxy-implementation
/people/michal.krawczyk2/blog/2006/04/19/xi-rfc-or-abap-proxy-abap-proxies-with-attachments
/people/sukumar.natarajan/blog/2007/01/07/how-to-raise-alerts-from-abap-proxy
/people/sravya.talanki2/blog/2006/07/28/smarter-approach-for-coding-abap-proxies
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy - ABAP Proxy to File
/people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies - Activate Proxy
/people/siva.maranani/blog/2005/04/03/abap-server-proxies - ABAP Server Proxy
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy - ABAP Client Proxy
/people/thomas.jung3/blog/2004/11/17/bsp-a-developers-journal-part-xiv--consuming-webservices-with-abap
/people/prateek.shah/blog/2005/06/14/file-to-r3-via-abap-proxy - ABAP Proxy
http://help.sap.com/saphelp_nw2004s/helpdata/en/48/d5a1fe5f317a4e8e35801ed2c88246/frameset.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/ba/f21a403233dd5fe10000000a155106/frameset.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/41e08c90-0201-0010-9197-d8774336ea78
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f0ae9874-109c-2910-f48a-e91f0cdd1c81
/people/sravya.talanki2/blog/2006/07/28/smarter-approach-for-coding-abap-proxies
reward points if helpful
regards
sreeni

How to catch CONVT_NO_NUMBER runtime error in ABAP Proxy

Hi all,
In our abap proxy program, sometimes the CONVT_NO_NUMBER will happen and cause the program dump and then stuck the whole queue. I noticed that this error cannot be caught by CX_ROOT exception class. So, how can I catch this runtime error and avoid the dump of our program?
Thanks,
YiNing

Hi,
While Executing the proxy,first give \h TC and then execute the proxy then it will automatically got to debugging mode.
I think ur data is worng,if it is wrong then only u will get this type of errors.
Regards,
Phani

Problem with sender ABAP proxy

Hi All,
I have created sender ABAP proxy (Async). I am testing the proxy from SPROXY transaction it selft .. when i provide the data and execute the proxy it is showing <b>"Services Processed Without Error"</b> , but i am not getting any error , i am not able to see any message in SXMB_MONI or RWB .. how to check where the message is failing ??

Hi,
You said you are sending message from proxy....its very easy to debug in this case. You can set a breakpoint directly in your proxy caling program. Just check if you are calling commit work after calling proxy.
Also you can do it using the abap system command '/H' or the code 'BREAK-POINT' for/in the report program triggering the iterface.
Check out this thread...
How to Debug proxies
Hope this will help you.
Ni;esh

Problem with Inbound Abap Proxy

Hi Experts,
I have an Inbound ABAP proxy scenario that insert data into a ztable. The whole process from XI to R/3 works fine, except it does not update my ztable.
The only time the ztable gets updated is when i debug it. I used this report "SPRX_TEST_INBOUND" to debug
Anyone who's had a similar problem.
Thank you in Advance,
Danny

Hi,
did you use the same XML from SXMB_MONI that gets posted during message flow?
you can check inside your inbound proxy if the values are not empty etc
and then raise an exception to see what's going on
you can also do an endless loop and get inside it to see the real values
that get passed into the proxy
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

Application ERROR - Fault message Error in Inbound ABAP Proxy !!

Hi Folks,
I have got application error while doing in Inbound proxy scenario. This inbound message is ProductActivityNotification, this message has got fault message. This message is triggering for faults. How to control this fault message or how to divert this error as an alert to RWB. Please give me your ideas step by step. Error as follows:
<?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>Application</SAP:Category>
<SAP:Code area="ABAP">APPLICATION_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="http://sap.com/xi/SAPGlobal20/Global">ProductActivityNotificationFault</SAP:ApplicationFaultMessage>
<SAP:Stack>Application has thrown an exception</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Please find the fault message has got following values
<?xml version="1.0" encoding="utf-8" ?>
- <n0:ProductActivityNotificationFault xmlns:n0="http://sap.com/xi/SAPGlobal20/Global" xmlns:prx="urn:sap.com:proxy:RAS:/1SAI/TAS653D9A9CCD9A8EF3AF9B:701:2009/02/10">
- <standard>
<faultText>Proxy Class (Generated)</faultText>
- <faultDetail>
<severity>information</severity>
<text>Start of inbound processing: ProductActivityNotification (ID )</text>
<id>000(/SCA/BIF_PROACT)</id>
</faultDetail>
- <faultDetail>
<severity>error</severity>
<text>Message ID is missing</text>
<id>032(/SCA/BIF_MI)</id>
</faultDetail>
</standard>
</n0:ProductActivityNotificationFault>
Will you please focus bit light on this error message please?
Regards
San

Hi,
Check your Source data is correct or not..beofr executing your scenario execute your inboud Proxy with valid data ,
check below blog...
/people/stefan.grube/blog/2006/07/28/xi-debug-your-inbound-abap-proxy-implementation
Regards,
Raj

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 Generation

Hi All,
I trying to create the ABAP Proxy(OUTBOUND)
I have created the message interface in XI and created outbound proxy in R/3 by using SPROXY Tcode.
Created the ZProgram by calling class.
and completed the Configuration steps in integration builder like (Receiver determination, Interface determination, Receiver Agreement and Receiver communication channel).
When I trying to execute Zprogram in R/3 it is giving "Proxy creation do not transport" and I did not see any message in SXMB_MONI in XI and R/3 too.
Is there any thing needs to be created in XI or R/3.
any help how to trace this..
Thanks
M

HEY MURALI,
In short : these are development steps for ur proxy :
1. generate the proxy based on a package of 4 layer strucutre.
2. After generating the proxy , activate it.
3. i will always test my proxy , at this level so that i can see its working and no issues w.rt. calling from z-program
4. i will now go and check the working of z-program and activate and execute it. you can also check if the earlier steps were successful , w.r.t debugging ur program.
5. Also check the settings/ configurations if anything missing.
Hope this helps
Vara
[PLEASE REWARD FOR POSTING]

ABAP Proxy connection Between PI and SRM for XMLs

Hello Experts,
We are trying to set up ABAP proxy connection between PI 7.1 and SRM so we can send XML from SRM into PI.
Our SRM developer is getting an SLD error (below) and seems like something is not set up right in the SLD. Could you help me out with any kind of blog/documention on setting up an ABAP proxy connection between PI and an ABAP system. Something that talks about what steps we need to take in PI and SRM.
error ...
*We saw the error during debugging. This error is preventing XML output
to be sent to PI.
BBP_BD 002 An SLD system has not been assigned to logical system
Thanks,
Mayur

Thanks all for a quick reply. I also had to take following step to achieve the task.
adding the XI system to the SRM config - SRM Server -->
Technical basic Settings --> Define System Landscape? (also please
associated documentation in that link for XI)
Thanks,
Mayur

Java Proxy and ABAP Proxy

hi,
can any one send me some documents on Java Proxy and ABBAP Proxy
regards,
John

hi,
Proxies are nothing but a mechanism to shift the application logic from the XI server onto the sender or reciever system so as to reduce the effort on the side of XI.Depending upon where the proxies are generated ,it is differentiated as client proxy ( sender ) and server proxy ( receiver ) .In R3 system having WAS 6.2 and above its already has an inbuilt small IE so the proxy generation is favoured and possilbe,for more on this please go thru the following links
Proxies: are interfaces which will get executed in the application system. They can be created only in the system from message interfaces using the proxy generation functions.
The biggest advantage of the proxy is that it always by passes the Adapter Engine and will directly interact with the application system and Integration engine - so it will and should give us a better performance.
The literal definition of a proxy is an object / process authorized to act for another; an agent or a substitute. In simpler terms, proxies in the XI context are objects used to encapsulate the creation (from a sender system) or parsing of XML (at a receiver system) as well as the communication with the relevant runtime components required to send or receive those messages. The Proxy Runtime controls these objects / processes, and can itself be controlled by the applications it communicates with.
The Proxy currently has the following components available:
1. ABAP Proxy Communication using XI or Web Services
2. Java Proxy Communication using XI (J2EE)
For further reference, visit the following sites,
To test a connection - /people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
Client Proxy - /people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
Server Proxy - /people/siva.maranani/blog/2005/04/03/abap-server-proxies
Testing proxy - /people/stefan.grube/blog/2006/07/28/xi-debug-your-inbound-abap-proxy-implementation
JAVA Proxies:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a068cf2f-0401-0010-2aa9-f5ae4b2096f9
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f272165e-0401-0010-b4a1-e7eb8903501d
ABAP Proxies:
/people/sap.user72/blog/2005/12/13/integration-builders-through-proxy-server-part--2
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
/people/arulraja.ma/blog/2006/08/18/xi-reliable-messaging-150-eoio-in-abap-proxies
/people/stefan.grube/blog/2006/07/28/xi-debug-your-inbound-abap-proxy-implementation
/people/michal.krawczyk2/blog/2006/04/19/xi-rfc-or-abap-proxy-abap-proxies-with-attachments
/people/sukumar.natarajan/blog/2007/01/07/how-to-raise-alerts-from-abap-proxy
/people/sravya.talanki2/blog/2006/07/28/smarter-approach-for-coding-abap-proxies
ON SDN TV
https://www.sdn.sap.com/irj/sdn/advancedsearch?query=abap%20proxy%20xi&cat=sdn_all&start=11#

ABAP Proxy synchronous interface - access to payload

Hi,
I have a scenario from ABAP Proxy -> XI -> Web Service.
On occassion, there is an issue with calling the Web Service (unavailable for instance) and an exception is returned to the ABAP Proxy for a SystemError.
I am able to catch this exception in the proxy and output the error - for example HTTP.Exception.HTTP.Adapter.
However, I also want to use information in the response payload to output on the error as the payload contain infrmation on why the error was thrown in the target application - for example - Format of data xxx is incorrect.
I can get access to the request payload using interface/class IF_WSPROTOCOL_PAYLOAD=>GET_SENT_REQUEST_PAYLOAD but there does not seem to be an equivalent for GET_RECEIVED_RESPONSE_PAYLOAD !
Have anyone done this before - use payload information in an ABAP proxy from the response payload ?
Kind regards
Colin.

Hi,
I will need the actual payload info not the status.
I will have to debug SXI_MONITOR in CRM to see how it is obtained.
Thanks
Colin

Debugging ABAP proxy

Similar Messages

Maybe you are looking for