My exit in validation exit dont execute for fb02
Hi guys,
Validation in field BSEG-ZLPRS for FB02 transaction.
1.- i add new form in se38 -> ZGGBR000
FORM u105 CHANGING b_result.
BREAK-POINT.
DATA: znolib LIKE zliber-znolib.
SELECT SINGLE znolib
INTO znolib
FROM zliber
WHERE bukrs = bseg-bukrs AND
username = sy-uname.
IF sy-subrc <> 0.
b_result = b_false.
MESSAGE i031(z001) WITH sy-uname.
ELSE.
IF znolib = 'N'.
b_result = b_false.
MESSAGE i031(z001) WITH sy-uname.
ELSE.
b_result = b_true.
ENDIF.
ENDIF.
ENDFORM.
2.- After activated i use RGUGBR00 for rebuilding validation structures
3.- The condition is SYST-TCODE = 'FB02', cause there is no specific condition, we need to check thhis field for all circunstances
I have all ok in ggb0
Best regards
Jua
Not solved yet...
in table GB01 i have:
BOOLCLASS = 9
CLASSTYPE = B
BLCTAB = BSEG
BCLFIELD = *
BEXCLUDE = ' '
Since i am not sustituying the field only validating its not necessary to change....
But my exit still not working
Best regards
Juan
Similar Messages
-
Field exits dont work for ENJOY trx
HI All,
May I know why field exits do not work for ENJOY transction codes.
Is this same case with User exits and screen exits??
Please make me clear on this.
SatishI guess field exits have been removed in the recent versions and enjoy transactions are the latest one, SAP has not incorporated the same.
However, user exits will work with all transactions in the latest versions as well.
regards,
Ravi
Note : Please mark all the helpful answers -
FBCJ BADI/User Exit or Validation Rule Implementation
Inspite of my maintaining validation as under, i am not able to achieve what i desire, i.e., System is still posting Cash transactions thru FBCJ t code for amount exceeding INR 50,000
1. Created a validation name
2. Assigned it to Application Area - FI
3. Callup Point - 2 Line item
4. In validation step 0001, created pre-requisite as
Transaction code = 'FBCJ' AND Account Type = 'D' AND
Posting key = '15'
5. Under check, Amount <= '50000.00'
6. Entered E in message type with corresponding message class ZKM_MSG_CLASS for message number 018
7. Assigned the above validation in OB28 t code for activation level 1 (i.e., Active)
System display a message; but also post it as well, despite of 'E' error message type.
How to tackle with the above problem.
Is there any other badi/user exit for FBCJ. I have only find CJ_DOCUMENT, but it's not working for me.
Thanks and Regards,
SohailHi
Below are some of BADIs available for WAK1. Please check.
Exit
WCOUP001 User exit for coupon processing in POS inbound
BADIs
RDM_BAPI_PROMO_CREATE - Enhancement Spot (RDM_OPT_PROMO_IN)
RDM_PROMO_POST - Enhancement Spot
RDM_PROMOTION_WAK1 - Enhancement Spot
WAKT_BADI_001 -
~~~Ganesh Kumar K. -
Hi,
I had setup a FI validation exit. In the source code of this validation, I raise an error message, if any. For example:
LOOP AT t_messages_return.
MESSAGE ID t_messages_return-id TYPE t_messages_return-type
NUMBER t_messages_return-number
WITH t_messages_return-message_v1
t_messages_return-message_v2
t_messages_return-message_v3
t_messages_return-message_v4.
ENDLOOP.
The validation is working fine, and it's not allowing user to continue document posts while error exists. The problem is that between my custom message error display and system come back to input screen, there's a popup raised by standard code:
"Correct the error reported before on the next screen".
User doesn't want this message being displayed, since it's an Information Message (like i000). Is there any way to disable this message ? It's raised by standard code just after my custom message code...
Thanks
RodrigoIs the user exit used in defining validation step in Tx:GGB0?
It's not good practice to issue error message in validation user exits, because document postig transactions are used in BDC sessions by SAP standard FI programs.
Instead of raising error in user exit, set B_RESULT = B_FALSE and issue generic message in message part of validation.
Check the validation definition in GGB0, message you are gettinin might be defined in the validation, removing it might not show the message.
Regards
Sridhar -
Regarding Exit of validation in SPRO
Hi All,
Normally for user exits the system should not ask for the Access key. But the exits of validations in tcode 'SPRO' it is asking for the acess key. It is creating some sort of confusion.plz clarify.
Regards
PrashanthHi prashanth,
1. customer exits (using CMOD, SMOD)
won't ask for access key.
2. But user-exits, (especially in SD Module)
have some Z INCLUDE,
which needs to be modified,
for writing our code.
So, only for the first time, it will ask for access key.
regards,
amit m. -
Help needed on Validation exit GGB0
Hi Guys,
Pls suggest how can i go about using exit validation for callup point 3(complete document level).
i am trying to call form U101, but its not getting called.
below is the code for this form.
FORM U101 *
Example of an exit using the complete data from one *
multi-line rule. *
This exit is intended for use from callup point 3, in FI. *
If account 400000 is used, then account 399999 must be posted *
to in another posting line. *
--> BOOL_DATA The complete posting data. *
<-- B_RESULT T = True F = False *
FORM u101 USING bool_data TYPE gb002_015
CHANGING b_result.
DATA: b_acc_400000_used LIKE d_bool VALUE 'F'.
Has account 400000 has been used?
LOOP AT BOOL_DATA-BSEG INTO BSEG
WHERE HKONT = '0000400000'.
B_ACC_400000_USED = B_TRUE.
EXIT.
ENDLOOP.
Check that account 400000 has been used.
CHECK B_ACC_400000_USED = B_TRUE.
B_RESULT = B_FALSE.
LOOP AT BOOL_DATA-BSEG INTO BSEG
WHERE HKONT = '0000399999'.
B_RESULT = B_TRUE.
EXIT.
ENDLOOP.
lemi knw the process to call validation exit at complete document level (callup point 3).
actually i am not able to pass parameter bool_data. plz suggest wht do v do for tht.
Rgrds,
Prash
Edited by: Prashant Malik on Sep 11, 2008 12:00 PMHi Prash,
in ZGGBR000 (copy of RGGBR000) you have to add your exit to internal table exits e.g.
Einfügen von U535 NB20081022
exits-name = 'U535'. "NB20081022
exits-param = c_exit_param_class. "NB20081022
exits-title = text-535. "NB20081022
APPEND exits. "NB20081022
The value c_exit_param_class for exits-param will provide you after creating the step in validation (transaction GGB=) below coding for the call of the exit in my exmaple in include GBTASFIF. With the vlaue c_exit_param_none it doesn't work. I did the same error.
FORM VALCHCK_2FI_BELG003
USING
BOOL_DATA
CHANGING
RES000.
DATA: RES001 LIKE D_BOOL.
Exit-Evaluation :RES000 *
RES000 = B_TRUE.
PERFORM U535(ZGGBR000)
IF FOUND
USING
BOOL_DATA
CHANGING
RES000.
ENDFORM. " VALCHCK_2FI_BELG003
Hope that solved your problem.
Regards
Norbert -
Exit Code 6 error on Mac for Photoshop cs6
Tried going through help sites for days finding a fix for Exit Code 6. None of the solutions have worked this far.
No errors when installing the trials for Ai, Id, and Acrobat CS6 on my Mac (which runs OS X version 10.9.2, Mavericks), but the same error always occurs when installing the trial for Ps CS6.
Here is the error summary:
Exit Code: 6
Please see specific errors and warnings below for troubleshooting. For example, ERROR: DF015, DW063 ...
-------------------------------------- Summary -------------------------------------- - 0 fatal error(s), 4 error(s), 0 warning(s)
----------- Payload: {9124DF4E-617D-486B-A970-8FA632244F24} Adobe Photoshop CS6 Core 13.0.0.0 -----------
ERROR: DF015: Unable to delete symlink "/Applications/Adobe Photoshop CS6/Adobe Photoshop CS6.app/Contents/Frameworks/amtlib.framework/Resources"(Seq 524)
ERROR: DW063: Command ARKDeleteSymlinkCommand failed.(Seq 524)
ERROR: DW050: The following payload errors were found during install:
ERROR: DW050: - Adobe Photoshop CS6 Core: Failed due to Language Pack installation failure ERROR: DW050: - Adobe Photoshop CS6 International English Language Pack_AdobePhotoshop13-en_GB: Install failed
Ran EtreCheck and got this report:
EtreCheck version: 1.9.11 (43) - report generated May 30, 2014 at 8:19:51 AM GMT+8
Hardware Information:
iMac (21.5-inch, Late 2012)
iMac - model: iMac13,1
1 2.7 GHz Intel Core i5 CPU: 4 cores
8 GB RAM
Video Information:
NVIDIA GeForce GT 640M - VRAM: 512 MB
System Software:
OS X 10.9.2 (13C64) - Uptime: 0 days 1:3:32
Disk Information:
APPLE HDD ST1000LM024 disk0 : (1 TB)
EFI (disk0s1) <not mounted>: 209.7 MB
Macintosh HD (disk0s2) / [Startup]: 999.35 GB (907.56 GB free)
Recovery HD (disk0s3) <not mounted>: 650 MB
USB Information:
HP Deskjet D2300 series
Apple Inc. BRCM20702 Hub
Apple Inc. Bluetooth USB Host Controller
Apple Inc. FaceTime HD Camera (Built-in)
Thunderbolt Information:
Apple Inc. thunderbolt_bus
Gatekeeper:
Mac App Store and identified developers
Kernel Extensions:
[not loaded] com.silabs.driver.CP210xVCPDriver (3.0.0d1) Support
[not loaded] com.silabs.driver.CP210xVCPDriver64 (3.0.0d1) Support
[not loaded] com.wacom.kext.wacomtablet (6.3.7 - SDK 10.8) Support
Launch Daemons:
[loaded] com.adobe.fpsaud.plist Support
[loaded] com.adobe.SwitchBoard.plist Support
[loaded] com.microsoft.office.licensing.helper.plist Support
Launch Agents:
[not loaded] com.adobe.AAM.Updater-1.0.plist Support
[running] com.wacom.wacomtablet.plist Support
User Launch Agents:
[loaded] com.adobe.AAM.Updater-1.0.plist Support
[loaded] com.adobe.ARM.[...].plist Support
[loaded] com.google.keystone.agent.plist Support
User Login Items:
iTunesHelper
Google Drive
Android File Transfer Agent
Internet Plug-ins:
FlashPlayer-10.6: Version: 13.0.0.214 - SDK 10.6 Support
QuickTime Plugin: Version: 7.7.3
AdobePDFViewerNPAPI: Version: 10.1.10 Support
AdobePDFViewer: Version: 10.1.10 Support
Flash Player: Version: 13.0.0.214 - SDK 10.6 Support
Default Browser: Version: 537 - SDK 10.9
SharePointBrowserPlugin: Version: 14.1.0 Support
WacomNetscape: Version: 2.1.0-1 - SDK 10.8 Support
Silverlight: Version: 5.1.30317.0 - SDK 10.6 Support
WacomTabletPlugin: Version: WacomTabletPlugin 2.1.0.2 Support
JavaAppletPlugin: Version: 14.9.0 - SDK 10.7 Check version
Audio Plug-ins:
BluetoothAudioPlugIn: Version: 1.0 - SDK 10.9
AirPlay: Version: 2.0 - SDK 10.9
AppleAVBAudio: Version: 203.2 - SDK 10.9
iSightAudio: Version: 7.7.3 - SDK 10.9
iTunes Plug-ins:
Quartz Composer Visualizer: Version: 1.4 - SDK 10.9
3rd Party Preference Panes:
Flash Player Support
WacomTablet Support
Time Machine:
Time Machine not configured!
Top Processes by CPU:
1% WindowServer
0% fontd
0% Google Drive
0% dpd
Top Processes by Memory:
197 MB mds_stores
147 MB Google Chrome
106 MB Finder
90 MB WindowServer
90 MB com.apple.IconServicesAgent
Virtual Memory Information:
4.36 GB Free RAM
2.09 GB Active RAM
749 MB Inactive RAM
827 MB Wired RAM
2.09 GB Page-ins
0 B Page-outs
I don't know what to do! Help!The following help document might help:
Exit Code: 6, Exit Code: 7 Installation Errors - http://helpx.adobe.com/creative-suite/kb/errors-exit-code-6-exit.html -
Hi all
I've got a error msg when try to generate a report using Cisco history report tool:
Error | An Exceptional Error occurred. Application exiting. Check the log file for error 5022
It only happens when choose report template: ICD_Contact_Service_Queue_Activity_by_CSQ_en_us.
User tried samething on other PC, it working fine.
only on user' own PC and only choose this report, error appears.
user runing windows 7 and do not have crystal report installed
tried reinstalled the software, doesn't work.
also tried this: (https://cisco-support.hosted.jivesoftware.com/thread/2041254) - doesn't work
then tried https://supportforums.cisco.com/docs/DOC-6209 - doesn't work
attached the log file.
thanks.wenqianyu wrote:From the log file:Looks like you get a Login Window.Error message showed up after username/password be enteredThere is an error in the log: Error happened in comparing UCCX version and HRC versionYou may need to do a clean uninstall, download the Historical report from the server, and install it again on the PC.Does this only happen to one PC or to every PC with this application?Wenqian
I have completely uninstalled the HRC, and download from server install again -- still doesn't work with exactly same error.
this matter only happens on this PC, when user try same thing on other PC, it works.
so i think it not relate to server or account. -
Custom Exit Button not working..looks for required input field on screen?
I defined this EXIT button as type E in Menu Painter.
I am using "MODULE At EXIT-COMMAND" in my PAI.
SAP message still asks for the required input field when I select the function EXIT button?
The logic still will not break into the At EXIT-COMMAND of my PAI?
Thank-You.Hi
Have you assigned variable OK_CODE in the list of screen element?
IF NOT zin_railid is initial.
LEAVE TO SCREEN 0100.
ENDIF.
Which is the sense to create a button for exit-command and doesn't allow the exit if the input field is empty?
In SE41 I entered "Back" over the back button, "EXIT" over the exit button, and "CANCEL" over the cancel button.
I selected each one, and got a popup to enter "E" for each type. As I said they appear, but do nothing?
Did I need to set a status for these?
No you don't, it's only important to define a functional having the attribute for EXIT-COMMAND
Max
Max
Edited by: max bianchi on Nov 5, 2010 6:31 PM -
Update Bool_data during validation exit
Hello Experts,
Is it possible to update the Bool_data fields during validation Exit ? I tried Update and Modify but not working.
Example,
Lv_text = 'TEST01'.
Bool_data-bseg-sgtxt = Lv_text.
so after posting, we will find the FI document line item text = TEST01.
I do not want to use substitution, so please avoid that
Thank youHello Krishna,
You can not during a Validation Exit update the Bool_data fields.
To do so, SAP have created substitutions. -
User exit or cutomer exit for migo?
HI friends,
Could anyone help me by providing the customer exit or user exit that need to triggered while saving in MIGO txn.
Thanks & Regards,
Sathish Kumar.Enhancement
MB_CF001 Customer Function Exit in the Case of Updating a Mat. Doc.
MBCF0011 Read from RESB and RKPF for print list in MB26
MBCF0010 Customer exit: Create reservation BAPI_RESERVATION_CREATE1
MBCF0009 Filling the storage location field
MBCF0007 Customer function exit: Updating a reservation
MBCF0006 Customer function for WBS element
MBCF0005 Material document item for goods receipt/issue slip
MBCF0002 Customer function exit: Segment text in material doc. item
Business Add-in
MB_RESERVATION_BADI MB21/MB22: Check and Complete Dialog Data
MB_QUAN_CHECK_BADI BAdI: Item Data at Time of Quantity Check
MB_PHYSINV_INTERNAL Connection: Core Inventory and Retail AddOn
MB_MIGO_ITEM_BADI BAdI in MIGO for Changing Item Data
MB_MIGO_BADI BAdI in MIGO for External Detail Subscreens
MB_DOC_BADI_INTERNAL BAdIs when Creating a Material Document (SAP Internal)
MB_DOCUMENT_UPDATE BADI when updating material document: MSEG and MKPF
MB_DOCUMENT_BADI BAdIs when Creating a Material Document
MB_CIN_MM07MFB7_QTY Proposal of quantity from Excise invoice in GR
MB_CIN_MM07MFB7 BAdI for India Version exit in include MM07MFB7
MB_CIN_LMBMBU04 posting of gr
MB_CHECK_LINE_BADI BAdI: Check Line Before Copying to the Blocking Tables
ARC_MM_MATBEL_WRITE Archive AddOn-Specific Data for MM_MATBEL
ARC_MM_MATBEL_CHECK Check AddOn-Specific Criteria for MM_MATBEL
Try this user exits & badis.
Regards,
Madan. -
Menu exit ( or ) Screen exit for tcode VF01
Hi,
Can you tell me menu exit or screen exit for this tcode VF01.
Thanks,
Prathap.Hi,
der r total 17 exit.
J_3RSINV
SDVFX001 User exit header line in delivery to accounting
SDVFX002 User exit for A/R line in transfer to accounting
SDVFX003 User exit cash clearing in transfer to accounting
SDVFX004 User exit G/L line in transfer to accounting
SDVFX005 User exit reserves in transfer to accounting
SDVFX006 User exit tax line in transfer to accounting
SDVFX007 User exit: Billing plan during transfer to Accounting
SDVFX008 User exit: Processing of transfer structures SD-FI
SDVFX009 Billing doc. processing KIDONO (payment reference number)
SDVFX010 User exit item table for the customer lines
SDVFX011 Userexit for the komkcv- and kompcv-structures
V05I0001 User exits for billing index
V05N0001 User Exits for Printing Billing Docs. using POR Procedure
V60A0001 Customer functions in the billing document
V60P0001 Data provision for additional fields for display in lists
V61A0001 Customer enhancement: Pricing
Hope it helps.
/sachinkumar. -
User exit/ badi for fb02 transaction
Hi,
what are the appropriate user exit/ badi for fb02 transaction for a disabling(graying out) a
payment block field for particular users..?
Regards,
AviFollowing are the exits available for FB02
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) -
EXIT BUTTON - PAGE NOT FOUND issue for Address
After customization of home page, we are getting page not found error for the Exit button in Address and in some other applications, it is opening a new window and in some other applications, the screen is getting struck and the backend user id is getting locked.
Could some one suggest me ? I feel we make the exit button invisible so that end user will not click on that totally. Is this a good idea?You can of course hide the exit buttin via personalisation
read the sap note 951257 for the issue you are having
The solution is to go and make the necessary entries.
- Go to V_T7XSSSERARBC view.
- Select the Area for which the exit button is not working.
- Enter 'Area Link Type' if not entered already.
- Enter 'Link Resource' if not entered already.
- Save the changes made.
With regard to the WorkProtect Mode, Ifollow the note #734861 -
"WorkProtect Mode - Global Settings".
also check the steps here
While creating an iView instance there are two option
-paste
-paste as delta link
You should choose paste as delta link option.
Please check the link for more information-
http://help.sap.com/saphelp_NW04s/helpdata/en/f5/eb515d0e6a11d7b84900047
582c9f7/frameset.htm
We checked the attachments, it seems that when you run the application
from preview mode you will not see 'exit' button. If you run the
application directly you will not see 'exit'button.
'Exit' button feature comes into picture when you consider that
application should use home page customizing feature. -
hi everyone,
can you send me some examples on menu exits and screen exits.
thank you.
preethamHi Preetham,
In older versions MENU Exits approached through Transaction CMOD by creating
PROJECTS and activating the project and assigning Program to that
Transaction Codes. For MENU Exits, Transaction Codes will be starting with
"+" sign and with default text "NODE TEXT NOT FOUND" for which you can
assign your Report or Dialog Program etc., (for Eg:- +DW4 MENU Exits
Transaction available in TOOLS --> ABAP Workbench --> Utilities --> <Node
Text Not found>).
Procedure for Creating MENU Exits.
1) To get into Area Menu Maintenance Screen Type SE43 T.Code in Command
Line.
2) In Area Menu Paramenter type 'S000' (S triple Zero)
3) Then Press Change Icon in Application Tool Bar. Then It may ask for
Access Key [or] it may display "Specify Processing mode" window. If it ask
for the Access Key Check for the availability of OSS Note and apply to open
Standard SAP Menu to include MENU Exits. Otherwise, if it display "Specify
Processing mode" window with Three Push Button. In which select "Change" and
proceed further.
4) Then it will display "Information" window with the following information
"Caution : The Original Language of the structure is German (editing lang. :
English) ". Then press "Enter Key to proceed further.
5) Then you will get into "Edit Area Menu S000".
6) for eg:- Expand Tools Menu.
7) Then Press ABAP Workbench <Icon>.
8) Then you will get into ABAP Workbench Menu Tree.
9) Then Expand Utilities Menu.
10) In the last line you will find one MENU EXIT Provision to include your
own menu. "Node Text Not Found" This text can be change by double Clicking
that. There you can find the T.Code. Here for Eg:- "+DW4".
11) for eg: - Here change the Text to "Sample Menu Exit" and then note down
the T.Code "+DW4".
12) Then Save with Change Request Number and come out of Transaction SE43.
13) Then Goto Transaction SE93.
14) Then type T.Code "+DW4" and press Create.
15) Then proceed further to create transaction called "+DW4".
I hope this could help you in Creating Menu Exit...
Creating menu exits
http://help.sap.com/saphelp_nw04/helpdata/en/c8/19762743b111d1896f0000e8322d00/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/83/7a18cbde6e11d195460000e82de14a/frameset.htm
For screen exits.
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
Screen exits add fields to screens in R/3 applications. SAP creates screen exits by placing special subscreen areas on a standard R/3 screen and calling a customer subscreen from the standard screens flow logic.
the tcode is cmod...
1.From the main screen of the Project management transaction, proceed as follows:
Select Enhancement components and choose Change.
2.Choose Edit component.
3.Choose the screen exit and double click on it
4.Create your subscreen using the Screen Painter.
5.Design your screen to be added to the standard screen and activate the particular screen and return back to the flow logic .
6.Choose the PAI and PBO to write down the logic.
7.Generate your screen and choose Back (the green arrow) to return to the Project management transaction.
8.Go to the transaction ME22 to view the customer defined screen exit.
9.Enter the purchase order number and press Enter.
10.Go to the menu header --> Details.
11.Purchase number is visible on the standard screen
check the foll link,
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
Menu exits allow you to add your own functions to the pulldown menus in standard R/3 transactions. To take advantage of a menu exit, you first need to create a project as described in the section Creating an add-on project. Then, you must include the SAP enhancement package that contains the menu exit you want to use in your project. From the main screen of the Project management transaction, proceed as follows:
Select Enhancement components and choose Change.
The system lists all customer exits contained in the enhancements included in your project.
Place the cursor on the menu exit you want to add your own function to.
Choose Edit component.
The system displays technical information about the menu entry. It also displays two input fields where you can specify a language and the text you want your menu item to have.
Enter the name of your menu function (such as Special order method) in the field New text.
Choose Save text.
Your special menu function will not appear in the pulldown menu of the corresponding standard transaction until you activate your enhancement project.
Specifying a menu text and activating your project are not the only steps you need to take to make your own menu item work. After you carry out these steps, your menu item will appear, but it will not call a corresponding function. To attach your menu entry to its corresponding function, you need to create a function module for the function module exit associated with your menu text. This function module exit is part of the same SAP enhancement that contains the menu exit you used. Creating Customer-Specific Function Modules tells you more about how to use function module exits.
also refer
MEnu Exit
http://www.sap-img.com/abap/what-is-user-exits.htm
Creating menu exits
http://help.sap.com/saphelp_nw04/helpdata/en/c8/19762743b111d1896f0000e8322d00/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/83/7a18cbde6e11d195460000e82de14a/frameset.htm
For screen exits.
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
chech these links for user exists its usefull
http://www.allsaplinks.com/user_exit.html
Re: Screen exit
user exit and customer exit
http://help.sap.com/saphelp_47x200/helpdata/en/dd/561602545a11d1a7020000e829fd11/frameset.htm
http://www.sap-basis-abap.com/sapab013.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
How to implement screen exit for a SAP standard transaction
Introduction
SAP provides standard transactions to enter data into database. But a client may want to maintain some additional information in SAP other than what is provided.
To make provisions for this, additional screens have to be provided and additional fields must be added into appropriate database table.
To pave way for this, SAP has provided the option for screen exits. Usually, SAP provides the following:
An append structure in the database table with the new fields.
A subscreen area into the standard screen where the programmer can attach his subscreen of his own program with the new fields.
A function group under which the new subscreen has to be created with the new fields.
Function exits to synchronize the PBO and PAI of the standard SAP program with the PBO and PAI of the subscreen so that data can flow back and forth between the standard SAP program and the program written by the developer for the subscreen. These function modules also exist in the same function group under which the subscreen will have to be developed.
Finally, a linkage has to be done between the subscreen area of standard SAP screen with the custom subscreen constructed by the developer.
Typically, SAP provides an enhancement in which the developer can create an append structure, use the function exits to synchronize the PBO and PAI of the standard SAP program and the custom subscreen program, and make the necessary linking( as mentioned above in step 4. But, again, this is not a hard and fast rule. Linking in some case, is also done by configurations.) SAP also usually provides the name of the function group under which the subscreen has to be developed.
Necessary guidance about implementing a screen exit development is usually available in the Documentation section of the enhancement ( can be availed by transaction SMOD).
Pre-Requisites
The developer to work on screen exit should have essential knowledge on the following:
DDIC concepts, including the knowledge of append structure.
Concept of SAP Enhancements and implementing them using Projects.
Concept of function exits.
Knowledge on Module Pool including subscreens, Tabstrip controls etc.
Steps
Guidelines
So, a developer can follow the guidelines mentioned below to implement a screen exit to a standard SAP transaction, as and when required:
Find out the Required Enhancements
Go to SMOD. Press F4 in the Enhancement field. In the next popup window, click pushbutton SAP Applications. A list will appear that contains information on all the enhancements, categorized under functional areas. Developer must search for the enhancements relevant to his functional area of interest for e.g., Purchasing, Asset Accounting, etc.
Note down the enhancements. Then, come to the initial screen of SMOD and view the documentation of each enhancement to find out which one is required for your development.
Utilize the Enhancement in a Project
After you have found one, do as directed in the documentation. Generally, the steps are as follows:
Create a project using CMOD including your enhancement.
Create the append structure with new fields.
Go to the desired function group and create a subscreen with the new fields. Write PBO and PAI for the subscreen, if required.
Use the function exits in the enhancement to link the PBO and PAI of the subscreen with that of the main SAP program supporting the SAP transaction.
Maintain necessary linkage between the subscreen area of standard SAP program with the custom subscreen developed along with the custom program name. This can be done in the project (developed by CMOD including the enhancement) or outside as a part of configuration.
Activate the project.
Test to ensure that required functionality are met.
Case Study 1
Add three new custom fields for Asset master and maintain information for them
Requirement
Three fields in the legacy system have to be maintained in Asset master. These fields are:
Original Asset number 20 characters
Location 2 15 Characters.
Model no 20 characters
Location 2 should start with L.
Pre-Analysis
Finding out the Enhancement
As described above, the enhancement is determined. It was found, that enhancement AIST0002 will serve the purpose. It contains the following components (can be viewed by transaction SMOD):
Exit Type Description EXIT_SAPL1022_001 Function Exit Check of User-Defined Fields when Using Create and Change BAPI EXIT_SAPLAIST_002 Function Exit Transfer Data for User Subscreens in PBO. EXIT_SAPLAIST_003 Function Exit Transfer of User-Defined Fields to SAP Master Data Transactions CI_ANLU Customizing Include Include structure to add new fields
Studying the Function Exits
The function module level documentation for the function exits are then viewed from transaction SE37. The documentation clearly laid out for the purpose for their use:
EXIT_SAPLAIST_002
Function module Level Documentation
This function module is called by asset master data maintenance at the start of the dialog. (When changing, it is called after reading of the data from the database; when creating it is called after the transfer of the default values from the asset class and reference asset.) The purpose of the function module is to enable this function group to recognize the master data. For interpreting or controlling master data fields that are important for user fields, it is possible to transfer to global variables at this point, so that they can be recognized when the user subscreens are processed.
Import Parameters
Understanding
This function module is called at the PBO to pass the information retrieved from the database to pass them to the custom subscreen and its underlying program. Import parameter : I_ANLU will be populated with the values for user-defined fields which will be passed to the subscreen program. So, there must be some sort of variable assignment from I_ANLU.
EXIT_SAPLAIST_003
Function module Documentation: This function module is called by SAP asset master data maintenance after the screens are processed, but before saving. The purpose of the function module is to transfer fields entered on user sub-screens of SAP asset data maintenance to the database for updating. The export parameter for this function module is:
Understanding
This function module will be used to transfer the user entered data in the subscreen fields to the main SAP program, which will then be saved into the database.
Studying the Documentation of the Enhancement
The enhancement documentation (as is viewed from the initial screen of SMOD] also supports the idea. Moreover, it informs that we need to develop a subscreen under function group XAIS. This is the function group under which the two function exit modules also exist. So, if the custom subscreen refers to the global data of the function group XAIS, then those values will also be available to these function exits as well.
Going to SE80 and viewing the function group XAIS helps us to inform that there are three DDIC tables declared for it:
Deciding the Final course of Action
After making all the investigations, the final course of action was determined.
SrlNo Step Justification
A project has to be created using transaction CMOD where the enhancement AIST0002 will be included.
Customizing include CI_ANLU has to be created with the custom fields demanded When CI_ANLU will be developed, the custom fields will get appended to the database table ANLU. Also, these fields will be used to create screen fields in the new subscreen.
A custom subscreen, say, 9000 will be developed under function group XAIS. The screen group for the screen will be CUST (or any name). The three custom fields added to table ANLU (by creating CI_ANLU) will be used to create new fields in the screen.
In the PAI of the subscreen, validation for Location to start with L will be added. The subscreen with three new fields has to be developed so that it can be attached to a subscreen area of the asset master screens.
In the custom include of the function exit module EXIT_SAPLAIST_002, the following code will be written:-
ANLU = I_ANLU. I_ANLU is the import parameter of this FM. The value is assigned to the global variable ANLU, referring which the three new subscreen fields are developed. So, data retrieved from database table ANLU will be passed to this FM as I_ANLU by the standard SAP main program. The value will be taken and passed to the global variable of the function group XAIS, so that the three custom fields (referring to ANLU of XAIS) get populated.
In the custom include of the function exit module EXIT_SAPLAIST_003, the following code will be written:-
E_ANLU = ANLU. The changed values in the subscreen fields exist in global variable ANLU for the function group XAIS. This function exit module will pass the data back to the SAP main program as E_ANLU.
Proper linkage/configuration has to be done so that the new subscreens get linked to the appropriate subscreen area of the Asset master screen. This has to be done otherwise, the new custom subscreen will not be displayed in the Asset master screens.
Development
Creating a Project to include the enhancement
Go to transaction CMOD and create a project.
Enter a description for the project. Then, click on the pushbutton Enhancement Assignments in the Application Toolbar.
Enter the name of the enhancement and Save.
Go to Components.
Creating Custom Include for ANLU
The screen shown below will appear, showing all the enhancement components under the assignment AIST0002. Double-click on the name of the Include Structure to create it.
Create the include structure with three new fields, as required. Then, save and activate it.
Develop the subscreen and the program
Go to transaction SE80. For the function group XAIS, create a new subscreen 9000.
Create it as subscreen.
Then, go to the Layout of the screen and create three new fields from Database table ANLU.
Drag the fields in the screen body and place them.
Then, save and activate the screen and come back to screen flow editor.
Create the PAI module to add validation for field Location 2, as required .
Activate the whole function group and come out.
Write code in the Function Exits to synchronize the programs
Now, code has to be written in the function modules EXIT_SAPLAIST_002 and EXIT_SAPLAIST_003 so that data flows to and fro between the main SAP program and custom subscreen program. For that, go back to transaction CMOD and change the function exits.
Write code in the function module EXIT_SAPLAIST_002 called once at the beginning of the transaction:
Write code in EXIT_SAPLAIST_003 to pass the data from the subscreen to SAP main program.
Then, activate everything the whole project and come out.
Complete the configuration to link the subscreen
The development portion is complete. Now, linking of the subscreen has to be done with the subscreen area of the main program. In most of the cases, this linking can be done in the enhancement itself. But, here, requirement is a bit different. It is done by configuration using SPRO.
Assets are created under Asset class. And for each asset class, there is a layout assigned to it. For a layout, there are multiple tab pages assigned to it. And, for each tab page, there are multiple screen groups/field groups assigned.
Here, the requirement is to create these three custom fields in the tab page General of asset master screen ( AS01/AS02/AS03/AS91).
Determine the Layout
To achieve this, first of all, we need to find out which layout is assigned to asset class 1000.For that, go to transaction AOLK( information has to be obtained from functional consultant).Select the Asset Class 1000 and click on folder General Assignment of Layout.
Here, for Asset class 1000, for all the user groups, tab layout SAP is assigned. Since layout SAP cannot be changed, it has to be copied and manipulated to include our screen group. Later, the new layout has to be assigned over here.
Create new tab layout
Go to transaction AOLA. Copy the tab layout SAP to create another layout, say, YSUB.
System will copy all the settings and will inform you about that.
Select your newly created layout and double-click on the folder Tab page titles.
You want to put your custom fields in the tab page General. So, select this tab page entry and double-click on the folder "Position of Groups".
Here, all the field groups currently residing in the tab-page General are shown. Add an entry for your newly created fields.
Select the group box from the list. An entry will come with U padded with the custom subscreen prepared by you.
Then, save and come out.
Assign the new Layout to Asset Class
Now, go to tcode AOLK and assign tab layout YSUB for asset class 1000.
Save and come out.
Test the Exit
Everything is over. Now, go to transaction code AS01/02/03 or AS91 to deal with an asset of asset class 1000. You will see your new fields added to the screen. Add values to them save. Then, enter into the tcodes again to see whether the values entered by you are being displayed or not.
Original Source: ittoolbox.com
MENU
refer
MEnu Exit
just refer to the link below for step by step procedure with screen shots
http://www.sapmaterial.com/?gclid=CN322K28t4sCFQ-WbgodSGbK2g
Check this link:
http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975e643b111d1896f0000e8322d00/frameset.htm
Menu exits allow you to add your own functions to the pulldown menus in standard R/3 transactions. To take advantage of a menu exit, you first need to create a project as described in the section Creating an add-on project. Then, you must include the SAP enhancement package that contains the menu exit you want to use in your project. From the main screen of the Project management transaction, proceed as follows:
Select Enhancement components and choose Change.
The system lists all customer exits contained in the enhancements included in your project.
Place the cursor on the menu exit you want to add your own function to.
Choose Edit component.
The system displays technical information about the menu entry. It also displays two input fields where you can specify a language and the text you want your menu item to have.
Enter the name of your menu function (such as Special order method) in the field New text.
Choose Save text.
Your special menu function will not appear in the pulldown menu of the corresponding standard transaction until you activate your enhancement project.
Specifying a menu text and activating your project are not the only steps you need to take to make your own menu item work. After you carry out these steps, your menu item will appear, but it will not call a corresponding function. To attach your menu entry to its corresponding function, you need to create a function module for the function module exit associated with your menu text. This function module exit is part of the same SAP enhancement that contains the menu exit you used. Creating Customer-Specific Function Modules tells you more about how to use function module exits.
User exits (Function module exits) are exits developed by SAP. The exit is implementerd as a call to a function module. The code for the function module is written by the developer. You are not writing the code directly in the function module, but in the include that is implemented in the function module.
The naming standard of function modules for functionmodule exits is:
EXIT_<program name><3 digit suffix>
The call to a functionmodule exit is implemented as:
CALL CUSTOMER.-FUNCTION <3 digit suffix>
To find a Exit.
Goto Transaction -- Find The Package
SMOD >f4>Use the Package here to Find the Exits In the Package.
Else if you Want to search by Application Area wise ,
There is one more tab to find the Exits in the Respective Application Area.
Implementing the Exit-- CMOD Create ProjectsAssgn your Component .
Now Run ur Transaction to Check if it Triggers.
Thats it..
Suppose you need to find out all the user exits related to a tcode.
1. Execute the Tcode.
2. Open the SAP program.
3. Get the Development Class.
4. Execute Tcode SE84.
5. Open the Node 'Envir. -> Exit Techniques -> 'Customer Exits -> Enhancements'
6. Enter the Development class and execute.
Check out this thread..
The specified item was not found.
1. Type the transaction : system->status-> <PROG. NAME>
2 open SE37 , type EXIT<PROG NAME> and press F4 to get the list of function exits available.
3. Open CMOD utilities->SAP enhancements
EDIT->All selections
4.type the function module name obtained in step 2, in fields 'component name' in 'additional selections' block. and execute.
5. The displayed list contains the enhancements names for the transaction You were looking for.
6. Create a project in CMOD and the code in default include->activate.
http://www.erpgenie.com/sap/abap/code/abap26.htm
which gives the list of exits for a tcode
http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec079f5db911d295ae0000e82de14a/frameset.htm
For information on Exits, check these links
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sapgenie.com/abap/code/abap26.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
http://www.easymarketplace.de/userexit.php
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sappoint.com/abap/userexit.pdfUser-Exit
http://www.planetsap.com/userexit_main_page.htm
User-Exits
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sap-img.com/ab038.htm
http://www.planetsap.com/userexit_main_page.htm
http://www.sap-basis-abap.com/sapab013.htm
http://sap.ittoolbox.com/documents/popular-q-and-a/user-exits-for-the-transaction-code-migo-3283
These links will help you to learn more on user exits.
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/frameset.htm
http://www.planetsap.com/userexit_main_page.htm
http://www.allsaplinks.com/user_exit.html
www.sap-img.com/abap/what-is-user-exits.htm
Also please check these threads for more details about user exits.
Re: Screen exit
user exit and customer exit
user exit
1. Document on UserExits in FI/CO
http://www.ficoexpertonline.com/downloads/User%20ExitsWPedit.doc
2. Finding User Exits...
http://sap.ionelburlacu.ro/abap/sap2/Other_Useful_Tips.html#Finding_User_Exits
3. List of all User Exits...
http://www.planetsap.com/userexit_main_page.htm
Reward points if helpful.
Thanks
Naveen khan
Message was edited by:
Pattan Naveen
Maybe you are looking for
-
Can not Upgrade Snow Leopard to Mountain Lion due to Bootcamp
This is a long standing problem I had since I bought my Macbook Pro (a purchase now I deeply regret) almost two years ago. I keep asking around every few months, to see if anyone came up with a good solution. I hope someone can help me this time When
-
Bluetooth connection with my car SKODA octavia problems
Hi,Please this connection probelm makes me crazy.I purchased a SONY XPERIA Z3 D 6553 and tried several time to connect via bluetooth to the SKODA Octavia multimedia of my car .Unfortunately I cant because when the connection started to establish it a
-
"as of" irregularities...
Hi. I am running the following query - SELECT * FROM analyst AS OF TIMESTAMP TO_TIMESTAMP('2011-03-30 15:00:00', 'YYYY-MM-DD HH24:MI:SS'); where I received the results as expected (same as current). I then ran it with the date 2011-03-29 and again re
-
Dear all can any one help me, i have 8 yrs in sap as an enduser (MM,SD,PP,) i want to learn configharation by my self only, not by going to any institute, so i need a book where i can get with fully screen shot, of mm spro transactions, so that i can
-
Hi few infotypes i didnot find the infotypes litlle confused 3.Multiple field enhancements 4.Union and association membership 5.Applicant marks and dd details 7.previous employee Ei,PF, and gratuity details 8.MOHP incentives 9.Piece rate incentives 1