Forms Debugging

Help!
I have a number of procedures/functions that I have placed into a package within my Form.
In my package I also have a number of variables defined to allow data to be accessed/shared between procedures without requiring lots of parameter passing.
I have now come to debugging the code and it appears there is no way to view the current values of any package level variables. I can only see local variables in function call stack or forms :GLOBAL. variables.
How can I see the values of package variables when debugging?
Do I really have to resort to putting MESSAGE commands throughout my code?
Any help is gratefully received!
null

I'm not sure but I remember having used Forms debugger to trace the current value in a specfic variable during runtime.

Similar Messages

  • AR FORM 에서 DEBUG LOG 생성하는 방법

    제품 : FIN_AR
    작성날짜 : 2006-05-24
    AR FORM 에서 DEBUG LOG 생성하는 방법
    ============================
    PURPOSE
    AR 의 주요 Form 에서 문제가 발생했을 경우 Debug log 를 발생 시켜 확인 할 수 있도록 한다.
    Explanation
    Debugging을 제공하는 주요 AR Forms:
    Transactions workbench (ARXTWMAI)
    Receipts workbench (ARXRWMAI)
    Collections (ARXCWMAI)
    단, ARXCUDCI Form 은 해당 하지 않는다.
    Debug Setup 순서
    주의)
    만약 11.5.9 이상의 경우라면
    <AR: Enable Debug Message Output> Profile 이 user level 에서 enable 되어 있어야 한다.
    11.5.10 이면서 ARP_STANDARD (ARPLSTDB.pls) Version이 115.36이며 아래와 같이 작업 한다.
    To turn on the debugging:
    Set the following profiles:
    FND: Debug Log Enabled = YES
    FND: Debug Log Filename = NULL
    FND: Debug Log Level = STATEMENT (most detailed log)
    FND: Debug Log Module = % or ar% or even ar.arp_auto_rule%
    만약 11.5.10 MAINTENANCE PACK (Patch 3140000) 을 적용한 경우라면
    <FND: Debug Log Enabled> 이 <FND: Log Enabled> 로 그리고
    <FND: Debug Log Level> 가 <FND: Log Level> 로 대체 될 것이다.
    1. 문제가 발생한 Form 에 접속하여 문제 재현을 시작 한다. 문제가 발생하기 직전 까지 진행 한다.
    2. menu에서 help/diagnostic/examine 을 Click 한다.
    3. Block LOV 에서 PARAMETER 를 선택한다.
    4. Field 란에는 AR_DEBU_FLAG 를 직접 입력한다.
    5. Value 에는 다음과 같이 입력한다.
    FS <path> <file>
    FS 와 patch, file 사이에는 반드시 blank 가 있어야 함을 명심한다.
    a)
    FS
    FS creates a file, displaying Forms and Server debug messages.
    b)
    <path>
    This is where the AR Debug Log file will be written to.
    To find out where the log file must be saved, type the following in
    SQL*Plus:
    select value from v$parameter
    where upper(name) = 'UTL_FILE_DIR';
    c) Decide what to call the debug log file. For example, debug2.dbg
    If the file specified already exists, the new debug messages will be
    appended to it. In general, it is recommended to define a new debug file for each problem reported.
    d)
    Full example:
    Block: PARAMETER
    Field: AR_DEBUG_FLAG
    Value: FS /sqlcom/log debug2.dbg
    위와 같이 작업 한 후 Error 가 나도록 재현 한다.
    생성된 debug log 를 확인 한다.
    Example
    N/A
    Reference Documents
    Note 152164.1 -- How To Create A Debug Log File In An AR Form

    Nope

  • Forms debug not working in 11g. Working fine in 10g

    I am able to attach the debug of runtime with the random port number, but not stopping at the breakpoints. This is happening in 11g environment.
    Same method is working in 10g environment. What additional configuration do I need to do to run a form in debug mode in 11g environment.
    My configuration is here.
    1. in env file, I have the debugger.jar added to Classpath
    cusm.env
    CLASSPATH=...;....;....;C:\Oracle\Middleware\Oracle_FRHome1\jlib\debugger.jar;...;...;
    FORMS=C:\Oracle\Middleware\Oracle_FRHome1\forms
    2. formsweb.cfg
    debug=no
    # Forms runtime argument: host for debugging
    host=
    # Forms runtime argument: port for debugging
    allow_debug=false
    [cusm]
    workDirectory=/oracleias11g/work
    envfile=cusm.env
    form=frm_main.fmx
    userid=@orcl
    lookAndFeel=oracle
    pageTitle=Development 11g
    width=1050
    height=800
    archive=frmall.jar,customicon.jar
    At runtime from the form
    debug.attach;
    Then in the forms designer
    Debug-->Attach Debug
    Enter the random port number and the server and enter.
    Create couple of breakpoints in the forms trigger.
    and press button in the form.
    Now control is expected to come to forms designer, but not stopping at breakpoints.
    When Stop debug from forms designer, the runtime session is ending.
    Please help.
    Thanks in advance,
    Ravi

    Assuming you connected to the running form successfully, it sounds like your breakpoint is not being called. In other words, if you put a breakpoint in a trigger that isn't firing then the break will never occur. A simple test would be to add a break in the WHEN-NEW-FORM-INSTANCE trigger. Since this trigger cannot be avoided, control will quickly be passed to the debugger at startup. If this works then you can assume what I mentioned, which is that your other breakpoints are not being reached.
    Just to be sure, I just tested the Debugger in Forms 11.1.2.1 on Windows and it appears to work correctly.

  • Form debugging - Which line is causing the error?

    I have a form that I'm working on, and when I run the form like normal, just as the end user would, I keep getting an error, "FRM-41039: Invalid Alert ID 0." I can't figure out where this error is coming from in my code. It seems that it must have something to do with timing, because in trying to track down the error, when I run the form in debug mode, obviously the timing is slower as I go line-by-line in the code to see which line may be causing the error, but when I do that, I don't get the same error. I'm not close to being an expert when it comes to design-time debugging in forms, and I was wondering if someone with more experience could point me in the right direction. Is there any way that I can somehow determine which line of code is causing this error to raise? If I could identify the line of code, I could maybe find out which alert it's looking for, right? Then I could maybe narrow down the problem a bit more. Anyone have any ideas? Thanks in advance.
    YEX
    <)))><

    Like it says :"FRM-41039: Invalid Alert ID 0." Alert does not exist. So try to find line in your code which contain something like:
    Show_Alert("<name of alert>")
    Or Alert with this name dows not exist or you are misspelling the name of existing Alert.

  • Forms DEBUG - help

    Hello all.
    I need to debug a list of forms which are running in a remote server. Because of the setup we have, i can not run them in the developer tool. I need to test them using the web based environment we have installed. I used to enable the debug mode in windows by adding the clause "/debug". I tried adding this in the web address that's calling the forms, but it didn't work. Could you please help me out?
    Thanks in advance.

    what do you mean when you say that i also attach my linux run form with Windows Forms builder?
    I use windows forms builder just to make the make the changes i need. Because of the nature of the forms, i can neither run nor compile them in windows.
    What i do, is to upload them to our linux server, compile them with a script i run from the command line, and move the fmx to the right folder. That's how i'm able to run them, otherwise i can't. If i try to run them in windows it raises an error message saying there's no http listener running in my local box...
    On the other hand, I tried to run them using the "DEBUG=YES" flag, but nothing happened. I used to work with forms 4.5, and at that time, when i wanted to debug a form i just made a shortcut with that same flag. Something like: "F45RUN.EXE formname.fmx /debug=yes", so, I tried something similar in this case...
    The URL I use to run the forms is "http://as4.ajc.bz:8889/forms/frmservlet/atisweb". I added the flag you mentioned at the end. Something like "http://as4.ajc.bz:8889/forms/frmservlet/atisweb debug=yes"... but it didn't work.
    Any other ideas?

  • Smart forms debugging

    Hi experts,
    Any body pls explain how to debug smartforms ?
    Is it necessary to write print program for smart forms ?

    Hi,
         In the Smartform, within the Code Node you can hardcode a normal abap Break Point ..
    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.
    Other 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.
    or
    SFTRACE can be used for debugging SMARTFORMS.
    Read More here.
    http://help.sap.com/saphelp_erp2004/helpdata/en/49/c3d8a4a05b11d5b6ef006094192fe3/frameset.htm
    See the Below thread for how to debug the Smartforms
    How to Debug Smartform?
    Re: debug of smartfrom
    Smart forms
    Thanks
    Nayan

  • Developer 2000 form debug problem

    Hi,
    I am trying to debug one form which is in Developer 2000 forms (too old). But for this specific form, when i am setting debug point and start debugging form exits instantly. This is happening with specific one form. Anyone please help me out.
    Thanks in advance.

    Did you try setting the breakpoint at a different position, maybe even a different trigger?

  • Online forms debugging

    Hello,
    We have an application running on Oracle database 9205 connected through forms 4.5 in the front end
    on numerous occasions the application throughs up error messages on screen or in the task bar.
    Our development team is located across a distance and hence problem resolution takes considerable time resulting in serious loss of bussiness
    I would like to know if there is some way wherein runtime forms can be debugged so that the problem resolution can be faster locally
    we do not have the fmb's for the corresponding fmx's.
    please provide some way out.
    Altaf

    Well I'm in a similar situation, where I have sometimes not a SQL*Net connection to the database host of the customer so I can't debug the fmb's locally (customer has only fmx) or transferring the fmb's to customer and installing devsuite there would simply be...not an option.
    I use SQL Monitor from Toad for watching the SQL Statements issued by the forms runtime for this or simply trace the sessions. Additionally we implemented a logging, where I put the log messages at design time which are ignored by default, and when setting a flag I get the whole debug infos...
    Additionally I found this http://log4plsql.sourceforge.net/ some time before...maybe this could make your work a little bit more easy ;)
    regards

  • 11G worklist forms debug?

    Someone knows how to do a debug of a human task form in SOA-BPEL 11G?

    You can use Remote Debuging to debug your Human Task application from JDeveloper. To do this, you'll need to enable remote debugging in the WebLogic server where the Human Task is deployed (typically a managed server). The setDomainEnv.cmd (located in [Oracle Home]\Middleware11gR1\user_projects\domains\[your domain]\bin) looks at the environment variable "debugFlag" to determine if remote debugging should be enabled. However, setDomainEnv also sets debugFlag=false if "nodebug" is passed as a parameter. I mention this because startManagedWebLogic.cmd passes nodebug when run without any parameters passed in. Therefore, you'll probably need to modify your start scripts such that debugFlag=true for the server hosting the Human Task (e.g. managed server) and not any other server (i.e. admin server). Once remote debugging is enabled in WebLogic, you need to configure JDeveloper to use remote debugging. This is a fairly simple process where you just need to enable remote debugging in the run/debug/profile. With remote debugging enable in your JDeveloper project, you can right-click on the project and select "Start Remote Debugger". If everything is configured properly, any breakpoints you've set will be hit.
    Edited by: jwoodard on Feb 18, 2010 10:56 AM

  • Smart form debugging

    how to debug a smart form

    Hi,
    For smartforms debugging you can do this.
    1. Execute the smartform (execute button in SMARTFORMS transaction)
    2. Take the generated function module and display it in SE80.
    3.Find the smartforms Elements (text elements, windows, code lines, loops) in this and set Soft break points.
    Correct name is SMARTFORM_TRACE. You have lots of options for adequate analysis
    Tcode - SFTRACE
    Cheers,
    SImha.

  • How can i debug a Form in 6i environment

    I want to debug a form in 6i environment. WIth trace utility can i do it?if yes pls help me in this

    Why not just use the "Run Form Debug" toolbar button or Program => Run Form => Debug? Just simply type "break;" in the trigger or Program Unit you want the Debugger to break in and step through the code to see what is happening. Running the Form in Diagnostics Mode as Draji suggests is an excellent option as well, but reading the output file can be a bit daunting and doesn't let you "See" what your code is doing. The Forms debugger is an excellent tool. It is well worth learning how to use.
    You can also turn Debug Messages on - which basically just displays an alert with the name of each trigger that executes. You can turn on the Debug Messages from: Tools => Preferences => Runtime tab => Debug Messages checkbox.
    Hope this helps.
    Craig...

  • No PL/SQL windown in Forms-10g Debug

    Dear gurus...I used to use a PL/SQL window in 6i forms debug tool which displayed at the bottom of debugging module. It was very useful to look at the database values of current session but I'm unable to fine this PL/SQL interation tool in 10g Forms debug module. Is it away from my eyes only or really doesn't exist in 10g-Forms???

    Caz,
    Two things. First; it is considered poor Forums Etiquette to hijack someone else's posting. Always create your own post and include a link to a related posting if your issue is similar to someone else's.
    Second; now that you have the FORMS_TRACE_PATH defined, you create the trace file by adding the "RECORD=FORMS" parameter to the URL. Optionaly, you can add the "TRACEGROUP=DEBUG/CUSTOM1" parameter as well as long as you have specified the CUSTOM1 trace group in the ftrace.cfg file. Just adding the RECORD=FORMS should be enough, however.
    If that still doesn't produce the results you are looking for, check out the following references: Oracle9i Forms Diagnostic Techniques and Oracle9iAS Forms Services Tracing and Diagnostics. I know these are for Forms 9i, but the process did not change between Forms 9i and Forms 10g. If you are using Forms 11g, I'm not sure if these technigues will work the same as I am not using Forms 11g yet. ;-)
    Craig...

  • Debugging a pdf form

    hi to all experts,,\
    can we debug a pdf form

    HI Mozam,
    you are asking about adobe form debugging right.
    generally adobe  forms called as pdf forms.
    if that is the case, do as i said above it will do.

  • Can you "debug" a form when running on the App. Server?

    We recently got a project to do defect fixing of a Oracle Forms 10g application.
    They have given us each developer a VM with an app. server, source code etc.
    Problem is, we cannot run the form using the Form Builder.
    They want us to always make changes to the form, deploy in the app. server and run the form using the Application Menu.
    Problem is, how can we do line-by-line debugging in a situation like this?
    Normally, we would press the "Run form debug" button to run the form in Forms developer in debug mode.
    What is the solution?
    Should we ask the owners to give us permission to run the form from Developer?
    Or, is there way to do debugging a form when running from app. server?

    user12240205 wrote:
    So Craig, why is it prompting me with a File Open dialog box when it tries to run a DB procedure?
    What does the Forms debugger supposed to do? Run it and bring back result?
    Because Forms doesn't know how to load the object so it is prompting you to open it.  However, since the Forms debugger can't read the source of the database program unit (procedure, package, function) - you can't debug it from Forms.  At least, I've never been able to do it and I've tried making Forms open a source file for a database program unit.  It basically boils down to the fact that Oracle Forms can only debug objects that are within the scope of the Forms runtime/builder and database program units are not contained within the Forms objects (eg; Forms binary, PL/SQL Library or Menu Module binary).  I recommend you "Step-Over" any call to a database program unit when you encounter them in the Forms debugger.  The database program unit will take longer than normal to run, but it will eventually finish and take you to the next line of code to be executed.
    Craig...

  • Debugging Forms 6

    I have an Oracle Developer 6 form that cannot be debugged. This
    form has a 'WHEN-NEW-INSTANCE' trigger that performs a database-
    stored function which accesses a table on the database to get
    the value of the current environment in which it is executing
    (not a complex function). When stepping through the code with
    debug, the form will 'hang' when the code to perform the
    function is executed.
    The form is executed from within the Forms Builder by pressing
    the little 'bug' icon.
    Any clues as to what I am doing wrong?
    Thanks in anticipation.

    I just use the Message command and not the debugger. It is all I have ever needed.
    <p>Only I got pretty involved, and created a form to use. You can get the fmb here:
    <p>    Zdebug -- A Forms debugging message tool

Maybe you are looking for