2011 Feb 02 3:50 PM
Hi all,
I must do changes in a node for a DMEE. I need check that it is populated right. My aim is to do an offset for document with 2 positions by year, becuase banks save a key the document, and how the number range in FI is renewed all years, the problem is trigered when the user send the file to bank. It's possible to mantain the range with this concatenation, but the person who mantain it, sometimes forget to do it.
I suspect that the debugger is called by the records in table DMEE_TREE_DEBUG, but I don't know how to populate it, and if it's the right solution, and if it's possible.
I'm searching with strings DMEE debug, DME engine debug in this site and notes, but I don't find the solution. I can debug the creation of file (PAYM) with report SAPFPAYM, because with F110 is so difficult (it works in background).
Can somebody give me any suggestion or idea how to solve it.
Thanks in advance.
Regards,
Eduardo
Hi all,
I must do changes in a node for a DMEE. I need check that it is populated right. My aim is to do an offset for document with 2 positions by year, becuase banks save a key the document, and how the number range in FI is renewed all years, the problem is trigered when the user send the file to bank. It's possible to mantain the range with this concatenation, but the person who mantain it, sometimes forget to do it.
I suspect that the debugger is called by the records in table DMEE_TREE_DEBUG, but I don't know how to populate it, and if it's the right solution, and if it's possible.
I'm searching with strings DMEE debug, DME engine debug in this site and notes, but I don't find the solution. I can debug the creation of file (PAYM) with report SAPFPAYM, because with F110 is so difficult (it works in background).
Can somebody give me any suggestion or idea how to solve it.
Thanks in advance.
Regards,
Eduardo
2011 Mar 30 9:13 AM
Hi,
1) Assign an exit module to your tree. Ideally just before the code you want to check
2) In TC SE37 set a session breakpoint in the function module you choose earlier
3) Execute the TC F110 with the print option
4) In TC SM37 find the F110 you just executed
5) Place the cursor on the job (be sure to select the right line)
6) In the command field u2013 type u201Cjdbgu201D and press Enter
And here you go, debugging of background programs!
Step 1 and 2 is not necessary but faster since you donu2019t have to do a lot of F5/F6
2016 Jun 06 12:41 PM
| User | Count |
|---|---|
| 3 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |