Skip to Content
P D

Production Debugging Issue

Hi Experts,

     I am facing one error situation in production system for an adobe form. This issue we are not able to replicate in development or quality system. Wrong information is displayed for a particular data in adobe forms. The program codes written in this adobe forms runs as a background task. So how can I debug this particular piece of code in production system. In development system I gave an infinite loop in the code and through SM50 i debugged the program. But how to debug in production system ?

BR.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Dec 24, 2014 at 12:13 PM

    Hi,

    1. Do you have Debug Authorization in PRD Client.

    2. if yes, try to fetch the Dynamic Function Module name, with respect to Adobe Forms

         or execute the Adobe Forms manually, you will get the trigger function module name.

    3. Goto SE37, and search the code, which has been written in Adobe. (Search with [in main program])

    4. Put the Break-point and execute the Program. While executing system will stop the process on break-point.

    Regards

    Praveer.

    Add comment
    10|10000 characters needed characters exceeded

    • Hi,

      Through JDBG T-Code you can debug a back-ground job.

      You can start a selected Job Debugging, once you have started the Debugging, you can search your respective bunch of code and you can analysis the same.

      Regards.

      Praveer.

  • Dec 24, 2014 at 01:30 PM

    Hi,

    try to use a temporary statement like this instead of an endless loop:

    WAIT UP TO 10 SECONDS.

    So, you will have 10 (or more) seconds to debug your code through SM50. And business process will not suffer.

    Best regards,

    George Shlyahov

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Sam,

      Basically, this the way we use to debug the Smartforms and Adobe Forms.

      and if we are trying to debug the Web Dynrpo related object, then we use EXTERNAL BREAKPOINT.

      You can go for one more way.

      Go to ST05 T-code. and trace the Function Module information, which are triggering while executing the respective web dynpro application.

      and try to debug the any one of the function module.

      If you are able to debug, then you have to search the respect function module or class, which contains the Adobe Forms Information.

      or If you are not able to debug any of the code through the EXTERNAL BREAKPOINT.

      then check the SU53 (Authorization) T-code, whether you have sufficient authorization to debug the objects or not.

      Regards.

      Praveer.


  • Dec 24, 2014 at 03:04 PM

    Hi,

    First you should have FF(Fire Fighter) ID in order to debug some thing in Production environment.

    For background debug, while you are saving the job start debugging and start update debugging ON from debugging option.

    Once job is saved, automatically update debugging will start and then now you can keep your break points(using debug break point option(Breakpoints --> Break point at--> XXX)) and execution will stop at the desired(interface) point. 

    Hope this helps.

    Add comment
    10|10000 characters needed characters exceeded