Debug RFCs within ABAP

I have a custom FM that I'm calling remotely via the .Net connector. When this function module is called via the ABAP test harness everything works great. When I'm calling it remotely nothing works. How do I set this code up for debugging bearing in mind that triggering it directly from the SAP client works just fine.

Aaron,
Goto FM and from the menu click on
Utilities> Settings>ABAP Editor--> Debugging over here check the External Debugging by passing the User ID.
And put a breakpoint where ever u want and call the FM from .Net then cursor will stop at the breakpoint...
Hope this helps...
Chandra.

Similar Messages

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)

Debugging RFC function module from ECC to CRM

Hi All,
My requirement is to debug an RFC function module present in CRM(7.0) system from ECC(6.0) system. A report program in ECC will call CRM custom FM. I found many posts in SDN with the same issue and tried to implement suggestions provided there. But I couldn't succeed. The approach I followed is:
I logged in to ECC report program and kept an external breakpoint just before the function module call.
I logged in to CRM system, opened the function module and kept an external breakpoint there.
In both the systems I provided the dialogue userid( id through which I log in to SAPGUI) in the system->settings->debugging option.
In CRM I activated the external break point in transaction SRDEBUG.
Now when I execute the report program in ECC, control stops at the breakpoint. If I press F5 at the function call, control is not going to the external break point set in the CRM FM. I am getting output of FM directly.
I tried with different settings like turning on the check box for IP matching and session breakpoint active immediate, switching to classic debugger etc. I also tried to provide the RFC user id instead of dialogue user but system throws exception saying only dialogue userids are allowed. I found that by inserting an infinite loop statement, control goes inside the RFC CRM FM but I prefer not to change the code.
Please let me know if I missed anything.
Thanks and Regards,
Naren

Hi,
Debug RFC calls
When an RFC function module is called it is usually not possible to debug the call, using the below techniques we can achieve the same. For this example we are calling an RFC enabled FM in ECC system from CRM system.
Scenario 1: Calling a custom RFC FM
STEP 1: Add an infinite loop in the remote custom Function Module (adding a u201CDO. ENDDO.u201D statement at the start of the FM would be enough).
STEP 2: Execute your program in the CRM system. The execution stops at the RFC call, because of the infinite loop.
STEP 3: Now login to the ECC system and go to transaction SM51 select the process which is executing the RFC and navigate to the menu: u201CProgram/Session->Program->Debuggingu201D this triggers the debugger session in a separate window.
Scenario 2: Calling a Standard RFC FM
When we are debugging a standard program we cannot add the infinite loop, hence we cannot go to SM51 and debug the work process. The RFC destination for the ECC system has a User specified, the RFC function module gets executed using this users credentials. Usually the basis team set up the RFC user as non Dialog user, this does not allow debugging. Contact your Basis team and get this changed to a dialog user enabling you to debug RFC function calls via the normal debugger.
Note: User name configured in the RFC destination (transaction SM59)
Note: User type for the RFC User (transaction SU01D)
Hope this will be helpful..

Java WD cooncect to RFC in ABAP

Hi,
i'm having doubt about the way Java Web Dynpro should have or has to do, to connect to a RFC in Abap.
do i have to use some special process?
i appreciate the help, thanks in advance

hi,
follow the process..
1.Right click the model and create a new model .
2.select Rfc model.
3. next screen will ask for R3 System detils.give the details.
4. it will ask for two JCO connectyion give the name of JCO connection.
5. now select your Rfc and click ok.
6. now go to data modular and mapped the model to component.only mapped input node.it will contain both input and output.
7. write the code now...
1.bind the node to context.
2.set the input values for rfc.
3.execute the bapi.
if u need any code and clarification please reply...

XML to internal table conversion within ABAP mapping class

I am doing a ABAP mapping for file to Idoc. My requirement is to convert XML file into ABAP internal table (within ABAP mapping class). Is there any standard FM, method, transformation etc, which can be used here.
Thanks, Dehra

Dehra,
Have you seen this weblogs which talks about this:
/people/r.eijpe/blog/2005/11/10/xml-dom-processing-in-abap-part-i--convert-an-abap-table-into-xml-file-using-sap-dom-approach
/people/r.eijpe/blog/2005/11/21/xml-dom-processing-in-abap-part-ii--convert-an-xml-file-into-an-abap-table-using-sap-dom-approach
/people/r.eijpe/blog/2006/02/19/xml-dom-processing-in-abap-part-iiia150-xml-dom-within-sap-xi-abap-mapping
/people/r.eijpe/blog/2006/02/20/xml-dom-processing-in-abap-part-iiib150-xml-dom-within-sap-xi-abap-mapping
Hope this helps you....
---Satish

Web Service to ABAP Proxy, Calling RFC from ABAP Proxy

can any body send me the notes or Step by step process of Webserice of calling RFC using ABAP proxy, I am new to XI. send me detail process of this perticular scenarios

Hope this helps
/people/siva.maranani/blog/2005/05/23/communication-between-sap-system-webservice-using-proxies
also refer to
/people/shabarish.vijayakumar/blog/2006/03/23/rfc--xi--webservice--a-complete-walkthrough-part-1
/people/shabarish.vijayakumar/blog/2006/03/28/rfc--xi--webservice--a-complete-walkthrough-part-2
Rgds,
Kumar
Message was edited by:
Kumar

QoS in RFC to ABAP Proxy

Hi,
Could some one please tell me, where can i maintian QoS (EOIO) in RFC to ABAP Proxy scenario?
I have to make sure, the data goes in order.
Thank you in advance.
Best Regards,
Prasad.

Hello Michal,
But i read the below link,
http://www.sdn.sap.com/irj/sdn/index?rid=/webcontent/uuid/70d8e250-e892-2b10-ab8a-d04433cf158b [original link is broken]
there they mentioned about it.
If not supported, could you please advice me how can i achive this EOIO case with sender RFC adater?
May be can we do something at recevier side?
Thanks in advance.
Best Regards,
Prasad.

How to debug RFC

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

Hello Kalyan,
What do you mean by debug RFC? RFC can be tested using SM59 transaction code.
Regards
Arif Mansuri

Debugging RFC Calls

I was going thru the Blog
/people/michal.krawczyk2/blog/2006/01/17/xi-debugging-rfc-calls-from-the-xi-not-possible-who-said-that-
I am not understanding what Michal is trying to say? Would some one explain me please.
I understand that when we are talking to an RFC and error occurs how XI is going to handle.
Thanks

Thanks Michal.
Just I have listed what I have understood, please correct me. (I got confused with your naming conventions)
1) Existing RFC : RFC-OLD (XI calls RFC_OLD)
2) Copy : RFC-OLD_Copy
3) : Delete the function code in RFC-OLD
4) : RFC-OLD Calls RFC-OLD_Copy
DATA: queue_name like TRFCQOUT-QNAME.
*setting the queue name
queue_name = 'DEBUG_QUEUE'.
 call function 'TRFC_SET_QUEUE_NAME'
 exporting
 qname = queue_name
 exceptions
 invalid_queue_name = 1
 others = 2.
 if sy-subrc <> 0.
 endif.
*call the new function in the background *and passing all the parameters from the old RFC! *so we'll be able to debug the RFC with correct *parameters
CALL FUNCTION 'RFC-OLD_Copy'
in background task
destination 'NONE'
as separate unit
TABLES
 TABLESAMPLE = TABLESAMPLE.
*remember about the commit work
Commit Work.
Endfunction.

Detect DEBUG mode in ABAP code

Hi all,
Is there a way to detect that we are in DEBUGGING mode in ABAP code.
I need to determine this, because we have function modules that will be runned in a separate process in the background. If i could detect DEBUG mode, i could choose not to run these modules in the background, making debugging them possible.
Regards,
Rob.

When you debug a program that calls function modules using the IN BACKGROUND TASK addition, they are processed in a background work process (additional internal session). If you set the In background task: Do not process option, the system collects the function calls, but does not start the background work process. The Debugger assigns a transaction ID, which identifies the background work process uniquely. You can now start the Debugger for the background work process using transaction SM58. You can select the function module concerned here, and then execute it via the Edit menu.
http://help.sap.com/saphelp_47x200/helpdata/en/c6/617d0ce68c11d2b2ab080009b43351/frameset.htm
There is a system variable SY-DEBUG, not sure if it works, though.
Regards,
Subramanian V.

Debugging RFC

I just rolled out a new app and can't get he RFC call to work.   The trace file shows:
---> RFC MESSAGE/ERROR : 104
RFC_ERROR_SYSTEM_FAILURE
CPIC-CALL: 'ThSAPCMRCV' : cmRc=20 thRc=456
Timeout during connection setup (check that partner exists)
So I did a bit of messing around in SM59. The ONLY thing I would change in SM59 was
the program being called. I changed the called program than ran connection test. All these Unix programs are owned by the same user and have the same rights.
/usr/sap/DEV/SYS/exe/run/tp -> worked OK
/usr/sap/DEV/SYS/exe/run/tf80server.csh -> timed out
copied 'tp' to 'tf80server.csh'
/usr/sap/DEV/SYS/exe/run/tf80server.csh -> worked OK
/usr/sap/DEV/SYS/exe/run/sapftp -> worked OK
copied 'sapftp' to 'tf80server.csh'
/usr/sap/DEV/SYS/exe/run/tf80server.csh -> worked OK
copied orignal tf80server.csh back
/usr/sap/DEV/SYS/exe/run/tf80server.csh -> timed out
The timeout doesn't seem to be consistant what whatever program I put in. I even created a short shell script (called vince.sh) that only had:
   echo "hi"
   exit 0
/usr/sap/DEV/SYS/exe/run/vince.sh -> timed out
BUT copied 'tp' to 'vince.sh'
/usr/sap/DEV/SYS/exe/run/vince.sh -> worked OK.
So I don't think it is a TaxFactory issue but an internal SAP/RFC
issue. I am unsure how to debug further.
Suggestions?
Thanks!
HP-UX 11.31 Oracle 11.2.0.2 SAP 7.00 Kernel 278 Basis Support Pack 22

Though I would still like to know how to further debug RFC turns out it is a BSI issue. The tf80server executable turned out to be the point of failure.

While debuging rfc I'm getting some problems..

HI Guys,
While Debugging RFC's, when passing values to parameters they are entering to BAPI Return,but for some values they are not entering to BAPI Return..
Its very Urgent..Please Rectify As soon as possible
With Regards
kirankp

Hi,
I guess this problem is specific to the BAPI which you are invoking remotely.
It might be giving different output returns on different inputs parameters.
Please provide more detail for making the problem more clear, if issue aint resolved.
Regards,
Tanveer.
Please mark helpful answers

DOS commands within ABAP

Please tell me how to execute DOS commands from within ABAP.

1.create your shell script your_shell_script.sh:
src=$1
dst=$2
mv -f $src $dst
2. Create your command Z_YOUR_COMMAND using SM69:
- Operating system command: /bin/sh (the path to your shell interpretator)
- Parameters for operating system command:
/home/sap/bin/your_shell_script.sh (the path to your shell script)
- Set "Additional parameters allowed" checkbox
3. Call your command from ABAP:
data:
param type sxpgcolist-parameters.
status type extcmdexex-status,
exitcode type extcmdexex-exitcode,
it_log type table of btcxpm.
p_src = '/common/home/edw/parsekb/b2/*'.
p_dst = '/common/home/edw/parsekb/b1'.
concatenate p_src p_dst into param separated by space.
CALL FUNCTION 'SXPG_CALL_SYSTEM'
EXPORTING
COMMANDNAME = 'Z_YOUR_COMMAND'
ADDITIONAL_PARAMETERS = param
IMPORTING
STATUS = status
EXITCODE = exitcode
TABLES
EXEC_PROTOCOL = it_log
EXCEPTIONS
NO_PERMISSION = 1
COMMAND_NOT_FOUND = 2
PARAMETERS_TOO_LONG = 3
SECURITY_RISK = 4
WRONG_CHECK_CALL_INTERFACE = 5
PROGRAM_START_ERROR = 6
PROGRAM_TERMINATION_ERROR = 7
X_ERROR = 8
PARAMETER_EXPECTED = 9
TOO_MANY_PARAMETERS = 10
ILLEGAL_COMMAND = 11
OTHERS = 99.
if sy-subrc <> 0.
*TODO: add your error handling logic
endif.

Trigger rfc from abap porxy

hi all;
how to trigger rfc from abap porxy

Hi Mehra,
check this link and just check for only how proxy is being used/...
https://websmp208.sap-ag.de/%7Esapidb/011000358700011142902001E/HOWTosendxmldatatobw.doc
And u can check one more document related to the above link in Services.sap.com (How to push data from BW to XI PDF)
If not Give me u r mail id i will forward it...
Regards,
sridhar
Message was edited by: sridhar reddy kondam

Debug subVI within RT executable

I have a startup executable VI for RT. However, there is a problem within a subVI of the startup VI. It only shows up in the executable version. Is there a way to debug subVIs within executables?

Hi faustina,
When you build your RT executable you can make it a debuggable. After you deploy it, you can choose Operate»Debug Application or Shared Library... from LabVIEW. This way you can use standard debugging tools.
On a side note, what problem are you finding with the subVI? Is it not running or just giving incorrect results?
Tanya V
National Instruments
LabVIEW Platform Product Support Engineer

Debug RFCs within ABAP

Similar Messages

Maybe you are looking for