BADI/User Exit to capture DELETED DATE - MIRO/MIR7

Hi Friends,
Could anybody help me out in finding a BADI or User Exit (or some other means) so as to get the actual deleted date for the documents parked through MIRO/MIR7 ?
(I have found a BTE to capture the deleted date for the documents parked through FB60/FV60.)
Thanks in advance.
Regards,
Saravanan SR

Hi Uday,
User exits are:
EXIT_SAPLMR1M_001 - MM08R002 - User exit for tolerance checks
EXIT_SAPLMR1M_002 - LMR1M001  - User exits in Logistics Invoice Verification
EXIT_SAPLMR1M_003 - LMR1M001  - User exits in Logistics Invoice Verification
BADI's are:
BADI_ENJ_ALT_ADR - Go to alternative vendor/customer data
MR_CIN_LMR1MI2G_SEL - BAdi in LIV for determining line selection
MR_CIN_LMR1MI2G - BAdI for India Version exit in include LMR1MI2G
Regards,
Sukhbold

Similar Messages

  • BADI USER/EXIT for inserting cust. data after the Pruch. Requsitio is SAVED

    Hi all,
    Is there any  BADI or USER EXIT available for the transaction ME51N to save
    some customer data fields in a separta Z table , after the data is saved from the
    Purcahse requistion .
    I  have used the customer exit MEREQ001 for additing the customer filelds with TABLE CONTROL.
    I am not able to save the data from the table control . Any suggestion on this will be apprecitated  .
    Best Regards

    Hi,
      You have  to use 'EXIT_SAPLMEREQ_003' to import data from screen to your tables and use 'EXIT_SAPLMEREQ_001' to send data to screen.use the below code like below:
    EXIT_SAPLMEREQ_001:
    tables : ci_ebandb.
    data : i_mereq_item type mereq_item.
    if im_req_item is initial.
    clear: ci_ebandb.
    else.
    i_mereq_item = im_req_item->get_data( ).
    move-corresponding i_mereq_item to ci_ebandb.
    endif.
    EXIT_SAPLMEREQ_003
    data : i_mereq_item type mereq_item.
    if not im_req_item is initial.
    i_mereq_item = im_req_item->get_data( ).
    move-corresponding ci_ebandb to i_mereq_item .
    call method im_req_item->set_data( i_mereq_item ).
    endif.
    Also set the flag EX_CHANGED = 'X' to transafer the changes to database
    Regards,
    Himanshu

  • Badi/ User Exit - to update item data on Post GR in MIGO

    Guyz,
    I have a requirement to update the value in ALAN1 , ALAN2 fields while posting GR in MIGO. And also I need to access the value of realted PO (ebeln) and line item(ebelp) and equipment number(or serial number) EQUNR filed ,while doing the coding for this enhanemnet.
    I was looking for Badi or User exit to meet the need. I have found a Badi MB_MIGO_ITEM_BADI, which I have implemented. I have put a break in the method and found that I can access all the value in the above mentioned field (IS_GOITEM, is the sturcture in the Badi signature) but one problem still persists.
    I can see only the last line item(ebelp), in IS_GOITEM, where I need to see all the line item, so that I can relate which Equnr is assigned to which Lineitem.
    Please tell me if you know any badi or user exit for this purpose.
    Regd,
    Anid 
    Points Guranteed
    Message was edited by:
            Anid

    Hi,
    we have checked above BADI;s but will not suffice the requirement;
    The requiement is
    While Creating PO(ME21N) and Changing PO(ME22N):
    When the user tries to Save the PO:
    All the line items should be accessible and can be editable.
    If the validation fails, error message should be displayed on
    the screen and user should be able to edit at that location.
    Please let me know if there is any other way or enhancement point for the same...
    Regards
    Shiva

  • BADI / user exit for Tcode IW32?

    Hi
    Are there any BADIs  / user exits for changing component data in Transaction IW32 for a maintainance order?
    regards
    cs

    Enhancement                                                                               
    IWO10012                                Maintenance order: Priority handling on central header                                                                               
    Business Add-in                                                                               
    IWO_UI_USEFLEX                          BAdI for Calling Up an Alternative UI                  
    I hope it helps.
    Best Regards,
    Vibha
    Please mark all the helpful answers

  • BADI/USER EXIT for MIRO.

    Hi All
    I have added a new field (GST) on MIRO screen using GUI XT.
    The requirement is such that I need to populate this field after I have entered the purchase order no (It needs to take the vendor from the PO and then its subsequent VAT no from the vendor master). I am not sure where to do this part of the coding.
    i have tried to implement BADIs
    BADI_ENJ_ALT_ADR
    INVOICE_UPDATE
    BADI_FDCB_SUBBAS01
    but it doesn't help.
    Is there any other BADI/User Exit that I can try.
    Thanks in advance.
    Harsh

    Hi,
    Bellow are the exit names for MIRO.
    <Irrelevant enhancement list removed by moderator>
    Regards,
    Goutam Kolluru.
    Edited by: Vinod Kumar on Feb 3, 2012 9:34 AM

  • 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.

  • BADI/User Exit for KO02

    Dear Experts,
    When I'm setting the BUDGETED status manually to Internal Order (With out distributing the Budget to Order in IM52) and after if I m setting RELEASE status the system is accepting. So, I want to stop this without giving the budget in IO, it should not accept to release IO.
    This is not possible with User Status, coz' User may go and set manually "REL" Status.
    can anyone suggest me the BAdi/User Exit for KO02(Internal Order Change) tcode.
    Thanks,
    Sanju.

    When you set a User status , you can assign an Authorization Object on who can change the status .
    Follow the path in SPRO--> Controlling --> Internal orders --> Order Master Data > Status Management> Define authorization Keys for Status Management
    Define Authorization Keys for Status Management
    In this step you define authorization keys which you can use to set up authorization checks when you manually set or delete a user status. When the system sets a user status as a reaction to business transaction, it does not perform an authorization check.
    When you set or delete a user status, the system checks whether the user is authorized for this action. In addition to the status profile and the object type, the system also checks the authorization key assigned to the user status in question.
    Example
    You want to define that certain user statuses can be changed only by a specified employee group.
    To do this, create an authorization key and assign it to the relevant user statuses.
    In the general authorization maintenance you can then assign authorizations for this key via the authorization object B_USERSTAT.
    Activities
    1. Check whether you want to define authorizations for your user statuses.
    2. If necessary, create authorization keys as follows:
    a) Choose "New entries".
    b) Enter a key and an explanatory text in the appropriate fields and choose "Save".
    You have now created the authorization key.
    3. Assign the authorization key to one or more user statuses in your status profile.
    4. Define corresponding authorizations and include them in the relevant authorization profiles.

  • Badi/user exit in tcodes me54n,me55,me28 and me29n

    hi all,
    1.which is the badi/user exits that is there in me54n and me55...for saving and releasing purchase requisation(s) .
    2.which is the badi/user exits that is there in me28 and me29n...for saving and releasing purchase order(s) .
    points will be rewarded.
    regards,
    johnson

    Transaction Code - ME54N                    Release Purchase Requisition                                                                               
    Enhancement                                                                               
    MEREQ001                                Customers' Own Data in Purchase Requisition                                                                               
    Business Add-in                                                                               
    ME_COMMITMNT_PARKING                    BAdI for Redefining Commitment Interface When Parking   
    ME_MEREQ_PARKING                        BAdI Purchase Requisition: "Hold"                       
    ME_REQ_HEADER_TEXT                      Copy Header Text: Enjoy Purchase Requisition
    Transaction Code - ME55                     Collective Release of Purchase Reqs.
    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. 
    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_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

  • 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 before FI document is posted during GR posting in MIGO

    Hi Gurus,
    In transaction MIGO, whenever a goods receipt is posted, a corresponding FI document is then created. I am in need of a BADI, User Exit, or other forms of enhancements that is triggered before this FI document gets posted because I have to edit data in the header (BKPF) and detail (BSEG) part, specifically the fields BKPF-XREF1_HD (Reference key 1) and (BSEG-ZUONR) (Assignment).
    The field XREF1_HD is to be populated with the vendor number from MIGO (GOHEAD-LIFNR)
    The field ZUONR is to be populated with the PO Number from MIGO (GOITEM-EBELN)
    Regards to all,
    Joseph

    Hi,
    I am on 4.6C.
    We are using EXIT_SAPLF048_001 of enhancement F180A001 for the same.
    Please note that control comes here for no of SAP transactions, hence you need to take care of it by executing your logic only for a particular SAP transaction.
    I hope this helps,
    Regards
    Raju Chitale

  • 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.

  • BADI/User Exit for KE51 and KE52

    Hi Experts,
    I am searchinf for a BADI/User exit In profit center master transactions KE51 and KE52 which should trigger  when we activate the Profit center and after the data base committed as i need to send the changed profit center data to other system. 
    any ideas will be highly appreciated.
    Thanks,
    Rajinikanth

    Try
    PCA00003  Derive Partner Profit Center for External Deliveries
    EXIT_SAPLPC45_002
    EC-PCA: Activate Derivation of Partner Profit Center

  • BADI/ User Exit for transaction FTR_EDIT/FTR_CREATE initial screen

    Hi All,
    I want a BADI/User Exit for FTR_EDIT/FTR_CREATE transactions to validate company code and partner fields.
    please provide your suggestions.

    Hi,
    here is a coding example that I implemented in the BAdI FTR_TR_GENERIC. This coding is executed when the user press the check button. The method is EVT_TRANSACTION_CHECK. This example is checking the payment date dfaell if it is equal to the system date. If not then a message is sent to the message handler. Here is the code:
      DATA: faelligkeit TYPE d,
            faelligkeit_text type c length 10,
            meldungstext TYPE c LENGTH 100.
      FIELD-SYMBOLS: <it_source> LIKE LINE OF pi_proxy_transaction->a_tab_conditions.
      IF sy-uname = 'XYZ'.
    *    BREAK-POINT.
        READ TABLE pi_proxy_transaction->a_tab_conditions INDEX 1
          ASSIGNING <it_source>.
        faelligkeit = <it_source>-dfaell.
        CALL FUNCTION 'CONVERT_DATE_TO_EXTERNAL'
           EXPORTING
             DATE_INTERNAL                  = faelligkeit
           IMPORTING
             DATE_EXTERNAL                  = faelligkeit_text
           EXCEPTIONS
             DATE_INTERNAL_IS_INVALID       = 1
             OTHERS                         = 2
        IF sy-subrc <> 0.
           MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
             WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
        ENDIF.
        IF faelligkeit <> sy-datum.
          CONCATENATE 'Fälligkeit' faelligkeit_text 'incorrect' INTO meldungstext separated by space.
          CALL METHOD pi_proxy_messages->set_message
            EXPORTING
              pi_message_id       = 'T0'
              pi_message_number   = '101'
              pi_message_severity = 'E'
              pi_message_var1     = meldungstext
            EXCEPTIONS
              OTHERS              = 4.
        ENDIF.
      ENDIF.
    It is not a really nice coding but it shows in a simple way how to use the BAdI.
    Regards
    Robert

  • BADI/ User Exit for transaction FTR_EDIT/FTR_CREATE

    Hi All,
    I want a BADI/User Exit for FTR_EDIT/FTR_CREATE transactions to validate company code and partner fields.

    Hi,
    here is a coding example that I implemented in the BAdI FTR_TR_GENERIC. This coding is executed when the user press the check button. The method is EVT_TRANSACTION_CHECK. This example is checking the payment date dfaell if it is equal to the system date. If not then a message is sent to the message handler. Here is the code:
      DATA: faelligkeit TYPE d,
            faelligkeit_text type c length 10,
            meldungstext TYPE c LENGTH 100.
      FIELD-SYMBOLS: <it_source> LIKE LINE OF pi_proxy_transaction->a_tab_conditions.
      IF sy-uname = 'XYZ'.
    *    BREAK-POINT.
        READ TABLE pi_proxy_transaction->a_tab_conditions INDEX 1
          ASSIGNING <it_source>.
        faelligkeit = <it_source>-dfaell.
        CALL FUNCTION 'CONVERT_DATE_TO_EXTERNAL'
           EXPORTING
             DATE_INTERNAL                  = faelligkeit
           IMPORTING
             DATE_EXTERNAL                  = faelligkeit_text
           EXCEPTIONS
             DATE_INTERNAL_IS_INVALID       = 1
             OTHERS                         = 2
        IF sy-subrc <> 0.
           MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
             WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
        ENDIF.
        IF faelligkeit <> sy-datum.
          CONCATENATE 'Fälligkeit' faelligkeit_text 'incorrect' INTO meldungstext separated by space.
          CALL METHOD pi_proxy_messages->set_message
            EXPORTING
              pi_message_id       = 'T0'
              pi_message_number   = '101'
              pi_message_severity = 'E'
              pi_message_var1     = meldungstext
            EXCEPTIONS
              OTHERS              = 4.
        ENDIF.
      ENDIF.
    It is not a really nice coding but it shows in a simple way how to use the BAdI.
    Regards
    Robert

  • BADI / USER-EXIT FOR DEFAULTING THE FIELD VTTK-TNDR_ACTC IN TCODE VT01N

    Hi,
    I require a BADI / USER-EXIT for defaulting the field VTTK-TNDR_ACTC(Currency of Actual Shipment costs) to 'EUR' in transaction VT01N(Shipment Transaction) .
    Please could anyone help me with this .
    Regards,
    Sushanth H.S.

    Hi!
    User Exits in Transportation
    In Transportation, there are enhancements that you can use with transaction CMOD.
    For a detailed description of the individual enhancements, see the documentation on the individual enhancements or function modules in transaction SMOD.
    You can display all enhancements that are available for the area of transportation by choosing F4 in the Enhancement field. Enter V56* in the Enhancement field and choose Execute. Enter V54* to get a list of all enhancements for the area of shipment cost processing.
    Business Add-Ins in the transports
    Business add-ins (BADIs) are predefined user exits. They enable businesses, partners, and customers to add additional softward to the SAP source code. The linkup of SAP's New Dimension Products, such as APO and BW, to the standard system is thus possible.
    Customer-specific functions can be executed before the save time and after the database update.
    The following methods are available for the BADI with the definition name 'BADI_LE_SHIPMENT':
    AT_SAVE: BADI is called up at the time of the save. Checks and return to dialog are possible.
    BEFORE:_UPDATE: BADI is called up right before the data is saved to the database, that is, when all the data is available (for example, internal ly assigned shipment number).
    IN_UPDATE: BADI is called up after the database update.
    Standard Settings
    Creating a BADI method:
    Call up transaction SE19. Enter a name of your choice. Choose "create" and in the dialog box enter the definition name 'BADI_LE_SHIPMENT'. Afterwards, enter a short text for implementation. Save the BADI.
    On the tab page 'Interface', choose the method for implementation by double-clicking on it. Now you can enter your customer-specific program code. Save and activate the code. You can acess the transmission parameters entered in the BADI definition. With the method ***_AT_SAVE you can initiate the exception ERROR_WITH_MESSAGE (description 'An error message has occurred' ) if you wish to return to the dialog.
    Afterwards, go to the heading and activate the interface.
    Regards
    Tamá

Maybe you are looking for