Extraction in debug mode without RSA3

Hi,
does anyone know, if there is a way to run an extraction in debug mode on the R/3 side without using RSA3 or RSA7? It has to be a real delta extraction triggered by an InfoPackage in BW.
I've also tried the "simulate update" function in the monitor (right-click on Data Package), but that only simulates/ debugs the BW-BW transfer.
Thanks in advance!
Gerrit

Hi Gerrit,
Your requirement is only feasible if your extarctor is based on a function module. In such a case you can set a breakpoint in the function module and when you execute the infopackage the debugger will halt at the breakpoint.
I dont think it is possible for datasource based on table/view.
Bye
Dinesh

Similar Messages

Call function in debug mode

Hi,
when I´m on the test function screen of se37, I can run the function in debugging mode and it´s starting with the debugger on the first code line.
Is it also call a function from a report in this debugging mode?
thank you!
reward points guaranteed

Thank you for your answers...
Let me explain a little bit more in detail, what I want to do.
I have an XML interface function which is going to be called by an
external application about RFC, reading binary data,
interpreting that as XML and doing something in the SAP system afterwards.
As the system is a 4.6C I can´t debug externally, I want to provide
a debugging function in a monitoring application for that.
As people are using the monitoring, which are not familiar with all
the code behind that, I want to start the debugging mode by myself,
without setting a breakpoint.
Let me describe it like this:
When you type in /H in the transaction field in the SAP menu bar, the
debugging mode is going to be started for further actions.
All I want to do is starting that /h debug mode without typing anything
in the transaction field, just inside of the report.
How can I do that?
Michael

My program works only in debugging mode

Dear All,
I am just starting to use LabVIEW and developing a instumental driver.
The program is rather sequentially designed because I am only used to work with text-based program.
The current program is working in debugging mode without any error message.
To give an idea of how it is composed:
1. Set up the serial port setting (machine address, baud rate, parity, etc)
2. Send to the instument the name of a short program to be run.
3. Send mutiple string commands to the instruments. Those string commands construct a short program to control the instrument.
4. Send another string command to run the short program
The issue is that it does not work in excution mode. It looks to me that the communication between the instrument and computer seems to be too fast.
Since the program is designed in a sequential manner, it does not have any while-loop or for-loop so I cannot add any timing function.
Could anyone give me a hint or a right direction to fix this issue? It would be really appreciated. Thank you.
Solved!
Go to Solution.

You could do something like the attached modification.Note how I modified the connector pane for the subVI to use the conventional 4-2-2-4 pattern and notice where I connected the terminals.
NOTE: I am assuming the VI is supposed to run just once, and that you're not using the Run Continuously button in the toolbar. You're not, right?
Attachments:
NE-100_StairFlow_w_RUN00 MOD.vi ‏27 KB
NE-100_RAT_00_XX MOD.vi ‏18 KB

Recompile before existing Debug mode causes Raptor to hang

I have been able to do this a few times on 10R2, with Raptor, on Windows 2000 & XP
1) I write a small procedure or package in Raptor.
2) Compile it for debugging.
3) Set a few breakpoints.
4) Run it in debug mode within Raptor.
5) Step through to one of my breakpoints.
6) Go back and press the recompile for either normal or debug mode, without terminating/stopping the debug session.
7) Raptor hangs.
On a hunch, I opened up a SQLPlus window and tried to recompile the package with an alter ... compile while Raptor was still hung. The SQLPlus session was blocked from recompiling, and eventually it gave up.
I have found just killing Raptor can leave the a minor mess in the database, and Raptor will still have problems with that procedure/package when Raptor is restarted.
It appears that given time (more then a few minutes), the database cleans up things get back to normal.
Thanks,
Scott

This is a known bug. The session has a lock on the DB which makes the compile lock/hang.
-kris

Is it possible to extract a VI from an executable which has debug mode enabled?

It is a curiosity question from a client.
Is it possible to extract a VI from an executable which has debug mode enabled?
Since the block diagram would not be in edit mode.... Is it possible to "peer" into the executable, look at a VI and recover the block diagram? This owuld be for a deleted VI that is part of an executable which had debug mode enabled..
Did anyone try this?
Curious..

Extract VIs from an EXE? No problem. Even if debugging isn't enabled you can extract VIs, they just won't have block diagrams, and may not have front panels depending on if they were removed in the EXE making process.
Attached is an example project for making an EXE, the EXE itself, and a VI for extracting VIs from the EXE. The code is quite primative and it was just meant to demonstrate how this can be done.
To extract the Main.vi from the Application.exe, run Extract Main.vi from EXE.vi, provide the path to the EXE and the path to where the VI should be saved and then run the VI. This VI will set keys in the INI file for the application, then run th EXE. Then it opens an application reference to the EXE, then opens a VI reference to Main.vi. Then it aborts Main.vi, and extracts it.
Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.
Attachments:
Test EXE Extract.zip ‏763 KB

Procedure works in debug mode but not normally

I'm scratching my head on this and would appreciate any help as to what is happening.
We have client code that calls stored procedures on an Oracle 10g database. When I run it normally the procedure does not behave as expected. If I try to debug the code it works fine on client until I recompile the procedure again. I don't have the faintest idea why this happens but I'm not sure how to make it work correctly without putting it in debug mode.
If anybody has any idea what may be occurring I would appreciate the help.

hmmm, I'm not sure how to do that.
I do a select against a table into collection then loop the collection as follows:
          FOR Indx IN 1 .. v_Probs_Desc.COUNT
          LOOP
               v_MyClob := v_MyClob || v_Probs_Desc(Indx);
          END LOOP;
do some formatting by removing some tags embedded in the text
          v_MyClob := REGEXP_REPLACE(v_MyClob,'<GMT[[:print:]]*:','');
          v_MyClob := REGEXP_REPLACE(v_MyClob,'<GMT[[:print:]]*GMT>','');
          v_MyClob := REGEXP_REPLACE(v_MyClob,'<MAILTO[[:print:]]*MAILTO>','');
          v_MyClob := REPLACE(v_MyClob, '<PERSON', '');
          v_MyClob := REPLACE(v_MyClob, 'PERSON>', '');
          v_MyClob := REPLACE(v_MyClob, chr(13), chr(10));
Find position of the heading if found (case-insensitive).
          v_End := REGEXP_INSTR(v_MyClob, 'Steps to Reproduce([:punct:])?'||chr(10)||'|Steps([:punct:])?'||chr(10),1,1,0,'i');
          IF ( v_End = 0 ) THEN
               v_End := LENGTH(v_MyClob);
               v_Flag := 1;
          END IF;
          IF ( LENGTH(SUBSTR(v_MyClob, 1, v_End)) > 4000 ) THEN
               v_Text := SUBSTR(v_MyClob, 1, 4000);
          ELSE
               v_Text := SUBSTR(v_MyClob, 1, v_End);
          END IF;
--Remove any spaces or newlines from the beginning
          v_Wspace := ASCII(SUBSTR(v_Text, 1, 1));
          WHILE ((( v_Wspace = 10 ) OR ( v_Wspace = 32 )) AND ( LENGTH(v_Text) > 0 ))
          LOOP
               v_Text := SUBSTR(v_Text, 2, LENGTH(v_Text));
               v_Wspace := ASCII(SUBSTR(v_Text, 1, 1));
          END LOOP;
Make sure that the text is less than 4000 bytes so it can be inserted into another table.
          SELECT VSIZE(v_Text)
          INTO v_Size
          FROM DUAL;
          IF ( v_Size > 3950 ) THEN
               v_Text := 'Created from ' || v_p2t(indx).PROBLEM_ID || '>' || chr(10) || chr(10) || SUBSTRB(v_Text, 1, 3950) || ' ... ';
          ELSE
               v_Text := 'Created from ' || v_p2t(indx).PROBLEM_ID || '>' || chr(10) || chr(10) || v_Text;
          END IF;
there's other code but the above code snippet doesn't work outside of debug mode.
Edited by: dtjasonb on Oct 13, 2009 10:27 AM

Devloper system configuration (weblogic in debug mode on Eclipse/windows)

Hi,
I work on a project, which we may consider as big. Couple of thousads of java files, muilti-tired. We use, weblogic in eclipse on widows for development. Curreltly we have 1G ram on each of developer mechines. But most of us are complaining that, system is running slow in debug mode. Sometimes, we can't even work.
I greatly appreciate if somebody can point me to the URL or suggestion for good system configuration, so that we can work comfortably.
Just asking to increase the RAM may not help me in convencing the business/management. If there any specific recommandations by either by BEA or IBM (eclipse), that helps me a lot in raising the same to our buisness.
Greatly appricate your suggestions
Reg,
Mahi

Hi Bigmachini,
According to my solution, what about your issue now?
If you have been solved the issue, would you mind sharing us the solution here? So it would be helpful for other members who get the same issue.
If not, please let us know the latest information about it.
@Malik, could you please tell me if you try to check your issue by the above suggestion as I said?
If no, please try the above suggestions to check this issue and then tell me the latest message about this issue.
>>The error mostly occurs when debugging ADO.NET or database function calls. If code is run without debugging then there is no issue at all.
You could also try to copy your project and then debug your project in debug mode on a another machine you install same Windows 10 OS check this issue again.
Best 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.

Restart the server in debug mode: How to drop saved passwords?

In NWDS server pane, I entered a wrong password when trying to restart my SAP AS Java in debug mode. Now I only get exceptions "com.sap.enginemanagement.UnauthorizedException: Incorrect login information provided" without a chance of changing the entered credentials. Restarting NWDS didn't work.
Any ideas?
Thx,
Christoph

Hi Christoph,
are you talking about the "Java EE" perspective and the "Servers" view within it? I tried it out and it does not behave properly.
Try the "SAP Management" perspective. Within the left hand tree open your system, expand the instance starting with "J..", expand the "AS Java" node and select the "Process Table" node. In the right hand table select the server0 process and chose from the context menu "Start Debug Session".
The SAP JVM offers some extra debug options. Expand the "Expert Mode" in the modal dialog. If you want to debug web applications select "code isolation" and unselect all other options. A password dialog will appear and you must enter the credentials for the operating system user, not for the AS Java administrator.
One table column is labeled "Debug", there you can see the currrent debug port.
Either you start now a "Remote Java Application Debug" debug session or you have a Java EE project and can create a "SAP Application" debug session.
Anyway to see your application threads in the debugger you have to access your web application with a special debug URL.
If your URL looks like this: "http://localhost:50000/myapp" you have to insert a debug token beween host part and the path and the URL becomes "http://localhost:50000/@@@DEBUG@@@/myapp". If you miss to modify the URL you will not see any thread.
If you want to get a "normal" debug behaviour just deselect all options in the debug dialog. You will see all threads, you do not have to modify your URL, but the server will restart after you detached the debugger.
Hope this helps.
Best Regards, Stefan
Edited by: Stefan Bodenstein on Oct 1, 2008 12:00 PM

Processing happens only in debug mode.

Hi,
I am calling an RFC enabled FM BAPI_ALM_NOTIF_DATA_MODIFY and BAPI_ALM_NOTIF_SAVE to modify the data of a notification. These function modules are called within another FM which is also a RFC called in background as a separate task. The problem here is that, the data gets modified fine only when I am in the debugging mode and execute it. But if I execute without going to the debug mode, I cannot modify the notification data. Kindly suggest why this is happening and what the solution is. Thanks

I am not using any destination. The code is as shown:
WAIT UP TO 5 SECONDS.
CALL FUNCTION 'BAPI_ALM_ORDER_GET_DETAIL'
    EXPORTING
      number                 = aufnr
   IMPORTING
     es_header              = gf_header
    TABLES
     et_olist               = it_ord_notif
      return                 = it_ret
CALL FUNCTION 'BAPI_ALM_NOTIF_GET_DETAIL'
EXPORTING
    number                   = gf_header-notif_no
IMPORTING
   NOTIFHEADER_EXPORT       = gf_notif_exp
        CLEAR: gf_notif_no.
        DESCRIBE TABLE it_notif_no LINES g_line.
        READ TABLE it_notif_no into gf_notif_no INDEX g_line.
        IF gf_notif_no-short_text+0(3) = 'PRB'.
         clear: gf_notif_imp, gf_notif_imp_x.
            gf_notif_imp-desstdate = gf_notif_exp-desstdate.
            gf_notif_imp-desenddate = gf_notif_exp-desenddate.
            gf_notif_imp_x-desstdate = 'X'.
            gf_notif_imp_x-desenddate = 'X'.
            CALL FUNCTION 'BAPI_ALM_NOTIF_DATA_MODIFY'
                  EXPORTING
                    number                   = gf_notif_no-notif_no
                   NOTIFHEADER              = gf_notif_imp
                   NOTIFHEADER_X            = gf_notif_imp_x
                 IMPORTING
                   NOTIFHEADER_EXPORT       = gf_notif_result
                 TABLES
           CALL FUNCTION 'BAPI_ALM_NOTIF_SAVE'
EXPORTING
    number            = gf_notif_no-notif_no
IMPORTING
NOTIFHEADER       = gf_qmnum_save
TABLES
   RETURN            = it_ret2.
          endif.
            clear: gf_notif_no.
        LOOP AT it_notif_no INTO gf_notif_no.
          IF gf_notif_no-short_text+0(3) = 'PRB'.
            SELECT SINGLE objnr FROM viqmel
                                                  INTO g_objnr
                                                 WHERE qmnum = gf_notif_no-notif_no.
            SELECT SINGLE stsma INTO g_stsma FROM jsto WHERE objnr = g_objnr.
            SELECT SINGLE estat INTO g_stat FROM tj30t WHERE stsma = g_stsma AND
              spras = 'EN'
              AND txt04 = 'SFMR'.
            CALL FUNCTION 'STATUS_CHANGE_EXTERN'
              EXPORTING
                check_only          = ' '
                client              = sy-mandt
                objnr               = g_objnr
                user_status         = g_stat
                set_inact           = ' '
                set_chgkz           = 'X'
                no_check            = ' '
              EXCEPTIONS
                object_not_found    = 1
                status_inconsistent = 2
                status_not_allowed = 3
                OTHERS              = 4.
            IF sy-subrc = 0.
            ENDIF.
          ENDIF.
        ENDLOOP.
      ENDIF.
    ENDIF.
ENDIF.

Function Module working only in debug mode

Hi all,
The following Function Module works only in debug mode. The purpose of this FM is to create a notification and to put it in progress status. If I put a breakpoint before "CALL FUNCTION 'BAPI_ALM_NOTIF_PUTINPROGRESS'" it works. If I execute this FM without putting a breakpoint at that place it creates the notification but doesnt put it in progress status.
In other words, the last BAPI call doesnot work if I dont put a breakpoint before.
Can somebody help me to find out where is the problem?
Thanks,
Younes
FUNCTION ZFM_CREATE_NOTIF_IN_PROCESS.
""Local interface:
*" IMPORTING
*"     VALUE(NOTIFTYP) TYPE CHAR2
*"     VALUE(NOTIFHEADER) TYPE BAPI2080_NOTHDRI
*" EXPORTING
*"     VALUE(NOTIFNUMBER) TYPE CHAR12
*"     VALUE(NOTIFCURSTATUS) TYPE CHAR40
DATA: gs_bapi2080_nothdre TYPE bapi2080_nothdre,
      gt_return TYPE TABLE OF bapiret2.
The notification is created with a temporary number
CALL FUNCTION 'BAPI_ALM_NOTIF_CREATE'
EXPORTING
    notif_type         = NOTIFTYP
    notifheader        = NOTIFHEADER
IMPORTING
    notifheader_export = gs_bapi2080_nothdre
TABLES
    return             = gt_return.
READ TABLE gt_return TRANSPORTING NO FIELDS WITH KEY type = 'E'.
CHECK sy-subrc IS NOT INITIAL.
*The notication will be saved with a number which isnt temporary
CALL FUNCTION 'BAPI_ALM_NOTIF_SAVE'
EXPORTING
    number      = gs_bapi2080_nothdre-notif_no
IMPORTING
    notifheader = gs_bapi2080_nothdre
TABLES
    return      = gt_return.
READ TABLE gt_return TRANSPORTING NO FIELDS WITH KEY type = 'E'.
CHECK sy-subrc IS NOT INITIAL.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
The Notif is already created, it will be put in progress status
NOTIFNUMBER = gs_bapi2080_nothdre-notif_no.
   CALL FUNCTION 'BAPI_ALM_NOTIF_PUTINPROGRESS'
        EXPORTING
          NUMBER             = NOTIFNUMBER
          LANGU              = SY-LANGU
       IMPORTING
         SYSTEMSTATUS       = NOTIFCURSTATUS
       TABLES
         RETURN             = gt_return.

Hi Emmanuel,
Now I get your problem: you want to wait to have the commit finished! The call to BAPI_TRANSACTION_COMMIT has an optional parameter 'WAIT' which is space by default which causes only a commit. When you set this parameter to 'X' it will do a commit work and wait.
This should solve your problem!
Regards,
John.

Debug mode (EP6 SP 2) crashs from time to time

hi folks,
we got a very well running portal ep6 sp2 which
we use for iview development. the developers use
pdk and eclipse and we start the portal in debug
mode.
what happens is that from time to time it gets
unpossible to connect to the debug port. it is not
possbible to debug an iview from eclipse. the
connection to the debug port is not possible anymore.
the only solutions i got is a portal restart to ensure
that our developer can use the debug port. but that
takes too much time. does anybody know what leads to that
phenomenon? and how can we reanimate the portal to be
debugged without a complete restart?
i really appreciate any help,
maik

Hi Tracy,
Has it ever been shut off from AC power for any length of time?
I'm thinking a dead or weak PRAM Battery may cause the boot mode to change.
Unless of course it might be a sticky Shift key.
   1. Access the command line by either opening Terminal remotely, or by logging into the computer from another via SSH.
   2. Execute the following command in Terminal or on the command line:
      sudo nvram boot-args="-x"
      (If you want to start in Verbose mode as well, use sudo nvram boot-args="-x -v" instead )
   3. After using Safe Boot, to return to a normal startup, execute this command in Terminal or the command line:
      sudo nvram boot-args=""

Debugging mode in server - How does it work?

Hi
How does debugging mode in a server work ?
Is the code compiled line by line as we proceed or how ?
When we make a code change how is the hot code replaced when in debug mode and why not in normal run mode?
Why is it not necessary to restart a server when we make changes to jsp when in normal mode?
Thanks in Advance

How does debugging mode in a server work ?Just like in any othe rprogram.
Then how is it possible to change the values when
the program is running . i.e. we have a option that
we can change the values right !!
Because the debug api allows you to do that.
>
s the code compiled line by line as we proceedor
how ?
No. Line number information is stored in the.class
file, and the editor simply displays the line the
bytecode mentions. Whether bytecode and sourcecode
match is a different thing.
I had previously read that the compiler compiles
the code with break points at the beginning of every
class (for step by step method)
I agree with Rene. It happensthat you debug with the wrong source code and you will in that case notice that the debugger is saying that you are executing a line between methods.
>
>
When we make a code change how is the hot code
replaced when in debug mode and why not innormal
run
mode?I guess the executed bytecode for a method issimply
replaced in memory... the entry point was probably
stored and will be used to re-set to method entry
before running the new bytecode.
Then why is it not done when we are running the
server in the normal mode.
Why would it? What code should it replace it with?
>
>
Why is it not necessary to restart a server when
we
make changes to jsp when in normal mode?
Because the server can notice the change andunload
and reload the class.
I meant that when the jsp is compiled the servlet
is created when i run the server right.(i'm not
sure).
So when I change the code and without restarting the
server I run a jsp file it reflects the changes...
HOW??
Because some servlet runners can be configured to check changes on disk, and recompile if needed.
Kaj

Code runs fine in debug mode but hangs when compiled in release mode

I am struggling with the following problem. I have code which runs fine when it is executed in debug mode. However, when I compile it in release mode and run the executable, the code freezes and does not work. The code acquires images from a Hamamatsu camera. In the debug mode I am able to continuously acquire images. However, in the release version, the code hangs after acquiring the first image.
I am using LabWindows/CVI version 7.
I would greatly appreciate if I can get any help/suggestions in resolving this problem?
Thanks!
Regards,
Sripad
Solved!
Go to Solution.

Sripad:
If you search this forum for "debug release crash" or "release version crash" or similar phrases, you'll find that this is a pretty common question. Look through the other posts you find here to see if anything is applicable to you.
The debug version does some things like padding variables so you can sometimes overrun your declared variable space without overwriting the next variable. In the release, the variables are packed, so if you overrun one, you are overwriting another. Just one possible difference.
You can do some things in your release code to see where things get lost, like (temporarily using printf statements after multiple statements at the start and end of your loop to try to identify that failing line of code.
Look through other threads to find other ideas.

App working fine in debug mode but not otherwise on iPad

Hi everyone,
Sorry if I am putting this question in wrong section, this seems to be the most relative location to ask question.
My Problem:
I have developed an app using Adobe Air and starling. App is working perfectly when I run on Flash Builder (debug and run both). When deploying on iPad at one particular location, it is either not getting TouchPhase.ENDED or some code is crashing.
I tried to debug while running app on iPad and its working absolutely fine. But when I create the ipa file normally i.e. without debug mode, at a particular location code is not working.
Please help me out in this regard, asap. I need to deliver it.
Please!!!!
Thanks
Waqar Iqbal

Hi,
I know one case, but don't know if have a solution.
See Registering Add-on in 2004
Best Regards.

How to turn on debug mode for NW 7.3 trial version?

Hello SDN!
I've got a trial version of NW 73 from here: http://scn.sap.com/community/netweaver/blog/2012/07/12/netweaver-compositon-environment-73-trial-version-available-on-scn and installed it from instruction. Installation was OK and Java instance is up and running now. System asked me to change administrator password after I logon to the NWA for the first time. I've changed password and now I'm able to login to the NWA but system doesn't accept neither new administrator password nor OS users (root and cesadm users) passwords when I try to turn on debug mode for Java instance.
What I did wrong?
Regards, Lev

Hi Benny!
Thanks for answer.
The installation finished without any errors. Java instance run successfully. After install I opened browser right in VM window with url http://sapnwce73:50000/nwa to switch on debug mode. Since it was my first logon to the system as "Administrator" user the system asked me to change password. I've changed password and logon to NWA successfully as user with login "Administrator" and his new password. After I switched on debug mode the system asked me to login and password as shown on the follow screenshot:
This screen didn't accept neither Administrator user credentials, nor cesadm user credentials, nor root user credentials.
Also I've found that I'm not able to restart/stop Java instance because of the same issue - system doesn't accept user credentials.

Extraction in debug mode without RSA3

Similar Messages

Maybe you are looking for