Skip to Content

Get Started
Solutions
sap spotlight
Support
Training
Community
Developer
Partner
About
sap spotlight
Community / Archives / Discussions Archive / ABAP Development / F110 debug - exi
t FEDI0003
Archived discussions are read-only. Learn more about SAP Q&A
F110 debug - exit FEDI0003
My apologies in advance, as this topic has been posted before. I do realize that
there are quite a few threads on this already on the forum, however most, if no
t all previous postings, don't list a definitive answer aside from 'Thanks, solv
ed problem'. That being said, here is my question:
I am looking to be able to change values in IDoc PEXR2002 prior to the document
being created.
I have done the following steps:
1. Create project in CMOD, and activated the following enhancements: FEDI0002 (E
XIT_SAPLIEDP_101), FEDI0003 (EXIT_SAPLIEDP_002), FEDI0004 (EXIT_SAPLIEDP_902). W
ithin the code of each exit, I have inserted 'BREAK-POINT' in each. I have even
tried being more specific in my code by specifying segment name. All are exits a
re active.
2. Create entries in table 'FEDICUS' for message type PAYEXT, basic type PEXR200
2, and listed all segments of that Idoc. It is my understanding that entries for
selected segments must exist in this table in order for the user-exit to get ca
lled.
In running multiple payment runs via F110 (interactively), none of my break-poin
ts will activate. I have tried running F110 in background, as well as F110S in b
oth foreground/background with the same results.
I have already checked notes 1248868 and 937966. Neither has helped resolve this
issue for me.
Anyone else have any ideas or hopefully an answer?
Thanks.
Fricis Zuments
December 01, 2011 at 18:52 PM
0 Likes
Not what you were looking for? View more on this topic or
6 replies
SK J replied
November 21, 2011 at 20:52 PM
I can suggest something to analyse..
These user exits are being called from include LIEDPF15 based on some conditions
. Put a break point on these IF conditions and see when and how it triggers.
Thanks,
SKJ
0 likes
Vishnu Tallapragada replied
November 21, 2011 at 22:11 PM
EXIT_SAPLIEDP_902 is the correct exit to use. We use it in our company for manip
ulating the PAYEXT IDoc before it is sent to the banks for clearing the payment
to our vendors.
You need to set and save the parameters and/or proposal in F110 but should not a
ctually run it, if you want your breakpoints to be hit.
F110 only schedules the payment run in background and is designed for business u
sers, who don't want to wait on the run to complete.
Put your breakpoint and run the program RFFOEDI1 through SE38 / SA38, with the p
ayment run date and identification saved in F110. This works perfectly for me.
Revert back if you have any issues.
0 likes
Fricis Zuments replied
November 21, 2011 at 23:18 PM
Thanks for the feedback so far.
Vishnu- I followed what you said and the breakpoint is indeed being called now.
Strange in that since part of the F110 process also includes running RFFOEDI. I
would have thought that my breakpoints would have been called as part of F110. I
s there something else I am missing here?
Do your Accounting users break up the payment process and use F110 to create pro
posals only, and run RFFOEDI seperately?
0 likes
Venkat CH replied
November 22, 2011 at 05:19 AM
Hi Fricis Zuments,
I want to add a point on to your discussion, In order to debugg the F110 process
first thing you need to understand is programs "RFFOAVIS" 'RFFOEDI1' are used t
o post the documents.
When user runs F110 in Printout/data medium tab based on the clearing we will be
giving the variant name choosing the program
"RFFOAVIS" or 'RFFOEDI1' accordingly. And now put your breakpoint in the program
 "RFFOAVIS" or 'RFFOEDI1' as per your run.
And from process level of F110 after creating SCHEDULE PROPOSAL, don't run the p
aymentt run from F110, rather go to SE38 and execute the program "RFFOEDI1" and
select the variant which you gave in F110 and also give the "Program run date" a
nd "Identification feature" same as F110's "Run date" and "Identification" by wh
ich you can debugg the whole flow of F110.
I hope i might have confused you, if u confused lemme know i will clear tht conf
usion
Regards
Venkat
0 likes
Vishnu Tallapragada replied
November 22, 2011 at 05:51 AM
Dear Fricis,
I am glad that I could be of some help to you.
The business users in our company use F110 to do the full payment run as it is m
ore convenient that way.
The reason why F110 did not hit your break points is because it runs RFFOEDI1 as
a background job (background jobs are run by the system and are detached from y
our user session running in foreground that actually has your breakpoints) by us
ing SUBMIT ... VIA JOB construct
I use RFFOEDI1 to debug payment run user exits myself and I don't know anyone wh
o uses it other than for testing purposes. I also don't think anyone would use i
t to automatically run as a scheduled job even, as payment runs are taking money
out of the company bank accounts and business would want to run them through F1
10 only when they really need to pay.. hahaha )
If your problem is resolved you can set your question to resolved, so that it wi
ll help others searching for similar issues in locating this thread more easliy.
Best regards,
Vishnu T
0 likes
Fricis Zuments replied
December 01, 2011 at 18:52 PM
Thanks again for your input Vishnu and everyone.
From what I have read in some SAP notes (note 1248868 to be exact) as well as ot
her postings, it seems like some are saying EXIT_SAPLIEDP_002 is the correct exi
t to use, however you are saying EXIT_SAPLIEDP_902 is the correct one. To be tho
rough in my tests, I decided to place the same code in both of them and try it o
ut. Here is what I put in:
IF segment_name = 'E1EDKU3'.
DATA ls_e1idku3 LIKE e1idku3.
DATA: i TYPE i.
DESCRIBE TABLE edidd_table LINES i.
IF edidd_table-segnam = 'E1EDKU3'.
ls_e1idku3 = edidd_table-sdata.
IF ls_e1idku3-pairzawe = 'A'.
ls_e1idku3-pairzawe = 'D'.
edidd_table-sdata = ls_e1idku3.
MODIFY edidd_table INDEX i.
ENDIF.
ENDIF.
ENDIF.
Essentially, I am trying to change the value for payment method from one value t
o another. I see the exit getting called when I set an external breakpoint at my
top IF statement, however the underlying code gets skipped over, even though th
e condition has been met.
Do you or anyone see any issues with my logic here?
Thanks!
0 likes
Share & Follow
Facebook twitter YouTube LinkedIn Google+ Instagram Slideshare
Privacy
Terms of Use
Legal Disclosure
Copyright
Trademark
Sitemap
Newsletter