BTE or EXIT for MR01 t code

Hi,
We are posting the invoice through T code MR01.At the time of posting user will enter Assignment field and item text for vendor line item as mandatory, Now the requirement is to pass the assignment and Item text data entered at vendor line item to be passed on all the line item.
Can anybody suggest BTE , EXIT or BADI for this requirement.

Hi,
Enhancement
MM08R001 User exits for ERS
MM08R002 User exit for tolerance checks
RMVKON00 Enhancements to report "Settle consignment liabilities"
Business Add-in
MR_CIN_LMR1MI2G BAdI for India Version exit in include LMR1MI2G
MR_CIN_LMR1MI2G_SEL BAdi in LIV for determining line selection
MR_CIN_MM08RFS0 BAdI for carrying excise duty to carry invoice verfication
MR_CIN_MM08RFX0 BADi for CVD in MRHR
MR_CIN_RMMR01RS BADI in ERS
Hope this answers your question.
Harini

Similar Messages

User exit for rerapp t-code

Hello,
i m looking for user exit for rerapp t-code but i couldnt find anything about that from internet. it s about e coming invoice. the invoice is being committed from rerapp t-code; then the view is being matched with invoice and clicked documents button. i m looking for a user exit when user click 'documents' button,
Thanks a lot,
Ayşegül

Hi,
Follow this steps, you will get the exact BADI.
1.     Go to the TCode SE24 and enter CL_EXITHANDLER as object type.
2.     In 'Display' mode, go to 'Methods' tab.
3.     Double click the method 'Get Instance' to display it source code.
4.     Set a breakpoint on 'CALL METHOD cl_exithandler => get_class_name_by_interface'.
5.     Then run your transaction.
6.     The screen will stop at this method.
7.     Check the value of parameter 'EXIT_NAME'. It will show you the BADI for that transaction.
Regards
Chaitanya

Find active user exit for a transaction code

Hi All,
Please help to find the active user exit for a transaction code.
for Ex. below is the list of user exits for package VA ( for creation of sales order and changing sales order). Let me know which user exit is active and which is not active.
Exit name Short text
SDTRM001 Reschedule schedule lines without a new ATP check
V45A0001 Determine alternative materials for product selection
V45A0002 Predefine sold-to party in sales document
V45A0003 Collector for customer function modulpool MV45A
V45A0004 Copy packing proposal
V45E0001 Update the purchase order from the sales order
V45E0002 Data transfer in procurement elements (PRreq., assembly)
V45L0001 SD component supplier processing (customer enhancements)
V45P0001 SD customer function for cross-company code sales
V45S0001 Update sales document from configuration
V45S0003 MRP-relevance for incomplete configuration
V45S0004 Effectivity type in sales order
V45W0001 SD Service Management: Forward Contract Data to Item
V46H0001 SD Customer functions for resource-related billing
V60F0001 SD Billing plan (customer enhancement) diff. to billing plan
Thanks & Regards,
Sabu

Goto TADIR table give program id as R3TR ,Objec type as CMOD and execute.
You will get all active exits in system.
Exits related to SD may be in ZSD package.

BTE/BADI/EXIT for F110

Hi gurus,
Can you please give me the BTE / BADI / Exit for F110. Because I have to change the value for BSEG-AUFNR (Order Number) into Blank.
Thanks gurus.

Hello,
how is it that you can see the order number and i.e. i cant?
What is the configuration?
best Regards
Laurynas Prikockis

BTE or Exit for Posting

Hi Experts,
Is there any BTE or user-exit that I can be use for example if I posted document with document type DR for company code 'XX' for customer 'YY'. Another post shall be done automatically with document type 'KR' for another company code 'X2' for creditor 'YY'. In short when posting it shall generate 2 documents with different document types..
Regards,
Ekitzv
Edited by: Ekitzv on Mar 14, 2011 2:39 PM

Hi,
This may not be possible using BTE, you may have to use a custom program to get this done. In Standard system may not allow to use different document types.
Regards
K.R

How to find the user exit for the T-code 'RECN'

Hi friends,
I have a requirement as-
In 'General Data with Fast Entry' tab of tcode 'RECN' there are 2 fields as contract conclusion date and contract end date.
Now, the requirement is as if entered contract end date is less than contract conclusion date then we have to display a warning message as "contract end date cannot be less than contract conclusion date".
So, how to find the right user exit to enter the code.
Plz help me.I will surely reward points.
Thanks,
Rishi

Hi Rishi,
If User exits and BAdi's are not provided, then you will for Enhancement points.
Procedure:
When you are in a particular transaction, Go to System--> status and you find the standard program of that particular screen. Go to SE38 and give that program name, display mode.
After that you click on the spiral icon there onthe top. Then,
You go to menu bar, Edit> Enhancement opitons> show implicit enhancement options.
You will be shown the points where you need to write the code.
For creating it you will go to Edit > Enhancement opitons> Create.
By this you will add some code in the standard programs.
Reward points if it helps you.
Cheers,
Swamy Kunche

User Exits for a Trans code

Can any one help me out about how to find out the user exixts available for a particular T-code?
Kindly explain the step by step process.
Thanks ,
Priya

Use below code. Enter Transaction code and the output will be list of all the user exits associated with it.
*& Report ZUSEREXIT                                                   *
*& Finding the user-exits of a SAP transaction code                    *
*& Enter the transaction code in which you are looking for the         *
*& user-exit and it will list you the list of user-exits in the        *
*& transaction code. Also a drill down is possible which will help you *
*& to branch to SMOD.                                                  *
REPORT zuserexit NO STANDARD PAGE HEADING.
TABLES : tstc, tadir, modsapt, modact, trdir, tfdir, enlfdir.
TABLES : tstct.
DATA : jtab LIKE tadir OCCURS 0 WITH HEADER LINE.
DATA : field1(30).
DATA : v_devclass LIKE tadir-devclass.
PARAMETERS : p_tcode LIKE tstc-tcode OBLIGATORY.
SELECT SINGLE * FROM tstc WHERE tcode EQ p_tcode.
IF sy-subrc EQ 0.
SELECT SINGLE * FROM tadir WHERE pgmid = 'R3TR'
                   AND object = 'PROG'
                   AND obj_name = tstc-pgmna.
MOVE : tadir-devclass TO v_devclass.
IF sy-subrc NE 0.
    SELECT SINGLE * FROM trdir WHERE name = tstc-pgmna.
    IF trdir-subc EQ 'F'.
      SELECT SINGLE * FROM tfdir WHERE pname = tstc-pgmna.
      SELECT SINGLE * FROM enlfdir WHERE funcname = tfdir-funcname.
      SELECT SINGLE * FROM tadir WHERE pgmid = 'R3TR'
                                  AND object = 'FUGR'
                                AND obj_name EQ enlfdir-area.
      MOVE : tadir-devclass TO v_devclass.
    ENDIF.
ENDIF.
SELECT * FROM tadir INTO TABLE jtab
                WHERE pgmid = 'R3TR'
                 AND object = 'SMOD'
               AND devclass = v_devclass.
SELECT SINGLE * FROM tstct WHERE sprsl EQ sy-langu
                              AND tcode EQ p_tcode.
FORMAT COLOR COL_POSITIVE INTENSIFIED OFF.
WRITE:/(19) 'Transaction Code - ',
       20(20) p_tcode,
       45(50) tstct-ttext.
SKIP.
IF NOT jtab[] IS INITIAL.
    WRITE:/(95) sy-uline.
    FORMAT COLOR COL_HEADING INTENSIFIED ON.
    WRITE:/1 sy-vline,
           2 'Exit Name',
          21 sy-vline ,
          22 'Description',
          95 sy-vline.
    WRITE:/(95) sy-uline.
    LOOP AT jtab.
      SELECT SINGLE * FROM modsapt
             WHERE sprsl = sy-langu AND
                    name = jtab-obj_name.
      FORMAT COLOR COL_NORMAL INTENSIFIED OFF.
      WRITE:/1 sy-vline,
             2 jtab-obj_name HOTSPOT ON,
            21 sy-vline ,
            22 modsapt-modtext,
            95 sy-vline.
    ENDLOOP.
    WRITE:/(95) sy-uline.
    DESCRIBE TABLE jtab.
    SKIP.
    FORMAT COLOR COL_TOTAL INTENSIFIED ON.
    WRITE:/ 'No of Exits:' , sy-tfill.
ELSE.
    FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.
    WRITE:/(95) 'No User Exit exists'.
ENDIF.
ELSE.
FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.
WRITE:/(95) 'Transaction Code Does Not Exist'.
ENDIF.
AT LINE-SELECTION.
GET CURSOR FIELD field1.
CHECK field1(4) EQ 'JTAB'.
SET PARAMETER ID 'MON' FIELD sy-lisel+1(10).
CALL TRANSACTION 'SMOD' AND SKIP FIRST   SCREEN.
*---End of Program.
Best Regards,
Vibha
*Please mark all the helpful answers

BTE / user exit FOR F110

Hi,
My requirement is to perform certain validations before performing payment run i.e before a standard idoc is generated through f110.
Could anyone please provide some inputs on this.
Thanks

Hi ,
Check the below exits...
FEDI0002 Function exits for EDI DOCS in FI - Incoming pyt adv.no
FEDI0003 Function exits for EDI docs in FI - Save PEXR segments
FEDI0004 Function exits for EDI docs in FI - particular events
FEDI0006 Function Exits for EDI-docs in FI: Save IDCR Segments
Also go to smod > f4 and enter package as FBZ which is the development class for F110 there you would find the enhancements that might be useful.
Regards,
Himanshu

User Exit for CO11n transaction code

Dear friends,
I have a requirement that in T-Code CO11n the user enters the order confirmation and when they go for the goods movement, the screen shows the BOM list with quantities.
My requirement is that the user will put one quantity for the main material and the rest of the quantities should be calculated through the input value and appear in the respective fields.
For that I need an enhancement so please suggest me a userexit or any possible solution for the same.
Thanks in advance.
Regards,
Mubashir

Hi mubhasir,
The following are the list of available user-exits in transaction code co11n, go thru the documentation of all userexit in Tcode SMOD and choose a appropriate one for ur requirement.
Reward points, if helpful....
Regards
Karthik D
<b>Transaction Code - CO11N                    Single Screen Entry of Confirmations
Enhancement/ Business Add-in            Description
Enhancement</b>
CONFPP01-                                PP order conf.: Determine customer specific default values
CONFPP02-                                PP order conf.: Customer specific input checks 1
CONFPP03-                                PP order conf.: Cust. specific check after op. selection
CONFPP04-                                PP order conf.: Customer specific input checks 2
CONFPP05-                                PP order conf.: Customer specific enhancements when saving
CONFPP06-                                PP Order Confirmations: Actual Data Transfer
CONFPP07-                                Single Screen Entry: Inclusion of User-Defined Subscreens
CONFPS01-                                PS confirmation: Determine customer specific default values
CONFPS02-                                PS confirmation: Customer specific input checks 1
CONFPS03-                                PS confirmation: Customer specific check after op. selection
CONFPS04-                                PS confirmation: Customer specific input checks 2
CONFPS05-                                PS confirmation: Customer specific enhancements when saving
CONF0001-                                Enhancements in order confirmation
CONFPI01-                                Process order conf.: Calculate cust.specific default values
CONFPI02-                                Process order confirmation: Customer spec. input checks 1
CONFPI03-                                Process order conf.: Cust. spec. check after op. selection
CONFPI04-                                Process order conf.: Customer specific input checks 2
CONFPI05-                                Process order conf.: Cust. spec. enhancements when saving
CONFPI06-                                Process order confirmation: Actual data transfer
CONFPM01-                                PM/SM order conf.: Determine cust. specific default values
CONFPM02-                                PM/SM order confirmation: Customer specific input checks 1
CONFPM03-                                PM/SM order conf.: Cust. spec. check after op. selection
CONFPM04-                                PM/SM order conf.: Customer specific input check 2
CONFPM05-                                PM/SM order conf.: Cust. specific enhancements when saving
<b>No.of Exits:         24</b>

Exit for MIR4 transaction code

hi,
Is there any exit or Badi to populate lfsnr (number of external delevary note which we entered in Goods receipt MIRO) insted of xblnr in MIR4 (invoice document) transaction code.
regards,
revoori

Hi,
Please find the userexits available for MIR4.
Transaction Code - MIR4                     Call MIRO - Change Status
Exit Name           Description
MRMH0001            Logistics Invoice Verification: ERS procedure
MRMH0002            Logistics Invoice Verification: EDI inbound
MRMH0003            Logistics Invoice Verification: Revaluation/RAP
MRMN0001            Message output and creation: Logistics Invoice Verification
LMR1M001            User exits in Logistics Invoice Verification
LMR1M002            Account grouping for GR/IR account maintenance
LMR1M003            Number assignment in Logistics Invoice Verification
LMR1M004            Logistics Invoice Verification: item text for follow-on docs
LMR1M005            Logistics Inv. Verification: Release Parked Doc. for Posting
LMR1M006            Logistics Invoice Verification: Process XML Invoice

BTE / User exit / BADI for F-03 and F-04

Hi friends,
I have a requirement where in i have to use a bte or exit for f-03 and F-04.
help me!!.
please.

bte or exit for f-03 and F-04
What is the actual requirement ? business point of view .
It may be possible that for a validation you can use the standard functionality of GGB0.
Cheers ,
Dewang

UserExit or Customer Exit for F110 - '*' on Vendor Line Item Payment Run

Dear all,
Background
Currently in F110, when processing for vendor payments, the item text ( or segment text) is only printed out when item text begins with an asterik ' * '. The asterik is meant to indicate that this document/item is posted from external system. You may do a F1 on the text field for detail explanation.
In the event, asterik is not present on the item text even if the text is not blank, it will not be printed at all.
Here are two OSS notes on the asteriks: 312623 and 1292333.
Include: F110SFS0_SATZ_KOMPLETTIEREN
*------- Segementtext
IF REGUP-SGTXT(1) NE '*'.
    REGUP-SGTXT = SPACE.
ENDIF.
Requirement
User is requesting for item text to be printed at all time, when the text exist, regardless of ' * '.
Question
Does anyone know of a user exit / customer exit that i could use to do modification for SGTXT ?
Would appreciate it, if you could share your suggestions / experiences - on this matter, even if it doesn't need to be resolved through user exits. Thanks in advance

BTW..you have fot following exits for F110;
Transaction Code - F110                     Parameters for Automatic Payment
Enhancement/ Business Add-in            Description
Enhancement
RFFOX074                                Frame for user exit RFFOX074 (in program RFFOCH_U)
RFFOX075                                Frame for user exit RFFOX075 (in program RFFOCH_U)
RFFOX081                                Frame for user exit RFFOX081 (in program RFFOF__T)
RFFOX082                                Frame for user exit RFFOX082 (in program RFFOF__T)
RFFOX100                                Frame for user exit RFFOX100 (in program RFFOUS_T)
RFFOX101                                Frame for user exit RFFOX101 (in program RFFOUS_T)
RFFOX102                                Frame for user exit RFFOX102 (in program RFFOUS_T)
RFFOX103                                Frame for user exit RFFOX103 (in program RFFOUS_T)
RFFOX104                                user exit
RFFOX105                                Frame for user exit RFFOX105 (in program RFFOUS_T)
RFFOX200                                Frame for user exit RFFOX200 (in program RFFONZ_T)
RFFOX210                                Frame for user exit RFFOX210 (in program RFFOAU_T)
RFFOX211                                Frame for user exit RFFOX211 (in program RFFONZ_T)
RFFOX230                                General program for user exit RFFOX230 (in program RFFOJP_L)
RFFOX240                                Enhancement for User Exit 240 (RFFOAT_P)
RFFOX250                                Enhancement for User Exit 250 (RFFODK_E)
RFFOX901                                Framework for user exit RFFOX901 (in program RFFOM100)
RFFOX902                                Framework for user exit RFFOX902 (in program RFFOM100)
FDTAX001                                Enhancement to Transaction FDTA (event after the download)
FEDI0002                                Function exits for EDI DOCS in FI - Incoming pyt adv.notes
FEDI0003                                Function exits for EDI docs in FI - Save PEXR segments
FEDI0004                                Function exits for EDI docs in FI - particular events
FEDI0006                                Function Exits for EDI-docs in FI: Save IDCR Segments
RFFOX003                                Frame for user exit RFFOX003 (in program RFFOM100)
RFFOX041                                Framework for user exit RFFOX041 (in program RFFOBE_I)
RFFOX042                                Framework for user exit RFFOX042 (in program RFFOBE_E)
RFFOX043                                Framework for user exit RFFOX043 (in program RFFOBE_D)
RFFOX061                                Frame for user exit RFFOX061 (in program RFFOCH_P)
RFFOX062                                Frame for user exit RFFOX062 (in program RFFOCH_P)
RFFOX063                                Frame for user exit RFFOX063 (in program RFFOCH_P)
RFFOX064                                Frame for user exit RFFOX064 (in program RFFOCH_P)
RFFOX065                                Frame for user exit RFFOX065 (in program RFFOCH_P)
RFFOX066                                Frame for user exit RFFOX066 (in program RFFOCH_P)
RFFOX071                                Frame for user exit RFFOX071 (in program RFFOCH_U)
RFFOX072                                Frame for user exit RFFOX072 (in program RFFOCH_U)
RFFOX073                                Frame for user exit RFFOX073 (in program RFFOCH_U)
Business Add-in
FI_BSTM_MC_EXIT                         FI Account Statement: Exit from MultiCash Conversion
FI_F110_SCHEDULE_JOB                    F110: Check before scheduling a proposal/update run

Exit for ME21N

Hi,
Need your help for solving an issue related to ME21N ( Purchase Order Creation)
I am having ZVRL(say) condition type that is mandatory and is defined in pricing schema ZVVA01(say).ZVVA01 is further attached to purchase organisation 4000 (say).
I am having a document type ZVVN . I want to save the purchase order without ZVRL (Defined as Mandatory condition) for particular document type ZVVN. But as ZVRL is mandatory condition , So system does not allow me to save the purchase order.
For solution following option have been ruled out by the client-
1) Through a separate vendor schema with different purchase organization.
2) Entering any value like .01 or .002 for the mandatory condition type that is for ZVRL.
Other than above two, Can anyone please tell me if there is any exit/badi/ or pricing routine available through which we can avoid mandatory ZVRL condtion for particular document type ZVVN at the time of saving and changing the Purchase order.
Thanks
Deepak Gupta

Hi,
Check all user exit for ME21N
Transaction Code - ME21N Create Purchase Order
Exit Name Description
LMEDR001 Enhancements to print program
LMELA002 Adopt batch no. from shipping notification when posting a GR
LMELA010 Inbound shipping notification: Transfer item data from IDOC
LMEQR001 User exit for source determination
LMEXF001 Conditions in Purchasing Documents Without Invoice Receipt
LWSUS001 Customer-Specific Source Determination in Retail
M06B0001 Role determination for purchase requisition release
M06B0002 Changes to comm. structure for purchase requisition release
M06B0003 Number range and document number
M06B0004 Number range and document number
M06B0005 Changes to comm. structure for overall release of requisn.
M06E0004 Changes to communication structure for release purch. doc.
M06E0005 Role determination for release of purchasing documents
ME590001 Grouping of requsitions for PO split in ME59
MEETA001 Define schedule line type (backlog, immed. req., preview)
MEFLD004 Determine earliest delivery date f. check w. GR (only PO)
MELAB001 Gen. forecast delivery schedules: Transfer schedule implem.
MEQUERY1 Enhancement to Document Overview ME21N/ME51N
MEVME001 WE default quantity calc. and over/ underdelivery tolerance
MM06E001 User exits for EDI inbound and outbound purchasing documents
MM06E003 Number range and document number
MM06E004 Control import data screens in purchase order
MM06E005 Customer fields in purchasing document
MM06E007 Change document for requisitions upon conversion into PO
MM06E008 Monitoring of contr. target value in case of release orders
MM06E009 Relevant texts for "Texts exist" indicator
MM06E010 Field selection for vendor address
MMAL0001 ALE source list distribution: Outbound processing
MMAL0002 ALE source list distribution: Inbound processing
MMAL0003 ALE purcasing info record distribution: Outbound processing
MMAL0004 ALE purchasing info record distribution: Inbound processin
MMDA0001 Default delivery addresses
MMFAB001 User exit for generation of release order
MRFLB001 Control Items for Contract Release Order
AMPL0001 User subscreen for additional data on AMPL
See which is suitable for your requirement.

How to created exit for CS02 transaction to maintain bom details of a mater

hi ,
     plz explain how to created exit for CS02 transaction to maintain BOM details of a material. what is the BOM component . give me sample example.

Hi,
these are the user-exits for CS02
Transaction Code - CS02                     Change Material BOM
Exit Name           Description
PCSD0001            Applications development R/3 BOMS
PCSD0002            BOMs: Customer fields in item
PCSD0003            BOMs: Customer fields in header
PCSD0004            BOM comparison
PCSD0005            BOMs: component check for material items
PCSD0006            Mass changes user exit
PCSD0007            Check changes in STKO
PCSD0008            WBS BOM: Customer-specific explosion for creating
PCSD0009            Order/WBS BOM, determine URL page
PCSD0010            Order/WBS BOM, determine explosion date
PCSD0011            Knowledge-based order BOM, parallel update
PCSD0012            Customer - Mat. number/mat. number during material exchange
PCSD0013            Customer-specific processing of an explosion for BOM browser
Regards
Nilesh

Screen exit for me32k for header and for items

hi experts,
i need a screen exit from me32k to add subscreen in :
1. items
2. header
thanks in advanced,
dana.

Hi,
Just some information on screen exits:
Screen Exit:
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 themsave. Then, enter into the tcodes again to see whether the values entered by you are being displayed or not.
Original Source: ittoolbox.com
User 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 if found helpfull,
Cheers,
Chaitanya.

BTE or EXIT for MR01 t code

Similar Messages

Maybe you are looking for