ABAP proxy related issue

Hi All,
Good morning,
i working with ABAP proxy to file scenario. the requirement for this scenario is we are fetching data from data base to internal table then using that table we have to write code and send data to xi. can give me past response that how to write code using internal table. i want only code related internal table not total code.
thanks for fast response.
regards
sai

Hi Sai komala,
After genrating the Proxy, you can view the calss & structures genrated by proxy.You need to create an object with refrence of Class and to be create workareas for your Message type and Data type strucutres. Create an Internal table with your desired structure and do the validations as per your mapping rules.After completion of your all validations you need to populate your final internal table data to the structure of message type and call the execute asynchronous method.
Have a look into following weblogs
/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
TO debug u r proxy code, just like your normal R3 report program. put a breakpoint and execute the program , you can view the debugging of your proxy.
Hope it will helps to solve u r probolem
Cheers
Veera

Similar Messages

ABAP Proxy timeout issue

Hi,
I have a scenario in where I provide a web service. I get called by this web service and then call a abap proxy (synch). The abap side takes time to gather the data. after 600 secs, the connection gets a timeout.
It says, "500 Connection timed out"
"Detail: Connection to partner timed out after 600s"
In smicm I increased the HTTP value to 9000. So, how do I get this error?
Parameters are like below in PI:
icm/server_port_0 = PROT=HTTP,PORT=50000,TIMEOUT=90,PROCTIMEOUT=9000
icm/keep_alive_timeout (sec.) = 50
icm/conn_timeout (msec.) = 5000
xiadapter.inbound.timeout.default = 5400000

Hi,
Check if you are getting some short dumps in ABAP side due to this timeout in ST22.
Probably the issue is the work process time out in the ABAP side as you mentioned it takes more time to gather data. the profile parameter is rdisp/max_wprun_time and it has default value of 600 seconds. if thats the case then you can increas it.
regards,
francis

ABAP Proxy Authetication issue

Hi there,
we're currently integrating a rail order portal via ABAP Proxy technology. We've installed the corresponding interfaces witch package EA-HR602.
During test in SPROXY as well as testing from application the user is promted to enter login credentials for the PI system.
Has anybody any idea, how to configure this application? We did all the setup for proxy runtime, all test reports are running well.
Please help, this issue prevents our go-live. Help is highly aprreciated and will be rewarded.
Cheers,
Matthias

Hi Kral
Check the link given by Sarvesh
Check your configurations with the blog. Moreover did you tried giving PISUPER as the user for RFC destination and test it again.
IF change of user works then you need to revisit the roles of the user you have.
Thanks
Gaurav

ABAP Proxy authorization issue when sending message.

Hi
We have an interface which uses ABAP proxies. This is used to send a message with attachment, but when i send the message I am getting a 401 error message which says unauthorized.
I checked all the configs on the sending side and i cant fine anythin wrong. I tried SLDCHECK and all looks fine there as well. I have done the configuration in the Integration engine on the sending side as mentioned in the BLOG - Activating ABAP Proxies.
We have 3 XI systems Dev, QA and Prod sharing the same SLD. The configs that we have on the sending system (App Sys.) is given below.
SM59
HTTP connection : SAPISU_XID
Host : XI Dev hostname Service Number 8080 (80 <sys number>)
Path Prefix : /sap/xi/engine?type=entry
USER : XIAPPLUSER
The TCP/IP connections LCRSAPRFC and SAPSLDAPI are also setup on the system which connects to our SLD.
The TCP/IP connections works fine and i am able to test it succesfully, but the HTTP connection fails with an authorization error (401) when i test it. Now the wierd thing is if I use XIAFUSER instead of appuser it works fine, but if i make a copy of XIAFUSER and try that... It fails again.. I know it sounds strange. So i was wondering if there is any setting on XI which restricts HTTP connections to a particular user??
I would really aprpeaciate if you could please give me your thought on this issue...
Cheers
Prav

Hi Manish
Thanks for the input again.
I checked SICF on the XI system and its not set to any user.
The HTTP connection on out prod environment is working fine without any issues and its uses a user which is a copy of XIAPPLUSER. SICF in prod also does not have any user configured for service SAP\XI\Engine.
Thanks for the link, had a look at it, but It looks like these users mentioned are only available with XI7. Our server was upgraded from 3 to 7 and I am not able to find these users on the system.
I tried testing the HTTP connection in prod using a diffrent user and found its the same story there. If i use any use other than the cutom one.. it fails.. could there be any setting in the exchage profile that can affect this??
Thanks for your time and help.
Prav

Issue in Iodc- abap proxy scenario

Hi all
I have a idoc to abap proxy scenario. The issue is ,
when we send the idoc to client A of target system, it works ifne.
But when we send the saem mesage to Client B, we find a error message in sxmb_moni of Target system. the mesage is Application_fault.
Is it because of any error in XI configuration or somethin else.

hi all
thanks for all your responses.
I forgot to mention that based on a particualr field value in the idoc , it will be routed to eihter Client 100 or 200 .
I gave the conditions in Receiver Determination.
Same Server Proxy is used in both the target business sytems.
I have done all the Configuration Steps ,( Created two separate business systems also )
Also I have checked wiht all the system settings to be made in the target system B.
When i trigger the idoc to Client 100, it goes to XI and then reaches Client 100 of System B
without any problem. I get the desired result from proxy code.
When i send the saem idoc to Client 200, it reaches the target system and routed to client 200. But getting this error message in
the Call Inbound PRoxy step. (from sxmb_moni)
<SAP:Category>Application</SAP:Category>
<SAP:Code area="ABAP">APPLICATION_ERROR</SAP:Code>
Since it reaches the target system correctly, i guess there is nothing wrong in the XI configuration side.
But if its Application fault, how come the same data is processed successfully in one client whereas it thorws error in another.

Issue with inbound abap proxy

I have an Inbound ABAP proxy scenario , the ABAP code inserts data into a ZTable.
I am having an issue in the runtime where
1. I see transaction data in SXI_MONITOR of both XI & application system.
2. if tried to debug with the report SPRX_TEST_INBOUND (as the application system WebAS is 6.20) the proxy code works just fine, and records are inserted in the ZTable.
records are not getting inserted into the table when run end to end..anybody faced this situation ?
Appreciate genuine replies....

Hi,
but this just has to work
if this doesn't work then "something realy strange is going around here"
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Consume WSDL in ABAP proxy : Issue with name space

Hi,
I was trying to consume a WSDL in ABAP and I have created ABAP proxy using wizard in SE80 and also did the LPCONFIG.
While calling the proxy methods it is throughing the "authrization failed" error because of the following issue.I have successfully executed same WSDL from some third party tools with out error.only difference I have observed in SOAP request is, Third party tools passing all name spaces at envelope level but in ABAP proxy it is not passing all name spaces at envelope level.
1. SOAP genarated from WSDL in third party tool.
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://schemas.xxxxx.com ">
<soap:Body>
 <tns:GetKMContent>
 <tns:request>
 <tns:clientID>1</tns:clientID>
 <tns:employeeID>307478</tns:employeeID>
 <tns:languageCountryCode>en-US</tns:languageCountryCode>
 <tns:wscVariables>
 <tns:empcountry>US</tns:empcountry>
 </tns:wscVariables>
 </tns:request>
 </tns:GetKMContent>
</soap:Body>
</soap:Envelope>
SOAP genarated from WSDL in ABAP proxy.
<soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">
<soap-env:Header>
<n0:Trace xmlns:n0="http://www.sap.com/webas/630/soap/features/runtime/tracing/">
<TraceLevel xmlns="http://www.sap.com/webas/630/soap/features/runtime/tracing/">Full</TraceLevel>
</n0:Trace></soap-env:Header>
<soap-env:Body>
 <nr1:GetKMContent xmlns:nr1="http://schemas.xxxxx.com ">
 <nr1:request>
 <nr1:clientID>1</nr1:clientID>
 <nr1:employeeID>307478</nr1:employeeID>
 <nr1:languageCountryCode>en-US</nr1:languageCountryCode>
 <nr1:wscVariables>
 <nr1:empcountry>US</nr1:empcountry>
 </nr1:wscVariables>
 </nr1:request>
 </nr1:GetKMContent>
</soap-env:Body>
</soap-env:Envelope>
I was trying to use the SOAP genarated in ABAP proxy in thrid party tool and end up with same "authrization failed " error. If I move the name space nr1 from <nr1:GetKMContent xmlns:nr1="http://schemas.xxxxx.com "> GetKMContent node to soap-env:Envelope <soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:nr1="http://schemas.xxxxx.com "> then it is working fine.
Question :Is there any way in ABAP proxy to pass name space at soap-env:Envelope level or is there any way to change the SOAP request once it is genarated from ABAP Proxy?. Is there any API to change SOAP information?
Thanks,

Hi Kavitha,
I am also facing the same issue.
Could you please share the solution if you have solved this.
Thanks,
Arun

Issues with ABAP Proxy in XI 3.0

Hi,
We are on XI 3.0. We are doing a scenario of file >XI> R/3 (ABAP Proxy).
The XML message is going to R/3 with no errors as indicated in the monitors on both XI and R/3. The XML messages has the status of 'Message Processed'. But, the proxy never gets executed. Is there a step I must perform to execute the Proxy? My understanding is that if the Receiver Communication Channel is of XI type, it will automatically execute the Proxy on the R/3 (receiving) system.
We tested the proxy using the report SPRX_TEST_INBOUND, and it works as expected.
Please advise.
Thanks in advance.
Best Regards,
Doo

Hi Doo,
how do you know, that the proxy was not called?
If you are missing database updates, check if you have a commit work in the code.
Regards
Stefan

ABAP Proxy and commit issue

Hi,
I want to send data using an ABAP proxy from SAP ECC to PI.
The location where I call the method is in MV50AFZ1 Form uxerexit_delete_document
In my opinion it is not wise to execute a commit work statement in this location. The proxy however needs a commit work to send the data.
I also tried using a CALL FUNCTION ... IN UPDATE TASK. This also doesn't trigger the proxy to send the data.
(and it is not allowed te execute a commit in update task .. .because it's already a "commit".
Is there a way to get this thing working in this way? Or do you always have to program a separate program for sending the data with a proxy??
Thanks
Ron

Hi Ron,
Try submitting a report as a background job from the user exit...and inside this report you can write the code to call the proxy + commit.
*Submit report as job(i.e. in background)
data: jobname like tbtcjob-jobname value
' TRANSFER TRANSLATION'.
data: jobcount like tbtcjob-jobcount,
host like msxxlist-host.
data: begin of starttime.
include structure tbtcstrt.
data: end of starttime.
data: starttimeimmediate like btch0000-char1.
Job open
call function 'JOB_OPEN'
exporting
delanfrep = ' '
jobgroup = ' '
jobname = jobname
sdlstrtdt = sy-datum
sdlstrttm = sy-uzeit
importing
jobcount = jobcount
exceptions
cant_create_job = 01
invalid_job_data = 02
jobname_missing = 03.
if sy-subrc ne 0.
"error processing
endif.
Insert process into job
SUBMIT zreport and return
with p_param1 = 'value'
with p_param2 = 'value'
user sy-uname
via job jobname
number jobcount.
if sy-subrc > 0.
"error processing
endif.
Close job
starttime-sdlstrtdt = sy-datum + 1.
starttime-sdlstrttm = '220000'.
call function 'JOB_CLOSE'
exporting
event_id = starttime-eventid
event_param = starttime-eventparm
event_periodic = starttime-periodic
jobcount = jobcount
jobname = jobname
laststrtdt = starttime-laststrtdt
laststrttm = starttime-laststrttm
prddays = 1
prdhours = 0
prdmins = 0
prdmonths = 0
prdweeks = 0
sdlstrtdt = starttime-sdlstrtdt
sdlstrttm = starttime-sdlstrttm
strtimmed = starttimeimmediate
targetsystem = host
exceptions
cant_start_immediate = 01
invalid_startdate = 02
jobname_missing = 03
job_close_failed = 04
job_nosteps = 05
job_notex = 06
lock_failed = 07
others = 99.
if sy-subrc eq 0.
"error processing
endif.

Issue with ABAP Proxy

Hi,
My scenario is SAP(ABAP Proxy) - XI - Web service. I can not see any messages in XI when I run the Proxy program, when I check for the outbound messages from SXMB_MONI in SAP system the message status is "Scheduled" and Q.Status shows "Message waiting in Queue" . What could be the message status if the outbound proxy is successful?
Can someone let me know what could be the problem and where I can check for entire scenario for these problesm?
Thanks
Suresh

Hi,
If this is not a Production System means,
goto SMQ2 and delete all the Strucked Messages in all the Queues.
And now goto SMQR say De-Register Queueus and
goto SXMB_ADM--Manage Queues--Just say Register Queues
Now Trigger your Report Program to send the data to XI.
Check in R/3 side as well as in Xi side also in the T-code SXMB_MONI for Successfully processed messages.
REgards
Seshagiri

How to Handle BARCODE related issues in WebDynpro ABAP

Hi All,
How to handle barcode related issues in WDA?
is it possible in WDA or not?
please provide information or any links related..
Thanks,
raj.

Hi ,
You just need to install the software comes with the barcode scanner in the local PC and while reading you have to put the cursor on the field like inputfield . a barcode when interpreted by scanner is nothing but alphanumeric words.
Regards
Yash

Abap Proxy Issues

Hi there, Iu2019ve been struggling with abap proxies the last couple of daysu2026 I want to create a program that executes the proxy and send thru some data via an internal table. (To another proxy on the same system but a different client.) Iu2019ve checked out the client/server proxy blog but it only shows some of the configuration. Is there may-be a complete step by step? How do I check if the RFC destinations are setup correctly? I have created scenarios for this but every time I check it in the sxmb_moni it shows a green flag and cannot find a receiver service..
Thanx,
Jan

have u refer the below links.
ABAP Proxy configuration:
How do you activate ABAP Proxies?
Client Proxy -
ABAP Proxies in XI(Client Proxy)
Server Proxy -
ABAP Server Proxies
File to Inbound Proxy:
File to R/3 via ABAP Proxy
Debugging Inbound Proxy:
XI: Debug your inbound ABAP Proxy implementation
chirag

Issue with FM 'STATUS_CHANGE_EXTERN' using ABAP Proxy

Hi Experts,
I am using the FM 'STATUS_CHANGE_EXTERN'   & 'STATUS_CHANGE_INTERN' to change the user status & system status using ABAP Proxy.
But SAP is updating the system status using ABAP Proxy through ''STATUS_CHANGE_INTERN'' but not updating the User stauts 'STATUS_CHANGE_EXTERN' using ABAP Proxy but when run the same in foreground then it's working fine..
I have already used the External Commit for the same.
Please help me in this case.
Thanks in Advance
Sachin

After call of CRM_STATUS_CHANGE_EXTERN you need to call BAPI_TRANSACTION_COMMIT.
call function 'CRM_STATUS_CHANGE_EXTERN'
    exporting
        objnr               = iv_guid
        user_status         = iv_status
    exceptions
        OBJECT_NOT_FOUND    = 1
        STATUS_INCONSISTENT = 2
        STATUS_NOT_ALLOWED = 3
        OTHERS              = 4
if ( sy-subrc = 0 ).
    call function 'BAPI_TRANSACTION_COMMIT'
        exporting
            wait = ABAP_TRUE
else.
    "!+ Handle error
endif.
Best regards,
Tomas.

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 Errors

Hi Experts,
My scenario R/3->XI(ABAP Proxy)--->SUS Systems
Getting the following error in SUS system.XI system it doesn't throw any error in moni.
I am new to proxy concepts.Also please let me know any related blogs or suggestions in this regards.
<?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">DYNAMIC_CALL_FAILURE</SAP:Code>
<SAP:P1>UNCAUGHT_EXCEPTION</SAP:P1>
<SAP:P2>CL_BBPX1_SUSIV_IN</SAP:P2>
<SAP:P3>EXECUTE_ASYNCHRONOUS</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error during proxy processing An exception with the type CX_BBPX1_STD_MESSAGE_FAULT occurred, but was neither handled locally, nor declared in a RAISING clause Application Error</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Thanks,
Sudhansu

Hi Behera,
Can you debug your proxy using this blog:
/people/stefan.grube/blog/2006/07/28/xi-debug-your-inbound-abap-proxy-implementation
https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/502a7f0e-e5d9-2910-5aa2-976a8ed8384f&overridelayout=true
Also please check few solutions given in this threads for the same issue:
Re: Messages waiting in SUS Moni
Re: ABAP Inbound Proxy Error !
Regards,
---Satish

ABAP proxy related issue

Similar Messages

Maybe you are looking for