Debug application form during FPCOPRA

[ricky_shaw]

Dear Experts,

When I execute the correspondence tcode FPCOPARA, an application form for letters (EFRM) is called & has the logic to update a Z* table to store some values.

In our QA system (non-editable), during mass exec of FPCOPARA for 100 contract accounts(CA), some wrong entries are updated in that Z* table for some CA's. I want to debug the appl form via external break points during FPCOPRA run & its not stopping in the form code.

How can I do this (enter debug)?

[RonnyF]

Hello Ricky,

transaction FPCOPARA is a FI-CA mass activity. You can debug a FI-CA mass activity by using transaction code DBUG before you schedule the run. In SAP KBA 2032637 'How to debug a FI-CA mass activity?' you can find more details about it.

Best regards,
Ronny

[ricky_shaw]

Hi Ronny, i don't see any DBUG tcode

[Sandra_Rossi]

DBUG is not a transaction code, it's a function code to be typed in the Command Field of FPCOPARA.

ricky.shaw

[ricky_shaw]

But where is this Command Field of FPCOPARA. ?

I got it..I need to type =dbug in the box..

Pls suggest.

[Sandra_Rossi]

ricky.shaw

Just DBUG, not =DBUG (although =DBUG should also work)

[PieterB · Accepted solution]

Hello Ricky,

you need to end the command DBUG in the command field after the creation of your mass activity run. See the by Ronny mentioned KBA for more info about the way to do it.

Regards,

Pieter

[ricky_shaw]

Hi Pieter, I need to enter DBUG in separate session after scheduling FPCOPARA?.

I don't have access to that KBA 2032637..Can you copy paste it here?

[PieterB]

Resolution

1. Call the transaction for the mass activity.
2. Create and save the parameters of the mass activity.
3. To debug the mass activity enter the command DBUG in the command field (before starting the mass activity).
4. The system responds with message >6 359 in a popup:"Activity run started in debugging mode".
5. Afterwards start the mass activity as usual via button "Schedule program run".
6. The program starts in debugging mode.

[ricky_shaw]

Hi Again, when i enter in command field on top left box, It says below

like this below when i saved the parameters

Am i missing something.

Can you help?

[Sandra_Rossi]

ricky.shaw

Pieter didn't say that DBUG is a tcode. It's not a tcode, it's a Function Code like you define in GUI Status of Dynpro screens. Read the SAP KBA, it explains.

Pieter just said to enter DBUG in the command field of FPCOPARA, not /NDBUG, not DBUG in the command field of SAP Easy Access.

[PieterB]

Hello Ricky,

1) Fill in your date ID and Identification

2) Type in 'dbug' in the command line and hit enter

3) confirm the pop-up

4) save your parameters (you can also do this before step 2)

5) click on 'Schedule Program Run' and FPCOPARA will be launched in debug mode.

Regards,

Pieter

[ricky_shaw]

Thank you all.

i had to use =dbug.