How to debug the BADI - BBP_CREATE_BE_RQ_NEW

Hi Experts,
Help me how to debug the BADI in order to validate my coding.
I have put a break point in the BADI and run the class CL_BBP_SC_TRANSFER_CLASSIC Instance DO by giving the SC no and the GUID but still the BADI is not getting triggered.
Suggest me any other way to debug the BADI.
Regards
Paul

Hi,
You can put an endless loop in your BADI BBP_CREATE_BE_RQ_NEW ,as shown below and force the program to stop there. Now go to SM50 and switch to debug mode for the program and start debugging(take process that keeps hangs in your endless loop).
Data: l_flag.
do.
if l_flag eq 'X'.
exit.
endif.
enddo.
BR,
Disha.
DO reward points for useful answers.

Similar Messages

How to debug the background job in ABAP

Hi Guys,
Can anyone let me know how to debug the background job in ABAP.
Thanks in advance
peter

Hi,
Goto SM37 and see the log if any is there and based on that you can check the code.
you can't debug background job.
Create a Variant for the Program and
Schedule JOB in background:
Go to SM36 create a Job
enter Program and Variant for that program in STEP..
click on Start Condition
Click on DATE and TIME enter date scheduled Start and END times
click on Period Values
Click on HOURLY/WEEKLY etc
CLick on RESTRICTIONS also to use further criteria.
so your job will be scheduled and run as per your requirement.
and in SM37 Transaction check the status of that JOB
Check this link for scheduling jobs..
http://help.sap.com/saphelp_nw2004s/helpdata/en/c4/3a7f87505211d189550000e829fbbd/content.htm
Check this
http://jplamontre.free.fr/SAP/Debug%20background%20process.htm
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/abap/abap+debugger&
Regards,
Padmam.

How to find the BADI'S in Web Dynpro ABAP

Hi Experts,
I'm new to Web Dynpro ABAP. Can any one tell me, how to find the BADI'S for standarad components like i.e DEMO_ROADMAP .Please tell me, steps/procedure to find the BADI'S in WDA.
Thanks ,
Chaitanya
Moderator message: wrong forum, please have a look in the "Web Dynpro ABAP" forum.
Edited by: Thomas Zloch on Jun 18, 2011 4:30 PM

Hi Nagaraju,
There is another fool-proof method to find BADIs while executing a transaction -
1. Goto transaction SE80
2. Select "Class / Interface", type in the class name CL_EXITHANDLER and 'Enter"
3. On the method GET_INSTANCE, create a Breakpoint just after the call to cl_exithandler=>get_class_name_by_interface at the following line -
<i>CASE sy-subrc.</i>
Once the breakpoint has been set, call the transaction you wish to find the BADI for and you will notice that the debugger opens everytime a BADI is about to be called. You could get the name of the BADI from the the value of the variable "EXIT_NAME".
CL_EXITHANDLER is a service class that is called by standard SAP code everytime a BADI is about to be called. So, setting a breakpoint here should let you know exactly which BADIs are called.
Hope this helps!
Thanks,
Rohini.

How to debug the report which isrunning in Background?

Hi all,
1.How to debug the report which is running in Background?
thanks & regards
vishnuvardhan

Hello,
Do like this.
Create an infinite loop before the line u want debug.
data: lf_flag.
do.
if lf_flag = 'X'.
exit.
endif.
enddo.
Now execute the report in background. In Tcode SM37 select ur job and in menu job--> Capture Active Job
IT will stop at the point of infinite loop.
Regards,
Vasanth

How to debug the method in abap program

How to debug the method in abap program ?
Could you please give the solution.
Thanks
sai

Hi ,
Place break point at call method .
It takes u in to the method implementation .
Here u can analyse the method implementation ...
Reward if useful
Thanks
Jagadeesh.G

How to debug the routines in the transformations as well as start,endroutin

Hi all,
Can anyone explain me how to debug the routines in the DTP, as well as the how to debug the start and end routines>?
I am new to bi 7 ?
thanks
Pooja

Hi,
In Execute tab change the processing Modes to 'serially in the dialog process for debugging' . then you can see the option 'simulate'.
http://help.sap.com/saphelp_nw70/helpdata/en/45/8594ebd17f1956e10000000a11466f/content.htm
Step by step doc,
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b0038ad7-a0c7-2c10-cdbc-dd674682c8e7?quicklink=index&overridelayout=true

LSMW VD51 , Validations in Begin of Transaction; how to Debug the code?

Hi All,
I have written code for validations i Begin of Transaction in the field mapping 5th step of LSMW for VD51.
Now this code not getting triggered at the time of Conversion of Data. How to debug the code. I have put a static break point 'BREAK-POINT' still not getting triggered.
Any suggestion / solution for this issue.
Thanks and Regards,
Narsimha Kulkarni

Hi Narshimha,
Make any mapping error during mapping and check the syntax of mapping it will drag you to the lsmw report there you can put your break point. You can check the report name from transaction code as well.
Remember this mapping block will execute when you execute the step Convert Data in LSMW.
Regards
Dhirendra

How to debug the update FM

Hi,
I am facing a problem with the debugging of the update FM. I have enabled the update debugging and the system says that update debuging is on . even though the control did not go into the FM.
Do i need to check in any other transaction . Please give me the details steps on how to see the what is happening in the update FM.
Full marks are guaranteed.
thanks
sankar

Hi
I have got a clue from SAP help on how to debug the update FM see the below information from SAP
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.
I have done everything that is said above , but could not find any entries in SM58
any suggestions
thanks
sankar

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 the Outbound IDOC

Dear SDN Members,
How to debug the outbound idoc please.
Thanks in advance
Yerukala Setty

Hi,
IDocs are processed by a function module, which are mapped against in table EDIFCT. When you process an IDoc in transaction BD87 you can put a breakpoint in the function module and it will stop there.For outbound processing it depends on which program is sending the IDoc. For transactional data like purchase orders, the IDoc is created via RSNAST00 which in turn calls a function module assigned to the processing code (BD41).
Thanks,
Asit Purbey.

HI how to debug the whole SC creation process

Hi
I need small help from all you great guys.
I am working with EBP application.
I want to know the process of creation of shopping cart to the creation of PO in the r/3 system.
How to debug the whole process. I can create a shopping cart in the EB web. I want to know what is hapening in the backend during the creation of shopping cart.
I know the web transaction for the creation of the shopping cart. I tried to debug the process by going SE80 and giving the web transaction , but it is very cumbersome process and i was confused. Is there any way i can know what is happening in the backend and how the SC data is transferred to the bacend and how PO is created in the R/3 system
sankar

Hi Sankar Rao
we can debug the shopping cart from sap GUI via tran. /nBBPSC01
1 Click on internal Goods/services and select the product for which you want to create a SC and press enter.
2 In command window input /h and press enter
3 Click on the button Order it will go in debug mode.
4 Insert break points on Statement - Select
5 Insert break points on Statement - Insert
6 Insert break points on Statement - update
and press F5 key to move one step ahead and F8 key to halt directly at each break point.This way go upto the save mode and order your SC at run time in debug mode.
regards,
Nimish Sheth
NB Do rewards points for helpful anwsers.

How to handle the bad record while using bulk collect with limit.

Hi
How to handle the Bad record as part of the insertion/updation to avoid the transaction.
Example:
I am inserting into table with LIMIT of 1000 records and i've got error at 588th record.
i want to commit the transaction with 588 inserted record in table and log the error into
error logging table then i've to continue with transaction with 560th record.
Can anyone suggest me in this case.
Regards,
yuva

>
How to handle the Bad record as part of the insertion/updation to avoid the transaction.
>
Use the SAVE EXCEPTIONS clause of the FORALL if you are doing bulk inserts.
See SAVE EXCEPTIONS in the PL/SQL Language doc
http://docs.oracle.com/cd/B28359_01/appdev.111/b28370/tuning.htm
And then see Example 12-9 Bulk Operation that continues despite exceptions
>
Example 12-9 Bulk Operation that Continues Despite Exceptions
-- Temporary table for this example:
CREATE TABLE emp_temp AS SELECT * FROM employees;
DECLARE
TYPE empid_tab IS TABLE OF employees.employee_id%TYPE;
emp_sr empid_tab;
-- Exception handler for ORA-24381:
errors NUMBER;
dml_errors EXCEPTION;
PRAGMA EXCEPTION_INIT(dml_errors, -24381);
BEGIN
SELECT employee_id
BULK COLLECT INTO emp_sr FROM emp_temp
WHERE hire_date < '30-DEC-94';
-- Add '_SR' to job_id of most senior employees:
FORALL i IN emp_sr.FIRST..emp_sr.LAST SAVE EXCEPTIONS
UPDATE emp_temp SET job_id = job_id || '_SR'
WHERE emp_sr(i) = emp_temp.employee_id;
-- If errors occurred during FORALL SAVE EXCEPTIONS,
-- a single exception is raised when the statement completes.
EXCEPTION
-- Figure out what failed and why
WHEN dml_errors THEN
errors := SQL%BULK_EXCEPTIONS.COUNT;
DBMS_OUTPUT.PUT_LINE
('Number of statements that failed: ' || errors);
FOR i IN 1..errors LOOP
DBMS_OUTPUT.PUT_LINE('Error #' || i || ' occurred during '||
'iteration #' || SQL%BULK_EXCEPTIONS(i).ERROR_INDEX);
DBMS_OUTPUT.PUT_LINE('Error message is ' ||
SQLERRM(-SQL%BULK_EXCEPTIONS(i).ERROR_CODE));
END LOOP;
END;
DROP TABLE emp_temp;

How to debug the workflow

dear friends,
please tell me how to debug the workflow, if you have time then you just see the workflow WS99900212 . in this i have done Leave Approver Notification . but i want to debug on that how to flow step by step .
please you tell me on same workflow , where i am going to take breakpoint.
Thanks in Advance for help.
Cheers.
Puneet.

You can try first of all to enable more logging. (I assume you are running release ERP 2005 since you are not saying what your release is.)
In the workflow builder, select menu item "Goto", "Basic data"
Select the "Version-dependent (current workflow version)" tab
Select the "Control" tab within the version-dependent subscreen
Select the "Performance optimization" tab within the control subscreen
Change the "Settings" drop-down value to "No restrictions on logging".
That will give you much more information in the workflow log. The description of this choice says "All the messages are logged. All runtime operations can be traced." As also noted: don't keep this setting in a production system.

How to debug the function separately which is added in the package

Hi Friends, I want to know how to debug the function separately, by taking it from package,. and i dont no where to add begin and end. and dont no how to give input to the function. ANd how to find the error which is detected from production, so i want to find from which statement its failing. So please guide me to proceed further. thanks in advance.

{ FUNCTION fn_get_trail_id (p_incr PLS_INTEGER DEFAULT 1) RETURN PLS_INTEGER IS
p_trail_id tb_xop_orders_trail.trail_id%TYPE;
BEGIN
IF p_incr >= 1 THEN
SELECT sq_xop_trail_id.NEXTVAL INTO p_trail_id FROM DUAL;
RETURN p_trail_id;
ELSIF p_incr = 0 THEN
SELECT sq_xop_trail_id.CURRVAL INTO p_trail_id FROM DUAL;
RETURN p_trail_id;
END IF;
END;
-- $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
BEGIN
ppr_openlog('AQ');
ppr_request_lock(v_cb_handle, v_cb_lock);
pr_xop_log_errors('AQ: ==== cb started ('||descr.msg_id||') ====');
my function is like this, how i can i in clude it in declare statement, and how to assign values for that.. and where i have to include "begin".plz help me

How to Debug the Failed Data loads?

Hi..All
Can Any one plz explain How to Debug the different types of Failed Data Loads?
Thanks & Regards
Jonn

Hi Jonn,
If any data failed ....1st analyze where it occurs according to that what we have to decide...
Analysis:
1.Check the Status Tab in RSMO--here we can get error information
2.Check the Details Tab in RSMO--here we can get whether extraction is completed,and where it is exactly failed i.e while updating from PSA or in Update rules etc
3.Check the corresponding request job log in SM37.
4.Check whether any shortdump in ST22.
5.Check the Request status in the Target...some times activation job failed in SM37 but in the Target we found as activated.
6.Check BD87 Transaction for any IDOC errors.
7.Check SM58 for TRFCs
Hope this helps u.....
Mohan

How to debug the BADI - BBP_CREATE_BE_RQ_NEW

Similar Messages

Maybe you are looking for