BADI/User Exit/BTE for updating Bar code in FI Invoice posting

Hi,
We have a requirement to update the bar code value in the table BDS_BAR_IN, once the FI invoice is generated. This is an inbound. I tried, but didn't find any user exit/BADI/BTE to do the same.
Basically, I need to get any of these enhancement points where I can update bar code with the generated FI document number.
Would appreciate your help.
Thanks
Itishree.

Hi,
Pls check if any of the following is good for ur scenario;
BBPIV001  User Exits EBP Invoice Verification
EBIA0019  IS-U: Customer-Specific Invoice Comparison
IDCP0001  Customer Data for Printing Prenumbered Invoices
J_1ASD06  User-exit invoice reference in billing document (SD)
LMEXF001  Conditions in Purchasing Documents Without Invoice Receipt
LMR1M001  User exits in Logistics Invoice Verification
LMR1M003  Number assignment in Logistics Invoice Verification
LMR1M004  Logistics Invoice Verification: item text for follow-on docs
LMR1M006  Logistics Invoice Verification: Process XML Invoice
MCBR0001  INVCO: Statistics update from invoice verification, valuatn
MCP20009  Extrapolation of Invoiced Sales for OTB
MCS60001  SIS: Statistics update, invoices
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
NBILL003  IS-H: Case-Related Invoice Processing
NEBILL00  IS-H: Function Exits for Estimated Invoice
NPRI0001  IS-H: User exits for invoice printout
NPRISG01  IS-H: Function Exits for Invoice Print SG
OICM0001  Exit for IS-Oil Repricing at Invoice Verification
PCA00004  Check valuation for invoice verification with transfer price
PCA00005  Check valuation for invoice verification with transfer price
V54C0004  Shipment Costs Processing: Determine Loc. for Tax Invoice
BADIs
/CWM/DEFAULT_VAL_IV             BAdI for Default Logic in Invoice Verification
/DSD/SL_FSR_INV_PROC            DSD Final Settlement Run: Processing Invoice Data
/SAPDII/SPP_INV_XML             XML file download for invoice details
/SPE/CRM_SUPPL_IV               Supplier Invoice
BADI_INV_PRTDATA                Customer Exit for Data Procurement for Invoice Printing
FI_GET_INV_PYMT_AMT             BAdI for determining the payment amount for an invoice
FMFG_IMPROPER_PANEL             Additional Processing of Improper Invoice Panel
ICL_INVOICE                     BAdI: Changes to Invoices or Collective Invoices
INVOIC_FI_INBOUND               BADIs for Inbound IDoc INVOIC FI (Vendor Invoice)
INVOICE_UPDATE                  Business Add-In: Logistics Invoice Verification
ISH_DOP_DEDUCTION               IS-H: Deduct Down Payment From Invoice
ISH_FILL_RNF49                  IS-H: Fill Form Structure RNF49 (Cllct. Invoice Cnc. Doc.)
ISH_FILL_RNFP2S                 IS-H: Fill Form Structure RNFP2SE (Collective Invoice Items)
ISH_INV_CANCEL_CHK_1            IS-H: Check Whether Invoice Can Be Canceled
ISH_INVOICE_CHECK               IS-H: Check Invoice Creation
ISH_PRINT_INVOICE               IS-H: Invoice Print
ISJP_ITEM                       Invoice Summary Items
MB_CIN_MM07MFB7_QTY             Proposal of quantity from Excise invoice in GR
ME_CIN_LEINRF2V                 BADI for LEINRF03 excise_invoice_details
MR_CIN_MM08RFS0                 BAdI for carrying excise duty to carry invoice verfication
MRM_RELEASE_CHECK               BAdI for Additional Checks Before Invoices are Released
OIA_ERS_ENHANCEMENT             Invoice split possibility
SS01_BADI                       Payment Statistical Sampling BAdI - Invoice Batching
VLC_INIV_EXECUTE                Execute Action INIV (Create Incoming Invoice)
VLC_OUIV_EXECUTE                Execute Action OUIV (Create Outgoing Invoice)
WB2_ALV_IV                      Change ALV Data from Invoice Verification Documents
WB2_SALES_INV_INPUT             BADI to modify input data for sales invoice
WB2_SALES_INV_OUTPUT            BADI to get data from created sales invoice
WOSCR_EXI                       SAP Retail Store: Vendor Invoice
Regards,
Renjith Michael.

Similar Messages

  • BADI-User exit required for updating Purchase order header field -IHREZ

    Hello All,
    We have requirement in our business to update the purchase order header field "our reference" EKKO-IHREZ with some text field. We need a BADI/user exit that can be used for updating this field . We have checked the BADI ME_PROCESS_PO_CUST and unfortunately we are not able to use this BADI as it getting triggered in enjoy SAP transactions ME21N , ME22N etc. We are not creating the purchase order manually and we are using ME59N for creating Purchase order . Hence we are looking for some user exit/BADI that can be used in ME59N for updating the purchase order header field IHREZ.
    Thanks in advance for your immediate response .
    With regards,
    Joseph Anand B

    TRY using the exist u2022     EXIT_SAPLME59_001
    You can also later on add this field by BAPI_PO_CHANGE

  • BADI/User Exit suggestion - for determining Partner in PO header

    Hi All,
    I want to be able to automatically populate and determine a manual partner function within the header of a purchase order creation.
    Example, when PO is allocated against account assignment 'P' then go to the WBS element assigned and retrieve the specific partner number for partner function type XX. Then populate this into the relevant header partner function of the PO.
    Any ideas of which BADI/User exit could be used in ME21N?
    Thanks
    Steve

    Hi Steve
    Before going to search the UserExit/BADI, please remember your account assignment will be at item level and the partner will be at Header level.If you have number of line items with different account asssginments or different WBS elements under account assignment P, it is difficult to determine the partner functional at Header level.Please think on how can you build logic? There are number of BADI/Exits available for Purchase order.
    Regards
    Ramakrishna

  • BADI/User-Exit Required for VL01N (Only PGI)

    Dear All,
    I need a BADI or User-Exit which will be triggered in VL01N only during PGI just before the material document gets created (after all validations are done).
    Thanks in Advance
    Santosh

    HI Santosh,
    Why do you want to Enhance just before the Material document creation. ?
    Why Cannot you do all your validations in USEREXIT_SAVE_DOCUMENT_PREPARE. so that this data is passed when MM document is created?
    any way The PGI push button, uses the FM MB_CREATE_GOODS_ISSUE_ITEM internall.This FM has some space provided for the Customer enhancements ( EXIT_SAPLMBWL_400)  iNCLUDE name is ( LXOIAU07) . I have not used this exit. So figure out if this can help you..
    But Try to analyze why do we need to modify just before MM document creation. if you can tell the problem thats forcing you, then some one in the forum has a solution for it...
    Thanks,

  • User Exit/BTE for F-26  for sequencing clearing open items

    Hi All,
    Is there a BTE/User exit to identify the items selected for clearing in F-26? ( On line item double click)
    Based on the open items displayed we need to enforce a check that they are selected in a proper sequence.
    Thanks in advance,
    Puneet

    Thanks for the reply.
    I succeded creating the validation with an user-exit. I made the following steps:
    1) I created the validation in GGB0 (for document header), issuing a standard message (420 "Exchange rate not found") from message class (ZRSAU) - which is a copy of RSAU message class (in the beggining I put no pre-requisites, checks or rules, just the message).
    2) In OB28 I attached the validation (with call point document header) and I made it active (without batch input).
    3) I copied the RGGBR000 program (which is standard program with an example of validation) into ZRGGBR00 (it should be maximum 8 characters).
    Then I changed the ZRGGBR00 program (form U100) comparing the translation date (from BKPF) with the date from table TCURR (and exchange rate type M, and documents currency other than local currency).
    If the program doesn't find any exchange rate in TCURR in that date, it issues the error message (assigned in GGB0).
    4) In GGB0, I put the U100 user exit as a check and rule
    5)  In GCX2, I attached the ZRGGBR00 program to the GBLR application area (which is for user exits for validations / rules).
    Now it's working fine!

  • BADI / USER-EXITS available for Txn. QE01

    Hi Experts,
    Could anyone please suggest appropriate BADIu2019s and user-exists available for Txn. QE01 to send the status change.
    Our requirement is to send a mail notification to the user when all the result recording status of the inspection characteristics turn to 'complete'
    In Tx QE01 the inspection results are recorded for each inspection characteristics.When results recorded for all the characteristics the user will close the insp. characteristic and the status will change to 'complete' then needs a mail notification so that user decision (UD) can be performed for the inspection lot.UD (Txn QA11) will be performing after result recording.
    Any suggestion will be appreciated.
    Thanx and Regards

    Hi ,
    Please check below BADI and User exits .
    Bus. add-in name     Description
    QE_RESULT_VALUATION   "Valuation of Single Values
    QE_SAVE              "Save Results
    QEEM_SUBSCREEN_5000   "EE: BAdI Subscreen for Display of Data on Screen 5000
    QM_IDI_INSPPOINT     "Changing of Inspection Point Processing in IDI and BAPIs
    QM_INPUT_PROCEDURE   "Input Processing
    Exit name     Description
    QEEM0003     "User exit: add. functions after valuating insp. characs
    QEEM0004     "User exit: add. functions after valuation of partial samples
    QEEM0006     "User exit: add. functions after closing inspection characs
    QEEM0007     "User exit: add. functions after completing partial samples
    QEEM0011     "User exit: add. functions before valuating insp. characs
    QEEM0012     "User exit: add. functions before valuating partial samples
    QEEM0015     "User exit: add. functions after entering individual results
    QEEM0020     "User exit: additional functions after entering the inspector
    QEEM0021     "User exit: additional functions for user key +US1
    QEEM0022     "User exit: additional functions for user key +US2
    QEEM0023     "User exit: additional functions for user key +US3
    QEEM0024     "User exit: additional functions for user key +US4
    QEEM0029     "User-Exit for Characteristic Overview Subscreen
    QEEM0030     "User-Exit for Subscreen: Characteristic Single Screen
    QEEM0031     "User-Exit for Table Structure with External Numbers
    QEEM0032     "Presentation of the characteristic text in the logon lang.
    QEEV0003     "Determination of order type for print
    QIST0002     "Generating MATERIAL_DATA for QM STI Interface
    QIST0003     "Generating VENDOR_DATA for QM STI Interface
    QIST0004     "Generating CHARACTERISTIC_HEADER for QM STI Interface
    QIST0005     "Generating CHARACTERISTIC_QUANTITATIVE for QM STI
    QIST0007     "Generating SAMPLE_HEADER for QM STI Interface
    QIST0008     "Generating RESULTS_ADDITIONAL_DATA for QM STI
    QIST0009     "Generating RESULTS_QUANTITATIVE for QM STI Interface
    QIST0010     "Generating REPORT_HEADER for QM STI Interface
    QIST0011     "Generating METHOD_DATA for QM STI Interface

  • USER EXIT PA for change material code

    Hi,
    I am looking for an user-exit for PA. In some cases, when we create a Post Document we need to change the material code, only in PA, not in FI.
    I have been looking for an user-exit to solve this question, but I find nothing. Do you know an user exit?
    To implement an usert exit for PA, is it necessary always to use tx KEDR?
    Thanku2019s in advance.
    Regards.

    Hi;
    For implementation of User Exit in COPA you need to use KEDR.
    My understanding of your Requirement is old Material No Raplacement to New Replacement..
    my assumption of your  scenario you  will create new Table and maintain Old No Against New Material No; from this table  user Exit  call  new material and substituting old No or do you have any other ideas on your requirement?
    try one more way
    Derivation Rule 1.
    use clear Option and Remove Old Material No in COPA documents.
    Derivation Rule 2
    Use Derivation Rule Option and make Condtions like old No = New material No.
    Regards
    satish

  • Badi/User-exit for vendor down payment request in f-47

    hi all,
    is there any badi/user-exit available for vendor down payment request?
    I need to trigger a workflow when a vendor down payment request in transaction code F-47.
    how can i do this?
    Pls guide me.
    Thanks & regards,
    Raj

    Did it using a business transaction event

  • Exit and BTE for MIRO T.code

    Hi Guru,
    My requirment is like that when i am doing MIRO with reference to PO no. . In Detail Tab in MIRO default Inv. Party -  (100077)is comming  with reference to PO - Partner  - Invoicing party Number.
    But Here in this MIRO - Detail Tab - Field Name - Inv. Party - I want only - Vendor Number with reference to PO - Partner - Vendor Number (100000).
    Kindly any one  suggest regarding Any BADI, User-Exit, BTE regarding this issue.
    Regards
    Rama

    Create the field exit on field BKLAS.
    and write the below code in the field exit.
    DATA: i_dynpread TYPE STANDARD TABLE OF dynpread WITH HEADER LINE.
    DATA: V_MATKL TYPE ASMD-MATKL
    V_BKLAS TYPE ASMD-BKLAS.
    i_dynpread-FIELDNAME = 'ASMD-MATKL'.
    append i_dynpread.
    clear: i_dynpread.
    CALL FUNCTION 'DYNP_VALUES_READ'
    EXPORTING
    DYNAME = 'SAPLBAS0'
    DYNUMB = '0300'
    TABLES
    DYNPFIELDS = i_dynpread.
    IF SY-SUBRC = 0.
    loop at i_dynpread.
    SELECT SINGLE BKLAS
    FROM ASMD
    INTO V_BKLAS
    WHERE MATKL = i_dynpread-fieldvalue.
    IF SY-SUBRC = 0.
    output = v_hkont.
    ELSE.
    error message.
    ENDIF.
    endloop.
    ENDIF.
    Regards

  • MIRO Validation BADI / USER EXIT

    Hi All,
    Need a line item level validation for invoice amount validation with PO line item.
    Please suggest me BADI / USER Exit name for same.
    Thanks,

    Use this exit.
    LMR1M001.

  • User Exit or BADI for Updating Tax code (MWSKZ) using ME21N

    Hi all,
    I am trying to fin out an exit or badi for Updating Tax code (MWSKZ) and Unit of Measure in transaction ME21n.
    The scenario is like this...
    For Purchase Orders Tax code will be defaulted from Purchasing info record or contract or parameter id for that item-vendor-plant.
    If the Tax Code is not defaulted and account assignment is blank then tax code on the PO is updated according to the below mentioned table
    Table
    Supplying Plant/              Receiving Plant                      Tax code
    Vendor/Country
    Any plant/vendor/
    country                           5050(NA)                               20
    2300                              6700                                     E0
    If the tax code on PO cannot be updated by the above table, then buyer needs to put tax code on the purchase order manually.
    Thanks,
    Shiva, Bangalore

    Hi Siva.,.,.,
    These r the exits.,..,which will be called while calling ME21N/ME22N/ME23N
    EXIT_SAPMM06E_006
    EXIT_SAPMM06E_007
    EXIT_SAPMM06E_008
    EXIT_SAPMM06E_009
    EXIT_SAPMM06E_012
    EXIT_SAPMM06E_013
    EXIT_SAPMM06E_014
    EXIT_SAPMM06E_016
    EXIT_SAPMM06E_017
    EXIT_SAPMM06E_018
    U want to default some values while the Initial screen will come right,
    while u Enter ME21N in command Prompt.,.,two exits will get triggerd,
    EXIT_SAPMM06E_014
    EXIT_SAPMM06E_016
    If u want to Default some values u can use these two exits.,.
    Try using EXIT_SAPMM06E_016.,.this will solve ur purpose.
    and if the user changes some values on screen.,,and you want them to get reflected .,.,.that means if user changes and saves data .,.
    While saving.,.,EXIT_SAPMM06E_012 and EXIT_SAPMM06E_013 will get triggerd
    Try using EXIT_SAPMM06E_013.,,.it was somehow the same requirement as mine.,.,IN my case it worked fine.,.,
    Regards
    Debasish
    Message was edited by:
            Debasish Das

  • BADI/user exit for transcation code "BP" in CRM

    Hi Experts,
    Is there a BADI / user exit that is triggered after successful saving/updating of Business Partner using transaction code "BP"?
    We want to send general infos such as partner number, Name, Birth date, etc. about the business partner being created/updated using IDoc.
    We are using CRM WinClient 4.0.
    If you know  the steps on how this requirement will be done, kindly post them.
    Thank you very much.

    I don't have any CRM system at hand, but I'm sure there are some BAdI's for this. Look in SE18 for BP or BUS, and i'm sure  you will find something.
    One suggestion though: Before going for the BadI, try and see if CRM also uses change pointers for sending Idoc's . This case you wont need any user exits / badis, an probably no programming at all.
    Transaction
    BD50: Activate Change Ptrs for Mess. Type
    BD61: Activate Change Pointers - Generally
    and use report RBDMIDOC for triggering IDoc.

  • BADI/User Exit for custom table update from Delivery

    Hi
    Our requirement is to update a custom table with the delivery number and other related details when the picking status is changed to "C". Kindly suggest BADI/User exit for this requirement .
    Thanks in Advance for your immediate help .

    Hi Joseph,
    See SAP Note 415716 - User exits in delivery processing. It says when you have the document number available, what is permitted, what not, ....
    I hope this helps you
    Regards
    Eduardo

  • Badi & User Exit for ME21N & ME22N

    Hi,
            My requirement is when a Purchase order is created using ME21n or when a line is added or changed using ME22n, the system should copy the vendors tax jurisdiction to the purchase order line items jurisdiction code. I tried badi (ME_PROCESS_PO_CUST) but could not suceed. Can any one tell me if any badi or user exit available for the same???
    Thanks in Advance.

    hi,
    Enhancement/ Business Add-in            Description
    Enhancement
    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 processing
    MMDA0001                                Default delivery addresses
    MMFAB001                                User exit for generation of release order
    MRFLB001                                Control Items for Contract Release Order
    MELAB001                                Gen. forecast delivery schedules: Transfer schedule implem.
    AMPL0001                                User subscreen for additional data on AMPL
    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
    MEFLD004                                Determine earliest delivery date f. check w. GR (only PO)
    MEETA001                                Define schedule line type (backlog, immed. req., preview)
    ME590001                                Grouping of requsitions for PO split in ME59
    M06E0005                                Role determination for release of purchasing documents
    M06E0004                                Changes to communication structure for release purch. doc.
    M06B0005                                Changes to comm. structure for overall release of requisn.
    M06B0004                                Number range and document number
    M06B0003                                Number range and document number
    Business Add-in
    ME_PROCESS_PO                           Enhancements for Processing Enjoy Purchase Order: Intern.
    ME_PROCESS_COMP                         Processing of Component Default Data at Time of GR: Customer
    ME_PO_SC_SRV                            BAdI: Service Tab Page for Subcontracting
    ME_PO_PRICING_CUST                      Enhancements to Price Determination: Customer
    ME_PO_PRICING                           Enhancements to Price Determination: Internal
    ME_INFOREC_SEND                         Capture/Send Purchase Info Record Changes - Internal Use
    ME_HOLD_PO                              Hold Enjoy Purchase Orders: Activation/Deactivation
    ME_GUI_PO_CUST                          Customer's Own Screens in Enjoy Purchase Order
    ME_FIELDSTATUS_STOCK                    FM Account Assignment Behavior for Stock PR/PO
    ME_DP_CLEARING                          Clearing (Offsetting) of Down Payments and Payment Requests
    ME_DEFINE_CALCTYPE                      Control of Pricing Type: Additional Fields
    ME_COMMTMNT_REQ_RE_C                    Check of Commitment Relevance of Purchase Requisitions
    ME_COMMTMNT_REQ_RELE                    Check of Commitment Relevance of Purchase Requisitions
    ME_PROCESS_PO_CUST                      Enhancements for Processing Enjoy Purchase Order: Customer
    SMOD_MRFLB001                           Control Items for Contract Release Order
    MM_EDI_DESADV_IN                        Supplementation of Delivery Interface from Purchase Order
    MM_DELIVERY_ADDR_SAP                    Determination of Delivery Address
    ME_WRF_STD_DNG                          PO Controlling Reminder: Extension to Standard Reminder
    ME_TRIGGER_ATP                          Triggers New ATP for Changes in EKKO, EKPO, EKPV
    ME_TRF_RULE_CUST_OFF                    BADI for Deactivation of Field T161V-REVFE
    ME_TAX_FROM_ADDRESS                     Tax jurisdiction code taken from address
    ME_REQ_POSTED                           Purchase Requisition Posted
    ME_REQ_OI_EXT                           Commitment Update in the Case of External Requisitions
    ME_RELEASE_CREATE                       BAdI: Release Creation for Sched.Agrmts with Release Docu.
    ME_PURCHDOC_POSTED                      Purchasing Document Posted
    ME_PROCESS_REQ_CUST                     Enhancements for Processing Enjoy PReqs: Customer
    ME_PROCESS_REQ                          Enhancements for Processing Enjoy PReqs: Internal
    ME_COMMTMNT_PO_REL_C                    Check for Commitment-Relevance of Purchase Orders
    ME_CCP_BESWK_AUTH_CH                    BAdI for authorization checks for procuring plant
    ME_CCP_ACTIVE_CHECK                     BAdI to check whether CCP process is active
    ME_BSART_DET                            Change document type for automatically generated POs
    ME_BAPI_PR_CREATE_02
    ME_BAPI_PR_CREATE_01
    ME_BAPI_PO_CREATE_02
    ME_BAPI_PO_CREATE_01
    ME_BADI_DISPLAY_DOC                     BAdI for Internal Control of Transaction to be Invoked
    ME_ACTV_CANCEL_PO                       BAdI for Activating the Cancel Function at Header Level
    MEGUI_LAYOUT                            BAdI for Enjoy Purchasing GUI
    EXTENSION_US_TAXES                      Extended Tax Calculation with Additional Data
    ARC_MM_EKKO_WRITE                       BAdI: Enhancement of Scope of Archiving (MM_EKKO)
    ARC_MM_EKKO_CHECK                       BAdI: Enhancement of Archivability Check (MM_EKKO)
    ME_CCP_DEL_DURATION                     Calc. of Delivery Duration in CCP Process (Not in Standard)
    ME_COMMTMNT_PO_RELEV                    Check for Commitment-Relevance of Purchase Orders
    ME_COMMITMENT_STO_CH                    BadI for checking if commitments for STOs are active
    ME_COMMITMENT_RETURN                    Commitment for return item
    ME_CIP_REF_CHAR                         Enables Reference Characteristics in Purchasing
    ME_CIP_ALLOW_CHANGE                     Configuration in Purchasing: Changeability Control
    ME_CIN_MM06EFKO                         Copy PO data for use by Country version India
    ME_CIN_LEINRF2V                         BADI for LEINRF03 excise_invoice_details
    ME_CIN_LEINRF2R                         BADI for CIN India - Delivery charges
    ME_CHECK_SOURCES                        Additional Checks in Source Determination/Checking
    ME_CHECK_OA                             Check BAdI for Contracts
    ME_CHECK_ALL_ITEMS                      Run Through Items Again in the Event of Changes in EKKO
    ME_CHANGE_OUTTAB                        Enrich ALV Output Table in Purchasing
    ME_CHANGE_CHARACTER                     Customer-Specific Characteristics for Product Allocation
    No.of Exits:         35
    No.of BADis:         55
    Arunima

  • BADI/User-Exit for MD14

    Hi,
    Our client wants to update certain data in PR while the PRs are created from Planned orders or after a PR is created from a Planned order.
    I've implemented BADI MD_PURREQ_CHANGE but while testing, the debugger is not taking to the break point.
    Thus it appears that this BADI is not applicable for MD14.
    I need a BADI/User exit where I can change the material description in PR.
    Please help.Helpful answers shall be rewarded.

    Hi abhijit,
    Check this program.You will get all exits for a transaction.
    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.

Maybe you are looking for