‎2009 Feb 13 6:31 AM
Hi guys,
I have a problem in FB01.
The user posts a concur(VE) document to FB01.
On 1st item, no business area is entered.
On the 2nd, BA 0005 is entered.
Due to OSS note 566083.
The 1st item was also populated with BA 0005.
Now, the user didn't what that to happen coz it will cause them problems in failed payments doc.
My question is, knowing the location of the code that was applied with OSS notes that had caused the problem, how will i know the nearest user-exit that comes before and after that code?
Thanks,
Navi
‎2009 Feb 13 6:33 AM
Hello
refer the given below link
https://wiki.sdn.sap.com/wiki/display/ERPFI/ShortTutorialonUserExits
Thanks
Arun
Edited by: Arun Kayal on Feb 13, 2009 7:40 AM
‎2009 Feb 13 6:36 AM
Hi Navi,
To find the user exits being used in your transaction you can use the following method :
1) Go to SE93 - Give ur Tcode - Copy the package name from there.
2) Go to Tcode SMOD - In enhancement put * - Press F4 help.
3) In Repository Info System dialog put the package name.
In this way you will get a list of all the user exits being used for your transaction.
Then keep a breakpoint in each of them to find out which one is getting called during your execution.
‎2009 Feb 13 6:40 AM
HI,
This is the clear Tutorial To find the User Exits:
[https://wiki.sdn.sap.com/wiki/display/ABAP/User+Exits]
Regards,
Gurpreet
‎2009 Feb 13 6:41 AM
You goto OBBH Transaction and select the Company Code & Substitution rule.( after double click) you will find some steps for Header and line Items. Here sometimes they default certain values like business area etc .
Expand the Substitution>Expand the Step 001 etc> you will find the Prerequisite and substitutions there.You check in Substitutions.
You can also Check program ZGGBS000 or rggbs000 ."substiution Routines.
‎2009 Feb 13 9:11 AM
‎2009 Feb 13 9:36 AM
Hi!
Sorry to update just now.
I check first the exits (for FB01) advised by other posters.
But the program did not pass through in any one of them.
I debug the standard program and it indeed passes through this transaction.
I will ask the functional the necessary filters and then advise them to address the error using OBBH.
Thanks a lot.
I'll get back to you once I settle my proposal to the functional and to the user.
Navi
Edited by: navi on Feb 14, 2009 1:06 AM
‎2009 Feb 13 8:26 PM
Careful Navi. According to note 42615,:
"In addition to accounts and amounts, the following fields, for example, are critical and must not be substituted:
GSBER: this could lead to inconsistencies with modules AM, CO and MM, since the business area is also used in these modules. "
Rob
‎2009 Feb 13 6:47 AM
Hi Navi,
The Transaction FB01 contains 14 user exits.
Exit Name Description
F050S001 FIDCMT, FIDCC1, FIDCC2: Edit user-defined IDoc segment
F050S002 FIDCC1: Change IDoc/do not send
F050S003 FIDCC2: Change IDoc/do not send
F050S004 FIDCMT, FIDCC1, FIDCC2: Change outbound IDoc/do not send
F050S005 FIDCMT, FIDCC1, FIDCC2 Inbound IDoc: Change FI document
F050S006 FI Outgoing IDoc: Reset Clearing in FI Document
F050S007 FIDCCH Outbound: Influence on IDoc for Document Change
F180A001 Balance Sheet Adjustment
FARC0002 Additional Checks for Archiving MM Vendor Master Data
FEDI0001 Function Exits for EDI in FI
RFAVIS01 Customer Exit for Changing Payment Advice Segment Text
RFEPOS00 Line item display: Checking of selection conditions
RFKORIEX Automatic correspondence
SAPLF051 Workflow for FI (pre-capture, release for payment)
Find ur user exit and go head....
Hopes it helps u....
Cheers,
Rajesh.
‎2009 Feb 13 9:29 AM
Hi,
I put breakpoints on the exits that you've mentioned, but the transaction does not pass in any one of them.
Thanks for helping.
Navi
‎2009 Feb 13 9:35 AM
Just putting breakpoints inside the exits wont make it work u need to create and include the exits in an active project through CMOD. then ur breakpoint will get triggered.
‎2009 Feb 13 7:11 AM
Hi,
I am sending a report program,
execute it and provide the tcode in it, it will list all the user exit in the tcode.
<< Irrelevent, unattributed cut and paste from http://www.sap-img.com/ab038.htm removed >>
Edited by: Rob Burbank on Feb 13, 2009 3:29 PM
‎2009 Feb 13 9:15 AM
Hello,
For user exit.
goto to tcode->status->program name->double click on that,
then goto to-> attribute take the package name and
Goto SMOD tcode ->Utilities->give the package name and F8
then a list of exits will display for that tcode as well as that package.
u can check the table MODSAP
For BADI's,
1)goto to tcode SE24 give the CL_EXITHANDLER and display and then double click on the GET_INSTANCE
keep Break point at this location 'call method cl_exithandler=>get_class_name_by_interface'
then the tcode it will trigger there and we can debugg there we can find badi'for that tcode and then remove the break point.
2)Goto to tcode->status->program name->double click on that program will display's
then press crtl+F then cl_exithandler
for testing u need keep breat-point and run that ...later remove that break-point.
‎2009 Feb 13 9:34 AM
‎2009 Nov 09 5:58 PM
either delete the implementation of OSS notes or do an implicit enhancement