topic Re: Production Debugging Issue in Application Development and Automation Discussions

Production Debugging Issue

former_member207873 — Wed, 24 Dec 2014 12:05:23 GMT

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.

Re: Production Debugging Issue

ipravir — Wed, 24 Dec 2014 12:13:12 GMT

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.

Re: Production Debugging Issue

former_member207873 — Wed, 24 Dec 2014 12:38:09 GMT

But the code in the interface code is run background. So i assume it would never go into the debugging mode.

BR.

Re: Production Debugging Issue

GeorgeShlyakhov — Wed, 24 Dec 2014 13:30:53 GMT

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

Re: Production Debugging Issue

ipravir — Wed, 24 Dec 2014 13:40:34 GMT

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.

Re: Production Debugging Issue

former_member207873 — Wed, 24 Dec 2014 13:46:14 GMT

So you mean i have to write this code and send it to production ? Any other ways to debug this in production ?

BR.

Re: Production Debugging Issue

ipravir — Wed, 24 Dec 2014 14:07:59 GMT

Hi,

Which code? Is you Program and Adobe Form is already in PRD Client or not?

If is it in PRD then below Steps to Follow to debug in Background Process.

1. Execute your program in PRD Client,

2. Go to SM37 T-Code and through the JDBG you can debug the same.

3. Based on that you can analysis the current program and Adobe Form logic and code,

4. Then your can change the same in your DEV Client and make your logic as per your requirement.

And then send your changes to PRD.

Regards.

Praveer.

Re: Production Debugging Issue

sagar_pawar14 — Wed, 24 Dec 2014 15:04:30 GMT

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.

Re: Production Debugging Issue

former_member207873 — Fri, 26 Dec 2014 11:18:17 GMT

Hi Praveen,

I tried your solution. But nothing is getting showed in SM37. This adobe form is actually called from a webdynpro based application. (SAP PLM) Not getting any idea on how to debug. I tried putting external debugger point also. But no luck.

BR.

Re: Production Debugging Issue

ipravir — Fri, 26 Dec 2014 11:22:10 GMT

Hi Sam,

Is the WebDynpro Program is Standard Program?

Regards.

Praveer.

Re: Production Debugging Issue

former_member207873 — Fri, 26 Dec 2014 11:35:46 GMT

Hi Praveen,

This is regarding PLM labels. The program which runs the adobe forms is a custom program.

BR.

Re: Production Debugging Issue

ipravir — Fri, 26 Dec 2014 11:45:30 GMT

Hi Sam,

Ok, If you know the Adobe Forms Name, go to the SFP T-Code and give the same.

And then Execute through execute button, you will get the Respective Function Module Name.

Copy the Function Module and go to SE37.

Open the Function Module and Search your Code space through SEARCH IN ALL.

after that put a breakpoint in particular line of code, break point should be

"SET/DELETE EXTERNAL BREAKPOINT "

After that execute your web dynpro application and check.

Regards.

Praveer.

Re: Production Debugging Issue

former_member207873 — Fri, 26 Dec 2014 12:08:07 GMT

Hi,

I tried that also..by giving program name in se38 by adding F01 & L in the program name. Still no luck.

BR.

Re: Production Debugging Issue

ipravir — Fri, 26 Dec 2014 12:24:12 GMT

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.