How to Debug PROXY Side Coding

Hi,
I need to debug my PROXY Code in R/3 side, but here from where to get the data for testing as I have the file content but not in XML format that is required in XML Editor when we debug the proxy.
In SXMB_MONI also I am finding the complete converted data,how to get the prcoess before data.
Thanks
Sudharshan

Hi -
>>>In SXMB_MONI also I am finding the complete converted data,how to get the prcoess before data.
Need more clarification... Are you talking about the XML before the mapping step but after file content conversion? If so, just go to any pipeline step before the Request Message Mapping step and look at the Payload->Main Document.
Regards,
Jin

Similar Messages

How to debug the LSMW coding???

Hi Experts,
Any one please tell how to debug the lSMW codings?
Thnx,
Mohana

Hi,
Go to the 5th Step that is
"5 Maintain Field Mapping and Conversion Rules"
select this radio Button and execute then
you will maping your defining fields to source structure fields
then where ever you want to write validations
you just select that field and click on RULES tab
then select radio-button User defined routine
then you will get a window
you just click on continue button
then you will get a PERFORM opposite to your selected field
save and come back
then select the 6th radio button
that is " 6 Maintain Fixed Values, Translations, User-Defined Routines"
and execute
there you will find your user defind routine
you just double click on the routine
then you will get a editor for writing your code for validations
you just pass p_in as input and you will get the result in p_out parameter
then you will put a Break point or put command like "BREAK-POINT"
then it will automatically triggered while running this project.
To view your generated code, you need to bring it up in the initial screen of your object.To do so,
click on the User Menu button & check the Display Read Program & Display Conversion Program will take
you into the generated code. Place your soft breakpoint as you normally do.
Another option: go to the step DISPLAY READ PROGRAM or DISPLAY CONVERTION PROGRAM.
Now you will see the ABAP editor with the code. Place the breakpoint (soft break point using STOP button on application tool bar) where ever you desire.
Regards.

I can only figure out how to debug on the flex side

I am calling CFC methods from my flex applications but I can
only figure out how to debug on the flex side. Is it possible to
debug on the CFC methods begin called from flex? I don't think this
is possible but you may prove me wrong :)

Thanks.
As a workaround I tried returning the thing that I suspect
the problem lies:
<cffunction name="updateField" access="remote"
returntype="String">
<cfargument name="field" required="true"
type="string">
<cfargument name="currencyName" required="true"
type="string">

<cfargument name="value" required="true"
type="Numeric">
<cfquery name="q" datasource="#datasource#">
update tbale
set <cfqueryparam value="#arguments.field#"
cfsqltype="cf_sql_varchar"> =
<cfqueryparam value="#arguments.value#"
cfsqltype="cf_sql_float">
where currencyName =
<cfqueryparam value="#arguments.currencyName#"
cfsqltype="cf_sql_varchar">
</cfquery>
<cfset flash.result="update RATES #arguments.field#" >
<cfreturn flash.result>
</cffunction>
but the following line does not return the correct string:
<cfset flash.result="update RATES #arguments.field#" >
I do I add arguments to the string?

How to debug smartforms

hi
could anybody suggest me how to debug smatforms
thank you
kalyan.

Please set a break point in side the smartform:
BREAK <USERNAME>.
Then at the time of print/ preview the program stops there.
Example : If you set the break point in initializationas
BREAK <USERNAME>.
Program stops at break point. After that use Serach and set more break points.
>Search the program logic/Textelement/Address via search and set the break point at that code.
1) One way to debug smartform is to debug the Function Module of that smartforms.
If you want to debug particular smartform node that the solution would be,
insert a "Program Line" just above the node you want to debug and this program line write a normal abap breakpoint.
So whenever you call the smartforms, it will stop at this breakpoint and you can debug onwards.
2) SFTRACE can be used for debugging SMARTFORMS.
1)goto tcode SFTRACE --> click "trace on"
2) Get the function module name and set break points in function module name.
There is a transaction 'SMARTFORMS_TRACE' (or was it 'SMARTFORMS_TRACE') which will give you quite helpful information.
In SAPSCRIPTS, you can 'Activate the debugger' in SE71 to start the debugging of script.
In SMARTFORMS, you can use BREAK-POINT (coded in any code window node) to initiate debugging of SF.
SFTRACE can be used for debugging SMARTFORMS.
Go in smartforms, put a breakpoint where you want in the generated FM.
Then go in you're PO, go to messages, generated you're output and make sure in further data option 1 is selected.
Then run program rsnast00 with you're form settings, that's it!
You could debug sapscript like that also,
regards,
srinivas

How to debug BADI BBP_SAPXML1_OUT_BADI during PO Creation and change

Hi All,
I have a scenario in which i need to send some additional fields with the PO data to the XI via PROXY .
To do this i have enhanced the proxy structure with additional fields and For mapping these fields, I created an implementation of method PURCHASEORDER of BAdI BBP_SAPXML1_OUT_BADI with filter PO ( Purchase orders ).
But this implementation is not getting processed.
Whenever Po is created the XI will receive the data but the additional fields are not available in XI.
To check the code i need to debug the badi implementation .
Can anybody please tell me why this badi is not triggered and how to debug the badi code.
Its urgebt .
Thanks in Advance.
Regards,
Naresh

Hi Naresh,
Go to your BADI Implementation set infinite loop in the method. Run the transaction SPPFP & set Promotion status to 0 & Processing Type as MET & execute it, Select the PO you want to debug & press F8. Goto sm50 to debug the BADI.
Thanks

How to debug a report

how to debug a report
i am new to ABAP

Hi
ABAP Debugger
The ABAP Debugger is an integrated test tool within the ABAP Workbench. You use it to check the program logic and to find errors in the source code of an ABAP program. In the Debugger, you can step through the source code of a program. The running program is interrupted after each step, allowing you to check its processing logic and the results of individual statements.
As of Release 6.10, you can also run Business Server Pages (BSP) in the debugging mode. You can also display and set breakpoints here. Business Server Pages can be displayed in the Object Navigator when you select an appropriate application under BSP Application.
Features
The Debugger provides an efficient means of identifying errors in ABAP programs. It contains the following functions:
 Ways of starting the Debugger
 Choosing different views
 Choosing different execution options in the Debugger
 Displaying source code in the Debugger
 Setting and deleting breakpoints
 Setting and deleting watchpoints
 Stopping a program at a particular statement or event
 Displaying and changing field contents at runtime
 Displaying ABAP Objects and references
 Displaying and positioning strings
 Setting and deleting database locks
 Opening the ABAP Editor, or Object Navigator
 System settings and runtime warnings
Starting the Debugger
There are two possible strategies for starting the Debugger in the ABAP Workbench:
 By setting breakpoints then running the program
 By running the program in debugging mode.
Setting Breakpoints
A breakpoint is a signal in a line of code that tells the ABAP runtime processor to interrupt the program at that line and start the ABAP Debugger. A distinction is made between static and dynamic breakpoints. For further information about the different types of breakpoints and how to use them, refer to Breakpoints.
Running a Program in Debugging Mode
You can start the Debugger without previously having set breakpoints. This is the best procedure to use when you want to test a program right from the beginning. It is also useful if you do not know the program very well and therefore are not sure where best to set breakpoints. You can start the Debugger as follows:
From the Object Navigator Select a report or transaction and program and choose Program Test Debugging.
From the ABAP Editor Choose Program  Execute  Debugging (or the Debugging pushbutton).
From any screen Choose System  Utilities  Debug ABAP.
From any screen Enter " /h " in the command field.
Checking System Programs for Errors
To check a program or program component that is part of the ABAP Workbench (for example, the Screen Painter), you must use the system Debugger. To start the system Debugger, choose System  Utilities  Debug system from any screen. To stop the system Debugger, choose Debugger  Debugging off.

Displaying Program Attributes
You can display the attributes Fixed point arithmetic, System program and Unicode checks active of the program that has just been executed by choosing Goto  Further Information  Program Attributes.

Display Modes in the Debugger
When you are debugging a program, there are various display modes that you can use. All of the display modes have the same structure. The top part of the screen displays an extract of the program source code. The bottom part displays the information specifically available in that display mode. There are also pushbuttons on the screen allowing you to switch to the most frequently-used display modes.
go to se38->give ur program name-.execute->give /h at command prompt->execute->now debugging will start->
f5-used for line by line debugging
f6-used for directly executing function modules or performs i.e. control won't go into that block.
f7-run to cursor
f8-direct executing.
fileds: here we can check fild values.
click fileds option and double click on the filed or type the filen name beside filed
tables : here we can check the data in the internal table.
click tables option and double click on the internal table.
Break points:
if you want to debug a particulr part you can use this.
place the cursor at any perform click breakpoint or double click on that line.it will be set.
if /h from report statement it will debug,so for debugging from particular point we will use break points.use f7 to traverse between multiple break points.
Watch-points: In some cases we need to check the data populated in the internal table for eample if we want to check the data of internal table record belongs to 100th vendor we will create watch point for this goto->breakpoints->create watch points->give filed itab-lifnr->=->100.
debugging procedure:
Use '/H' in the command line and execute the report/program, so that it goes to debugging mode
2. keep a hard coded break point in the code like BREAK-POINT and it stops there.
3.From the program Menu, Keep the Soft Break-points and do the debugging.
see the links
Refer to this thread
http://help.sap.com/saphelp_47x200/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/content.htm
http://www.sappro.com/downloads/Settings&SystemAreas.pdf
http://help.sap.com/saphelp_47x200/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/frameset.htm
https://forums.sdn.sap.com/click.jspa?searchID=2673672&messageID=3187106
https://forums.sdn.sap.com/click.jspa?searchID=2673672&messageID=850453
https://forums.sdn.sap.com/click.jspa?searchID=2673672&messageID=1546485
https://forums.sdn.sap.com/click.jspa?searchID=2673628&messageID=2048883
http://www.saplinks.net/index.php?option=com_content&task=view&id=24&Itemid=34
http://www.sap-img.com/abap/testing-and-debugging-abap-codes-functions.htm
Reward points if useful

How to Debug RFC Enabled FM ?

Hello All,
 I want to debug an RFC Enabled FM.
I've written a small Test program to check this.
DATA: eenumber LIKE bapip2001-pernr,
 subtype LIKE bapip2001-subty,
 objectid LIKE bapip2001-objps,
 lockindicator LIKE bapip2001-sprps,
 validitybegin LIKE bapip2001-begda,
 validityend LIKE bapip2001-endda,
 recordnumber LIKE bapip2001-seqnr.
CALL FUNCTION 'BAPI_ABSENCE_GETDETAIL
EXPORTING
 employeenumber = eenumber
 subtype = subtype
 objectid = objectid
 lockindicator = lockindicator
 validitybegin = validitybegin
 validityend = validityend
 recordnumber = recordnumber
* IMPORTING
* RETURN =
* START =
* END =
* ABSENCETYPE =
* ABSENCEDAYS =
* ABSENCEHOURS =
* NAMEOFABSENCETYPE =
IF sy-subrc <> 0.
WRITE:/ 'UNsuccessful'.
ENDIF.
When a Break Point is kept at the above FM and When I press F5 the cursor is going into the FM .
But when I specify the Destination in the Call Statement as :
CALL FUNCTION 'BAPI_ABSENCE_GETDETAIL' DESTINATION 'SID_010'
EXPORTING
 employeenumber = eenumber
 subtype = subtype
 objectid = objectid
 lockindicator = lockindicator
 validitybegin = validitybegin
 validityend = validityend
 recordnumber = recordnumber
* IMPORTING
* RETURN =
* START =
* END =
* ABSENCETYPE =
* ABSENCEDAYS =
* ABSENCEHOURS =
* NAMEOFABSENCETYPE =
The control is not going into the FM.
Can any one tell me how to debug the FM within a different system ?
Regards,
Deepu.K

Hi Deepu,
Your function module is at other system and you are calling it at some other system.
I hope you know on which system your function module exists.
First debug your coding at your system where you are calling this RFC Function Module and go to that point where your function module starts, now check the export data here
And
go to that system where this function module exists and give the same export data there and debug this Function Module at that system.
Reward points, if helpful,
Sandeep Kaushik

How to DEBUG a function module running in background mode? Please help!

Hi Experts,
 I am calling a function module in my ABAP code in background module using the following syntax:
CALL FUNCTION 'YBBC2_CREATE_SNAPSHOT' IN BACKGROUND TASK
 TABLES
 itab_std_format_inv = itab_std_format_inv
 itab_snapshot_inv = itab_snapshot_inv.
 COMMIT WORK.
If I put the breakpoint in the CALL FUNCTION line and execute the program, the debugger does not take me to the valled function module. This may be because I am running the function module as background task.
I cannot comment this "IN BACKGROUND TASK" statement as well since i am debugging in Quality system where I don't have change access.
So how to DEBUG a function module running in background mode? Please help!
Thanks
Gopal

Hi,
You could try to use the following trick:
(1) Put an endless loop into the coding of your function module where you want to start debugging, e.g.
DATA:
 lx_exit_loop(1) TYPE c.
lx_exit_loop = ' '.
DO.
 IF ( lx_exit_loop = 'X' ).
 EXIT.
 ENDIF.
ENDDO.
(2) Call your function module in background task
(3) Call transaction SM50 and search for the background process.
(3) Choose from menu Program/Mode -> Program -> Debugging
Now you the debugger should bring you right to your endless loop. Set lx_loop_exit = 'X' in the debugger and continue (F5 or F6).
Reward points
Regards

How to debug ABAP Web services from Microsoft Visual Studio

When developing .NET based Web services clients using Visual Studio that call Web services in SAP NetWeaver .NET developers would like to be able to debug inside SAP. In my blog <a href="/people/andre.fischer/blog/2007/02/07/how-to-debug-abap-web-services-from-microsoft-visual-studio to debug ABAP Web services from Microsoft Visual Studio</a> I would like to point .NET developers to the fact that SAP NetWeaver offers the option of external debugging to perform this task. Though the steps that have to be performed are described in the SAP Online Help I am sure that this option is not well known amongst the .NET developer community.

Hello WilliamIV,
>>How can I "configure" Visual Studio debugger to allow validation to work?
Since I do not have a VS2012 environment, according to your provided link, I created a test demo with VS2013, however, both ways catch the validation error:
If possible, you could have a try with VS2013 to see if it works or run the example on other machine with VS2012 to see if this is caused by the VS environment, in my side, I do not change any configuration, all are default.
If I misunderstood this issue, please feel free to let me know.
Regards.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

How to debug this error? trying to load excel file to Database

SSIS package "c:\users\asubedi\documents\visual studio 2012\Projects\Integration Services Project1\Integration Services Project1\PackageToLoadBuyerDedupe.dtsx" starting.
Information: 0x4004300A at BuyerDedupe, SSIS.Pipeline: Validation phase is beginning.
Error: 0xC0209303 at PackageToLoadBuyerDedupe, Connection manager "Excel Connection Manager": The requested OLE DB provider Microsoft.ACE.OLEDB.12.0 is not registered. If the 64-bit driver is not installed, run the package in 32-bit mode. Error code: 0x00000000.
An OLE DB record is available. Source: "Microsoft OLE DB Service Components" Hresult: 0x80040154 Description: "Class not registered".
Error: 0xC001002B at PackageToLoadBuyerDedupe, Connection manager "Excel Connection Manager": The 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine. For more information, see http://go.microsoft.com/fwlink/?LinkId=219816
Error: 0xC020801C at BuyerDedupe, Excel Source [2]: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "Excel Connection Manager" failed with error code 0xC0209303. There may be error messages posted before this with more information on why the AcquireConnection method call failed.
Error: 0xC0047017 at BuyerDedupe, SSIS.Pipeline: Excel Source failed validation and returned error code 0xC020801C.
Error: 0xC004700C at BuyerDedupe, SSIS.Pipeline: One or more component failed validation.
Error: 0xC0024107 at BuyerDedupe: There were errors during task validation.
SSIS package "c:\users\asubedi\documents\visual studio 2012\Projects\Integration Services Project1\Integration Services Project1\PackageToLoadBuyerDedupe.dtsx" finished: Failure.
how to debug this issue?

Hi Arjunji,
The issue occurs because you have only 32-bit Microsoft ACE 12.0 OLEDB drivers installed, however, the package runs in 64-bit runtime mode which requires 64-bit drivers.
To avoid this issue, you need to either install the 64-bit
Microsoft Access Database Engine 2010 Redistributable or run the package in 32-bit runtime mode. To run the package in 32-bit runtime mode, in SSDT, you can set the Run64BitRuntime property of the IS project to False; in a SQL Server Agent job, you can
configure the SSIS Package Job step and check the “Use 32 bit run time” option.
In addition, please note that the 32-bit install file of Microsoft Access Database Engine 2010 Redistributable and the 64-bit one cannot be installed side by side on a single server. However, if your current ACE 12.0 OLE DB drivers are installed by 32-bit
Office suit, you can go ahead and install the 64-bit Microsoft Access Database Engine 2010 Redistributable.
Regards,
Mike Yin
TechNet Community Support

How to debug Function Modules from ISA!!!

Hi Gurus,
How to debug the function modules from ISA.
For Ex:If i am in shopping cart or product catalog,e.t.c..i need to know which FM is calling from backend, how to debug the FMs/Bapis related to that from ISA side.
direct me to all the possible ways.
Regards,
Anil.

Hello Anil,
There are a few things you need to look at when trying to debug .
1. The function module needed ( you can do a trace to see which one is called.)
2. The user that is been user With statefull and stateless connection the FM can be called by either the JCO user or the internet user. This will need to be considered when setting your external break point.
3. The server been used, You will need to check the XCM to see which server is been used ie are you using a group connect of a specific server , You need to make sure that you are setting the breakpoint on the server that is specified in the XCM.
Have a look at note [871907|https://service.sap.com/sap/support/notes/871907] the attachment to the note may help you a lot. .
Hope this helps.
Regards
Mark
Edited by: Mark Foley on Feb 11, 2009 11:10 AM

How to Debug Functional Module called via RFC?

Hi Experts,
     Please, can someone explain to me how to debug functional module that is called via RFC? Thanks in advance.
Best Regards,
Aleksandar

Hi Laxman,
   First of all thank you very much for giving attention to my post. Ok, I am trying to debug function module in RM-CA (FICA), function module is called by CRM system (via RFC) and in addition all this chain is triggered by WebClient.
     I have user that can login on the CRM as well as on RM-CA (ECC 6.0) system, but those users are different (unfortunately I do not have administration permission so I cant change profiles of my users but I can ask for it). I can without any problem debug calls that come from WebClient, so setting an external break point in CRM system I can catch whatever I want but when process comes to point where actually call to back-end (RM-CA) takes place I simply cant get into functional module, that resides on RM-CA side. Actually what happens is that processing continues as was chosen NEXT STEP (F6).
     To resume, two systems and two different users. Where XCM user should be created? (on RM-CA system or CRM). Should I change something in Menu option Utilities -> Settings -> ABAP Editor tab -> Debugging tab, in field users? If you need any additional info please tell me.
Thanks again for your support.
Aleksandar

How to debug the smart forms

Hi All,
Can any body guide me how to debug the smart forms.
Thanks & Regards,
Satish.

Hi,
The the best way to debug the form is to put a breakpoint in the function module generated by the smartform.
Procedure:
Open the smartform we want to debug.
Goto Environment -> Function module name.
Open the function module in SE37. From the menu GOTO -> main program. Open the last include.
This incude contains the entire code ie the code we have written in initalization + form routines + program lines + sap generated code.
Even we can search for the text nodes, folders, templates, tables, graphics, address nodes etc with their names.
Put a breakpoint at any point you want.
If we issue any doc which triggers this form, when the control reaches the break point it will stop.
Please note that hard-coding the break points in the code ( Program lines ) is not recommended and it can´t be done unless if it is development server.
So, always put a session break point in the related function module.
We can use SFTRACE transaction to know the sequence of the control flow.
If you want to break at each and every text that is printed on the output form put the break points in the forms.
1. %write_text to break at text element.
2. %WRITE_TEXT_MODULE to break at text module.
3. %WRITE_INCLUDE_TEXT to break at include text.
Please put a break point at the first sy-subrc check.
If the control reaches this point, you can find the name of the element in the varible NAME and the content in the text node in %TEXT.
Its easy to understand the sequence of the printing if we put a breakpoint as stated above.
Regards,
Satish.

How to debug sproxy class program?

Hi experts,
In my scenario, PI will pick flat files, then post the data to ECC.
In ECC->sproxy->my scenario,double click the "provider class",then double click the method, I'll write the abap code here.
How to debug the program?
Thanks

Hi Michael,
After completion of writing the ABAP code. Keep a break point externally in your Proxy code and then try to execute. It will take to the break point and now check the code manually. If you need any changes modiify it accordingly.
The below blog will help you to debug the inbound proxy.
/people/stefan.grube/blog/2006/07/28/xi-debug-your-inbound-abap-proxy-implementation
Thanks,

How to debug Delta records..urgent

Hi All,
I loaded some records with delta mode.
In rsa3, I select delta mode D, and clk Excute button, But It is saying "Error During Execution".
A. What is the reason Can any one explain?
B. How to Debug my delta records?
Pls explain Urgent.
Thanks & Regards,
Lakshmi.K.

Hi,
in case of simulation of update mode D you also have to provide the name of your target system. Then check the box debug mode. After clicking the execution button you are in the coding right before the extraction fm gets called. Jump into in by pressing F5 ....
But first of all you need to make sure that your datasource provides a delta (this may cause the 'error during execution').
regards
Siggi

How to Debug PROXY Side Coding

Similar Messages

Maybe you are looking for