Posts

Showing posts with the label enhancements

Fixed Value Append to Standard Domains - SAP ABAP DDIC Enhancements.

Image
Fixed value appends are modification-free enhancements. With fixed value appends we can enhance a fixed value range at the domain level. The fixed values restrict users from entering values that are not part of a pre-approved list, such as selecting the type of fare for a flight or add a customer type. Below is a example of adding one new customer (e.g. Executive customer) to a Flight bookings Customer type S_CUSTTYPE. STEP 1:  Open SE11, select Domain, and enter the name of the domain which we want to enhance. Please see below example. I am using the S_CUSTTYPE domain. Click the Display button and Click the Value Range tab STEP 2:  In above screen, Follow menu path Goto > Fixed Value Append. A pop-up dialog box appears. Enter the name of the fixed value append, which must start with Y or Z, and click the OK icon. Please see below screen shots Click Ok and enter name z_new_customer Click OK STEP 3:  Enter a short description for the new f...

Enhancements In SAP ABAP - Interview Guide

Image
Enhancements in SAP ABAP has evolved as mentioned below: SAP Standard Programs Changes Changes are applied directly to SAP standard source code using ABAP editor. In order to change a SAP standard object is required a passcode released by  http://support.sap.com/sscr  using user and password of our customer.  Passcode is generated using object to be changed, installation number and SAP release. User Exits Changes are applied directly to SAP specific include never changed by SAP. A SSCR passcode is required, but is possible to use implicit enhancement. Example: MV45AFZZ (sales order user exit), MV50AFZ1 (deliveries), RV60AFZC (invoices). Call Customer-Function User exits are organized be project definition based on SAP application/module. Project definitions are listed into SMOD transaction. To implement an user exit is required to create a project implementation with CMOD transaction. A project definition can be involved in only one project implemen...

Solution: SAP SD Userexit - Screen Gets Grayed Out after Error Message

Most of the times when you are working on SD User Exit, for example ( MV45AFZZ, UserExit (USEREXIT_SAVE_DOCUMENT_PREPARE)), you get a requirement to display eror messages based on some validations and conditions. When you write something as  MESSAGE e001(ZV),  the error message shows up in the status bar, but the screen gets completely grayed out or say un-editable. To solve such issues what you can do is, replace the message statement MESSAGE e999(ZV). WITH  IF ( vbak-vbtyp = 'H' OR vbak-vbtyp = 'K' ) AND vbak-vgbel IS NOT INITIAL                                                                         AND  t180-trtyp  NE 'A'.     TYPES: BEGIN OF lty_vbrp,              vbeln TYPE vbrp-vbeln,          ...

Sample Program - Find Where Used Exits & Enhancements - Via CMOD & SMOD.

Image
This sample program will help you to find whether a function module exit has already been assigned to any enhancements. Also it will give information regarding Project name & enhancement name related to the function module exit. SAMPLE PROGRAM: REPORT z_test_where_used_exit_smod_cmod. SELECTION-SCREEN BEGIN OF SCREEN 100 AS SUBSCREEN. SELECTION-SCREEN BEGIN OF LINE. SELECTION-SCREEN COMMENT 1(30) userexit FOR FIELD member1. PARAMETERS: member1 TYPE modsap-member. "Function Module (User EXIT) SELECTION-SCREEN END OF LINE. SELECTION-SCREEN END OF SCREEN 100. SELECTION-SCREEN BEGIN OF SCREEN 200 AS SUBSCREEN. SELECTION-SCREEN BEGIN OF LINE. SELECTION-SCREEN COMMENT 1(20) enhname FOR FIELD member2. PARAMETERS: member2 TYPE modact-member. "Enhancement (SMOD) SELECTION-SCREEN END OF LINE. SELECTION-SCREEN END OF SCREEN 200. SELECTION-SCREEN: BEGIN OF TABBED BLOCK mytab FOR 5 LINES, TAB (40) button1 USER-COMMAND push1, TAB (40) button2 USER-COMM...

SAP ABAP - Implementing Or Activate Customer Exits / Function Module Exits.

Image
CMOD & SMOD are two transactions in SAP to manage exits. SMOD simply displays the enhancements present in the SAP System. This transaction is used to see the list of objects in an enhancement. It is a container which holds many related objects within it. CMOD is the project management of SAP enhancements (i.e. SMOD Enhancements). SMOD contains the actual enhancements while CMOD actually is the grouping of the SMOD enhancements. Transactions CMOD n SMOD are 2 parts of the enhancement. Using SMOD you can search for enhancement and their respective component. An enhancement includes one or more components (function exits, menu enhancements and screen enhancements). CMOD transaction code is used to create a project. Project is also a container, which holds several Enhancements. In case we know the user exit, and we have done the necessary changes as per the requirement then it won’t work unless and until a project is assigned to the exit. Hence it’s import...