User exit or Badi for VL31N (create inbound delivery)

Dear friends.
I wish to add a check before saving in the transaction VL31N for that i need to know user exit or BADI..can you help me to know what possible user exit or badi available for this task.. your suggestion and article will be greate help of mine,
thanking you
regards,
Naim

Exit Name Description
V02V0001 Sales area determination for stock transport order
V02V0002 User exit for storage location determination
V02V0003 User exit for gate + matl staging area determination (headr)
V02V0004 User Exit for Staging Area Determination (Item)
V50PSTAT Delivery: Item Status Calculation
V50Q0001 Delivery Monitor: User Exits for Filling Display Fields
V50R0001 Collective processing for delivery creation
V50R0002 Collective processing for delivery creation
V50R0004 Calculation of stock for POs for shipping due date list
V50S0001 User Exits for Delivery Processing
V53C0001 Rough workload calculation in time per item
V53C0002 W&S: RWE enhancement - shipping material type/time slot
V53W0001 User exits for creating picking waves
VMDE0001 Shipping Interface: Error Handling - Inbound IDoc
VMDE0002 Shipping Interface: Message PICKSD (Picking, Outbound)
VMDE0003 Shipping Interface: Message SDPICK (Picking, Inbound)
VMDE0004 Shipping Interface: Message SDPACK (Packing, Inbound)
BADI
DELIVERY_PUBLISHregards
vinod

Similar Messages

User Exit or Badi for VL01N (before the delivery will be displayed)

Hello Togheter:
I have to change the sort order of the delivery items in VL01N before they will be displayed (not at the moment when they'll be stored on the database). Does anybody know any enhancement or user exit or BADI that i can use for this? I've tried with BADI LE_SHP_DELIVERY_PROC, but there is no methode which I can use for reordering the table XLIPS/LIPS before the delivery will be displayed.
Thanks in advance
Klaus

Exits for VL01N ::::::
V02V0001            Sales area determination for stock transport order
V02V0002            User exit for storage location determination
V02V0003            User exit for gate + matl staging area determination (headr)
V02V0004            User Exit for Staging Area Determination (Item)
V50PSTAT            Delivery: Item Status Calculation
V50Q0001            Delivery Monitor: User Exits for Filling Display Fields
V50R0001            Collective processing for delivery creation
V50R0002            Collective processing for delivery creation
V50R0004            Calculation of Stock for POs for Shipping Due Date List
V50S0001            User Exits for Delivery Processing
V53C0001            Rough workload calculation in time per item
V53C0002            W&S: RWE enhancement - shipping material type/time slot
V53W0001            User exits for creating picking waves
VMDE0001            Shipping Interface: Error Handling - Inbound IDoc
VMDE0002            Shipping Interface: Message PICKSD (Picking, Outbound)
VMDE0003            Shipping Interface: Message SDPICK (Picking, Inbound)
VMDE0004            Shipping Interface: Message SDPACK (Packing, Inbound)
Hope they may help a little.
Regards,
Jignesh

BAPI for VL31N:Create Inbound Delivery

Hi all,
Please give the BAPI for VL 31N: Create Inbound delivery transaction
thanks

No bapi but you can use this function module GN_DELIVERY_CREATE
Select the data required - see below
select ebeln ebelp menge meins matnr werks lgort bstae loekz elikz
         lmein umrez umren insmk pstyp sobkz knttp kzfme kzvbr
         ematn mfrnr mfrpn emnfr cuobj uebto untto uebtk bwtar idnlf
         txz01 mfrgr gewei voleh ntgew brgew volum ean11 aktnr abeln
         abelp aurel matkl upvor uptyp uebpo wepos
          into corresponding fields of table xekpo_short
          from ekpo
           where ebeln = i_ebeln
             and ebelp = i_ebelp.
if sy-subrc ne 0.
    e_rc = 4.
else.
    read table xekpo_short index 1.
    call function 'ME_EKKO_SINGLE_READ'
      exporting
        pi_ebeln         = xekpo_short-ebeln
      importing
        po_ekko          = ekko
      exceptions
        no_records_found = 1
        others           = 2.
    if sy-subrc ne 0.
      e_rc = 4.
    elseif ekko-bstyp ne 'F' and ekko-bstyp ne 'L'.
      e_rc = 4.
    endif.
endif.
clear xvbsk.
xvbsk-mandt = sy-mandt.
xvbsk-ernam = sy-uname.
xvbsk-erdat = sy-datum.
xvbsk-uzeit = sy-uzeit.
xvbsk-smart = 'L'.
*- Nummer VBSK vergeben -
select single * from tvsa where smart = xvbsk-smart.
if sy-subrc = 0.
    call function 'NUMBER_GET_NEXT'
      exporting
        nr_range_nr = tvsa-numki
        object      = 'RV_SAMMG'
      importing
        number      = xvbsk-sammg
      exceptions
        others      = 01.
    if sy-subrc ne 0.
      message e700(me) with tvsa-numki text-007.
    endif.
else.
    message e700(me) with space text-007.
endif.
data: h_grkor like lips-grkor,         "Liefergruppe         "386409
       h_bsmng like ekpo-menge.         "Bestellmenge übergeordnete Pos.
if not ekko-lifnr is initial.
    call function 'VENDOR_MASTER_DATA_SELECT_12'
      exporting
        pi_lifnr       = ekko-lifnr
        pi_ekorg       = ekko-ekorg
      importing
        pe_lfm1        = lfm1
      exceptions
        no_entry_found = 1
        others         = 2.
    xkomdlgn-vsbed = lfm1-vsbed.
else.
    clear xkomdlgn-vsbed.
endif.
xkomdlgn-lifnr = ekko-lifnr.
xkomdlgn-inco1 = ekko-inco1.                              "363954
xkomdlgn-inco2 = ekko-inco2.                              "363954
xkomdlgn-exnum = ekko-exnum.                              "363954
xkomdlgn-bukrs_best = ekko-bukrs.                         "363954
xkomdlgn-matnr = xekpo_short-matnr.
xkomdlgn-werks = xekpo_short-werks.
xkomdlgn-lgort = xekpo_short-lgort.
xkomdlgn-charg = ?
xkomdlgn-vrkme = xekpo_short-meins.
xkomdlgn-meins = xekpo_short-lmein.
xkomdlgn-umvkz = xekpo_short-umrez.
xkomdlgn-umvkn = xekpo_short-umren.
if xekpo_short-matnr eq space.                            "386409
    xkomdlgn-meins = xekpo_short-meins.
    xkomdlgn-umvkz = 1.
    xkomdlgn-umvkn = 1.
endif.
xkomdlgn-insmk = xekpo_short-insmk.
xkomdlgn-kzfme = xekpo_short-kzfme.
xkomdlgn-kzvbr = xekpo_short-kzvbr.           "note 384051
xkomdlgn-lfimg = p_lfimg.
xkomdlgn-lfdat = p_eindt.
xkomdlgn-vgbel = xekpo_short-ebeln.
xkomdlgn-vgpos = xekpo_short-ebelp.
xkomdlgn-lfart = gf_dlv_type.
xkomdlgn-vgtyp = 'V'.
xkomdlgn-kzazu = 'X'.                "??? what's that for ????
xkomdlgn-knttp = xekpo_short-knttp.
xkomdlgn-sobkz = xekpo_short-sobkz.
if xekpo_short-matnr is initial or xekpo_short-pstyp = '6'.
    xkomdlgn-posar = 'B'.
endif.
xkomdlgn-ematn = xekpo_short-ematn.
xkomdlgn-mfrnr = xekpo_short-mfrnr.
xkomdlgn-mfrpn = xekpo_short-mfrpn.
xkomdlgn-emnfr = xekpo_short-emnfr.
xkomdlgn-cuobj = xekpo_short-cuobj.
xkomdlgn-uebto = xekpo_short-uebto.
xkomdlgn-untto = xekpo_short-untto.
xkomdlgn-uebtk = xekpo_short-uebtk.
xkomdlgn-bwtar = xekpo_short-bwtar.
xkomdlgn-kdmat = xekpo_short-idnlf.
xkomdlgn-arktx = xekpo_short-txz01.
xkomdlgn-mfrgr = xekpo_short-mfrgr.
xkomdlgn-gewei = xekpo_short-gewei.
xkomdlgn-voleh = xekpo_short-voleh.
xkomdlgn-ntgew = xekpo_short-ntgew * xkomdlgn-lfimg.
xkomdlgn-brgew = xekpo_short-brgew * xkomdlgn-lfimg.
xkomdlgn-volum = xekpo_short-volum * xkomdlgn-lfimg.
xkomdlgn-ean11 = xekpo_short-ean11.
xkomdlgn-aktnr = xekpo_short-aktnr.
xkomdlgn-abeln = xekpo_short-abeln.
xkomdlgn-abelp = xekpo_short-abelp.
xkomdlgn-aurel = xekpo_short-aurel.
xkomdlgn-idnlf = xekpo_short-idnlf.
xkomdlgn-matkl = xekpo_short-matkl.
Leergut-Stückliste übernehmen
clear xkomdlgn-grkor.
clear xkomdlgn-kmpmg.
clear xkomdlgn-uepos.
if xekpo_short-upvor ca '3X'.
    h_grkor = h_grkor + 1.
    xkomdlgn-grkor = h_grkor.
    h_bsmng = xekpo_short-menge.
endif.
if not xekpo_short-uebpo is initial and
         xekpo_short-uptyp ca '3X'.
    xkomdlgn-uepos = xekpo_short-uebpo.
    xkomdlgn-grkor = h_grkor.
    if h_bsmng ne 0.
      xkomdlgn-kmpmg = xekpo_short-menge / h_bsmng.
    endif.
endif.
*- Konsignation - SOBKZ 'K' hart reinsetzen, da von Pstyp abhäng......
if xekpo_short-pstyp eq '2'.
    xkomdlgn-sobkz = 'K'.
endif.
Kontierungsfelder
if xekpo_short-sobkz eq 'E' or xekpo_short-sobkz eq 'Q'.
    call function 'MMPUR_EKKN_READ_EBELN_EBELP'
      exporting
        pi_ebeln                   = xekpo_short-ebeln
        pi_ebelp                   = xekpo_short-ebelp
      PI_BYPASSING_BUFFER        =
      PI_REFRESH_BUFFER          =
      tables
        pto_ekkn_po                = xekkn
      exceptions
        no_records_requested       = 1
        others                     = 2.
    if sy-subrc eq 0.
      read table xekkn index 1.
      xkomdlgn-ps_psp_pnr = xekkn-ps_psp_pnr.
      xkomdlgn-vbelv      = xekkn-vbeln.
      xkomdlgn-posnv      = xekkn-vbelp.
    endif.
endif.
append xkomdlgn.

User Exit or BADI for MIGO on entry of inbound delivery number

Hi all,
I want a user exit or BADI for MIGO, my requirement is that whenever a user enters an inbound delivery number and presses enter in MIGO the exit should get fired.
Please help, if someone knows.
Thanks and Regards,
Mohammed.

hi
you can try out various BADI'S-
MB_MIGO_BADI
MB_MIGO_ITEM_BADI
Helpful function modules:-
MIGO_BADI_EXAMPLE
MIGO_BADI_EXAMPLE_GET_DATA
MIGO_BADI_EXAMPLE_GET_HEADER
MIGO_BADI_EXAMPLE_PUT_DATA
MIGO_BADI_EXAMPLE_PUT_HEADER
MIGO_BADI_EXAMPLE_UPATE_DATA
MIGO_BADI_EXAMPLE_UPDATE_HEAD
I hope at least one of these helps.
regards
Aakash

User exit or BADI for Tcode ME51N

Hi All,
My requirement is i need to check available quantity at the time of Purchase req creation. If PR quantity is available in stock then it should not allow to create new PR.
Is there any user exit or Badi for this requirement. Kindly send me.
Regards,
Paras

Hai,
User Exit: MEREQ001
Function exit             EXIT_SAPLMEREQ_001
                               EXIT_SAPLMEREQ_002
                               EXIT_SAPLMEREQ_003
                               EXIT_SAPLMEREQ_004
                               EXIT_SAPLMEREQ_005
                               EXIT_SAPLMEREQ_006
                               EXIT_SAPLMEREQ_007
                               EXIT_SAPLMEREQ_008
                               EXIT_SAPLMEREQ_009
                               EXIT_SAPLMEREQ_010
Screen exit               SAPLMEGUI
Include tables           CI_EBANDB
                               CI_EBANMEM

User Exit OR Badi for MK01 transaction (used for saving vendor amster data)

Hi All,
I have a requirement where I have to call my workflow, when we create the Vendor using my custom transaction (ZMK01, which is a copy of standard transaction MK01).
For Workflow triggering I am using FM 'SAP_WAPI_CREATE_EVENT' in the user exit 'EXIT_SAPMF02K_001' but this is only for checking the data on saving Vendor Master.
So I want to use FM 'SAP_WAPI_CREATE_EVENT' at right place. For that , I need User-Exit or BADI which is used for saving vendor master data.
Could anyone please help me to find out the user exit or BADI for save event of vendor master data using transaction MK01.
Looking forward to your advise and thanks in advance.
Best Regards,
Mamta

Hi ,
I forgot to activiate the project linked with User exit 'EXIT_SAPMF02K_001' .
so problem is solved now
Thanks,
Mamta

User exit or BADI for recruitment

Hi,
I am new to HCM, can you give me user exit or badi for recruitment.
Requirement - i have developed an infotype which i am updating through BSP, while the custom infotype is updated it should simultaneously update some of my Z tables. Hoping for positve replies earliest.
Thanks in advance:-
Santosh

Hi,
InfotypeThe data fields of HR master data, time management and recruitment are grouped logically into information types or infotypes for short.
Examples of infotypes are "Family/Related Person", "Organizational Assignment, "Basic Pay".
The following naming conventions apply to infotypes:
Infotypes 0000 to 0999 are used for HR master data
and sometimes for applicant data
Infotypes 1000 - 1999 for organizational management
Infotypes 2000 - 2999 for time data
Infotypes 4000 - 4999 for applicant data
Infotypes 9000 - 9999 for customers
Function character of step
This controls for which types of processing (create, change and/or delete a data record) a dynamic action should be carried out.
The processing type is indicated by a two-digit numeric value. These values can be added up; in other words, you can enter several processing types for each infotype, subtype or field. A dynamic action can also be carried out independent of the current processing type.
00 for Independent of the current function carried out
02 for Change
04 for Create
06 for Change and create
08 for Delete
10 for Change and delete
12 for Create and delete
Examples
If you enter 06, an action is carried out if the specified infotype was created or changed.
If you enter 00, an action is carried out irrespective of whether the specified infotype was created, changed or deleted.
Variable function part
The variable function part, which depends on the indicator for step, can have the following meaning:
P - Plausibility checks
You can enter values for specific infotype fields. Field names must be entered in full. Literals and constants can serve as comparison values. These must be enclosed by inverted commas. Variables can also be used.
The old value of a field can be used for comparison; the field name must be preceded by PSAVE-.
If fields of other infotypes are used for comparison, these must be stored in the module pool of the current infotype.
The following comparison operators are supported:
= equal to,
< less than,
<= less than or equal to,
> greater than
>= greater than or equal to and
<> not equal to.
Consecutive checks must be linked by a logical AND. Logical OR links must also be indicated by a /X.
Note:
Note that all checks with OR links must have a /X.
If the result of the comparison operation is not "true", then the following commands (I, F, W etc.) are skipped over until a field is reached or a new comparison operation takes place.
Examples
Infotype Field ..... Ind. Variable function part
0007 STAT3 P P0007-STAT3='0'
0007 STAT3 P PSAVE-STAT3='1'
The step is taken if the value in the P0007-STAT3 field changes from 1 to 0.
0007 P P0013-KLKZ1<>'0'/X
0007 P P0013-ALVKZ<>'0'/X
0007 P P0013-RVKZ1<>'0'/X
0007 P P0013-RVNUM=SPACE
The first three conditions are linked by an OR; at least one of these conditions must be met. Condition 4 must always be met.
The step is taken if the following holds true:
P0013-KVKZ1 not equal to 0 or P0013-ALVKZ not equal to 0 or P0013-RVKZ1 not equal to 0, and P0013-RVNUM empty.
I - Maintain infotype record
Enter the step, infotype, subtype, object ID, start and end dates of the record and an indicator which defines whether the step is to be run in the background. The possible actions are INS, COP, MOD, and DEL.
Use commas to separate selection criteria just like the separator in the matchcode. If an entry is missing, the system inserts a comma.
Separate the indicator for suppressing dialog from other entries by a slash D (/D).
Constants, such as those for subtypes, are not enclosed in inverted commas.
Variable entries are also permitted. Fields containing such values must be put in brackets.
Examples:
Infotype Field .... Ind. Variable function part
 .... I INS,19,01/D
Step: Create a Dates record, subtype 01, run in the background
 .... I DEL,14,M559
Step: Delete Rec. Payments/Deds. record with subtype (wage type) M559.
0007 .... I INS,8,,,(P0007-BEGDA),(P0007-ENDDA)
Step: Create a Basic Pay record (0008) without subtype and object ID. The start and end dates are the same as those in the current Planned Working Time record (0007); specify these two fields only if they are filled because the dynamic action was triggered by this infotype.
W - Default values for new record
Literals or variables are used as default values.
Set the defaults for the infotype, subtype, object ID, start and end dates using an I step and not a W step.
Do not set defaults for Q fields of an infotype because the values for these fields are derived from the corresponding P fields.
Examples
Infotype Subtype ..... FC Ind. Variable function part
0021 2 04 I INS,0015,M430
0021 2 04 W P0015-BETRG='10000'
When a Family/Related Person record (0021) record with subtype 2 (child) is created, an Additional Payments record (0015) with a default amount of 100.00 is created.
V - Cross-reference to another step
Here, you can combine fields to groups. The variable function part contains the value in the field which follows the "field" column. Steps which are specified only for the following field are also triggered for each of the other fields.
Examples
Infotype Field ..... FC Ind. Variable function part
0016 PRBZH 06 V PRBZT
0016 PRBZT 06 I DEL,0019,01/D
Infotype 0019, subtype 01 is deleted in the background when the field PRBZT or PRBZH in infotype 0016 is changed or created (function code 06).
The following entries are equivalent:
0016 PRBZH 06 I DEL,0019,01/D
0016 PRBZT 06 I DEL,0019,01/D
F - Call a routine
You can call internal (module pool) as well as external routines.
If you call external routines, type the program name in brackets after the routine name. Do not specify 'using' parameters. When calling an external routine, all data must be declared in a common part. You can use the fields of structure RP50D to return values from the routine. These are not used in the standard system and can only be populated via the routine and then can be used for defaults (W-Commands).
This allows customer-specific routines to be formulated with all the above steps.
Example 1:
Infotype Field ..... Ind. Var.function part
0016 PRBZT F PROBATION
0016 PRBZT I INS,19,01
0016 PRBZT W P0019-VTRMN=PRBEND
Module pool MP001600 contains the PROBATION routine. This routine uses the entries in the fields P0016-PRBZT and P0016-PRBEH to determine the end of the probation period which it stores in the field PRBEND.
The system creates a new 'Dates' record with the reminder date = PRBEND.
Example 2:
Infotyp ..... Ind. Var. function part
0001 F GET_DATE(ZPUDYN01)
0001 I INS,19,01
0001 W P0019-VTRMN=RP50D-DATE1
The GET_DATE routine in program ZPUDYN01 calculates a date and enters this date in the RP50D-DATE1 field via "TABLES RP50D" in ZPUDYN01. This date can be user-defined in GET_DATE: if necessary, user-defined infotypes can be read afterwards.
M - Send a mail
Enter the name of the feature which defines the characteristics of the mail.
Example
Infotype Field ..... Ind. Var.function part
0001 SACHP M M0001
A mail is sent when the field SACHP is changed. The characteristics of the mail are defined in feature M0001.
In the standard system, feature M0001 is provided as a model. The documentation on feature M0001 explains how to define the characteristics of a mail.
ADDITIONAL HINTS
If you use a date as a constant, enter it as YYYYMMDD (YYYY=year, MM=month, DD=day).
The table strings T001P, T503 and PSPAR are filled with the values which are valid on the record start date.
The old values of the infotype are stored in the field string PSAVE. The structure of this string is the same as the Pnnnn structure (nnnn=infotype). The structure is filled with (valid) values only when the delete, change and create functions are used.
Please read Create dynamic actions in the Implementation Guide.
Regards
Bernd

User Exits or BADI for Tcode ME51N

Hi All,
My requirement is i need to check available quantity at the time of Purchase req creation. If PR quantity is available in stock then it should not allow to create new PR.
Is there any user exit or Badi for this requirement. Kindly send me.
Regards,
Paras

Hi Paras,
Copy this program and execute. Will get all list of existin g Exits and Badis.
very useful program
Below code will give a list of BADIs for particular transaction.
*& Report ZNEGI16 *
REPORT ZNEGI16 .
TABLES : TSTC,
TADIR,
MODSAPT,
MODACT,
TRDIR,
TFDIR,
ENLFDIR,
SXS_ATTRT ,
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,
P_PGMNA LIKE TSTC-PGMNA .
DATA wa_tadir type tadir.
START-OF-SELECTION.
IF NOT P_TCODE IS INITIAL.
SELECT SINGLE * FROM TSTC WHERE TCODE EQ P_TCODE.
ELSEIF NOT P_PGMNA IS INITIAL.
TSTC-PGMNA = P_PGMNA.
ENDIF.
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 in ('SMOD', 'SXSD')
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:/(105) SY-ULINE.
FORMAT COLOR COL_HEADING INTENSIFIED ON.
Sorting the internal Table
sort jtab by OBJECT.
data : wf_txt(60) type c,
wf_smod type i ,
wf_badi type i ,
wf_object2(30) type C.
clear : wf_smod, wf_badi , wf_object2.
Get the total SMOD.
LOOP AT JTAB into wa_tadir.
at first.
FORMAT COLOR COL_HEADING INTENSIFIED ON.
WRITE:/1 SY-VLINE,
2 'Enhancement/ Business Add-in',
41 SY-VLINE ,
42 'Description',
105 SY-VLINE.
WRITE:/(105) SY-ULINE.
endat.
clear wf_txt.
at new object.
if wa_tadir-object = 'SMOD'.
wf_object2 = 'Enhancement' .
elseif wa_tadir-object = 'SXSD'.
wf_object2 = ' Business Add-in'.
endif.
FORMAT COLOR COL_GROUP INTENSIFIED ON.
WRITE:/1 SY-VLINE,
2 wf_object2,
105 SY-VLINE.
endat.
case wa_tadir-object.
when 'SMOD'.
wf_smod = wf_smod + 1.
SELECT SINGLE MODTEXT into wf_txt
FROM MODSAPT
WHERE SPRSL = SY-LANGU
AND NAME = wa_tadir-OBJ_NAME.
FORMAT COLOR COL_NORMAL INTENSIFIED OFF.
when 'SXSD'.
For BADis
wf_badi = wf_badi + 1 .
select single TEXT into wf_txt
from SXS_ATTRT
where sprsl = sy-langu
and EXIT_NAME = wa_tadir-OBJ_NAME.
FORMAT COLOR COL_NORMAL INTENSIFIED ON.
endcase.
WRITE:/1 SY-VLINE,
2 wa_tadir-OBJ_NAME hotspot on,
41 SY-VLINE ,
42 wf_txt,
105 SY-VLINE.
AT END OF object.
write : /(105) sy-ULINE.
ENDAT.
ENDLOOP.
WRITE:/(105) SY-ULINE.
SKIP.
FORMAT COLOR COL_TOTAL INTENSIFIED ON.
WRITE:/ 'No.of Exits:' , wf_smod.
WRITE:/ 'No.of BADis:' , wf_badi.
ELSE.
FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.
WRITE:/(105) 'No userexits or BADis exist'.
ENDIF.
ELSE.
FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.
WRITE:/(105) 'Transaction does not exist'.
ENDIF.
AT LINE-SELECTION.
data : wf_object type tadir-object.
clear wf_object.
GET CURSOR FIELD FIELD1.
CHECK FIELD1(8) EQ 'WA_TADIR'.
read table jtab with key obj_name = sy-lisel+1(20).
move jtab-object to wf_object.
case wf_object.
when 'SMOD'.
SET PARAMETER ID 'MON' FIELD SY-LISEL+1(10).
CALL TRANSACTION 'SMOD' AND SKIP FIRST SCREEN.
when 'SXSD'.
SET PARAMETER ID 'EXN' FIELD SY-LISEL+1(20).
CALL TRANSACTION 'SE18' AND SKIP FIRST SCREEN.
endcase.
Reward points if this helps.
hema.

Need user exit or BADI for FB60

Hi Guys!!,
I am working on one object which   belongs to FB60 transaction. I have to give error message when user enter the ZTERM Value above 45 days for particular vendor group(MSMED).please help out.
Richard.

Hi,
Foloowing are available user exits and BADIs for FB60.
F050S001                                               FIDCMT, FIDCC1, FIDCC2: Edit user-defined IDoc segment
F050S002                                               FIDCC1: Change IDoc/do not send
F050S003                                               FIDCC2: Change IDoc/do not send
F050S004                                               FIDCMT, FIDCC1, FIDCC2: Change outbound IDoc/do not send
F050S005                                               FIDCMT, FIDCC1, FIDCC2 Inbound IDoc: Change FI document
F050S006                                               FI Outgoing IDoc: Reset Clearing in FI Document
F050S007                                               FIDCCH Outbound: Influence on IDoc for Document Change
F180A001                                               Balance Sheet Adjustment
FARC0002                                              Additional Checks for Archiving MM Vendor Master Data
RFAVIS01                                               Customer Exit for Changing Payment Advice Segment Text
RFEPOS00                                              Line item display: Checking of selection conditions
RFKORIEX                                              Automatic correspondence
SAPLF051                                              Workflow for FI (pre-capture, release for payment)
Please find the one suitable to your need.
Hope it will help you.
Regards
Natasha Garg

User exit or badi for transaction PPOME

Hi,
is there any user exit or Badi available when creating a
relation between PD objects by means of transaction PPOME?.
Best regards.

HI
To search for a badi, go to se 24 display class cl_exithandler.
double click on method get_instance, get a break point on case statement.
execute and start the required transaction in new session.
look for variable exit_name. It would show the available badi's.
Please do reward if useful
Regards
Dinesh

User Exit or BADI FOR ME59N

Hi All,
   My requirement is in ME59N if Document Type is ZCD or ZSD it should not consider the Rounding Value (MARC-BSTRF) which is coming from Materrial Master (MRP1 View) and Purchase Info Record (EINE-RDPRF) which is coming from Purchase Info Record(ME12 or ME13), Can any one suggest me the right User Exit or BADI for this, Please go through the requirement.
Regards,
Sudhakar .A
Edited by: Sudhakar Allam on Feb 5, 2010 4:31 AM

HI Sudhakar ,
                          These are the list of enhancements and Badi's available for ME59N ,
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
MM06E011                                Activate PReq Block
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
AMPL0001                                User subscreen for additional data on AMPL
MRFLB001                                Control Items for Contract Release Order
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
MEQUERY1                                Enhancement to Document Overview ME21N/ME51N
MELAB001                                Gen. forecast delivery schedules: Transfer schedule implem.
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
The list of Badi are
ME_PROCESS_REQ_CUST                     Enhancements for Processing Enjoy PReqs: Customer
ME_PROCESS_REQ                          Enhancements for Processing Enjoy PReqs: Internal
ME_PROCESS_PO_CUST                      Enhancements for Processing Enjoy Purchase Order: Customer
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_PURCHDOC_POSTED                      Purchasing Document Posted
SMOD_MRFLB001                           Control Items for Contract Release Order
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)
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_DEFINE_CALCTYPE                      Control of Pricing Type: Additional Fields
ME_CHANGE_OUTTAB                        Enrich ALV Output Table in Purchasing
ME_CHANGE_CHARACTER                     Customer-Specific Characteristics for Product Allocation
ME_CCP_DEL_DURATION                     Calc. of Delivery Duration in CCP Process (Not in Standard)
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_BADI_DISPLAY_DOC                     BAdI for Internal Control of Transaction to be Invoked
ME_ACTV_CANCEL_PO                       BAdI for Activating the Cancel Function at Header Leve
MEGUI_LAYOUT                            BAdI for Enjoy Purchasing GUI
ME_CHECK_ALL_ITEMS                      Run Through Items Again in the Event of Changes in EKK
ME_COMMTMNT_REQ_RE_C                    Check of Commitment Relevance of Purchase Requisitions
ME_COMMTMNT_REQ_RELE                    Check of Commitment Relevance of Purchase Requisitions
ME_COMMTMNT_PO_REL_C                    Check for Commitment-Relevance of Purchase Orders
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
regards.

User exit or BADI for CNS0?

Dear Friends,
I want to validate something when a delivery is created from a Project from tcode CNS0. I was not able to find any user exit or BADI for it, if any body know any BADI or User exit, please let me know.
Thanks in advance
IK

Hi,
there is NO user-exits available for the CNS0
and BADI & Enhacement Point are avasilable ->
next go to t-code Se15>expand the enhacement tab>enter package under userexit and
                                                     execute you will get the list of exits
                                                     available...
                                                  -->enter package under Badi's tab and
                                                     execute you will get the list of Badi's
                                                     available...
                                                  -->Enter package Under Enhacement points and execute
                                                    you will get the list of Enhacements available
Craete Enhacement Points Implementation----
And to find the Enhamcement Points go to progrmam or screen where the Items table is there and
Press SHIFT+F4(enhace application tool) -->go to menu bar >EDIT>enhacement Operations
             -->Show implicit enhacements
--> once the yellow bar/Line appears right click and create a enhancement and add your own code.
Prabhudas

User exit or badi for vl02n

Dear ALL,
Can any one tell me the user exit or badi for VL02N.
I want it to trigger while saving.
How to write code in the form userexit_save_document.
Please guide me.
Regards,
Vidhya.

Hi,
check the following BADI:
BADI_IBDLV_DISPATCH_SE -BADI to dispatch Inbound Delivery for service enabled
You can check the following BADI's also for vl02n transaction..
LE_SHP_DELIVERY_PROC ---     Enhancements in Delivery Proces
LE_SHP_PRICING                 -
Interface to Pricing in the Delivery
LE_SHP_TAB_CUST_HEAD    --- Header Detail Delivery
LE_SHP_TAB_CUST_ITEM      -
Item Detail Deliver
LE_SHP_TAB_CUST_OVER   -
Tab Page for Own Data - Item Overview Delivery
LE_SHP_TAB_SCEM_HEAD
LE_SHP_TAB_GLTR_HEAD
BADI_SD_TO_FM                   -
Commitments Management in SD for Funds Management
Regards
Kiran

User exit or BADI for tcode CNS0

Dear Friends,
I want to validate something when a delivery is created from a Project from tcode CNS0. I was not able to find any user exit or BADI for it, if any body know any BADI or User exit, please let me know.
Thanks in advance
IK

Hi,
there are tow enhacement spots avaialble for T-code CNS0
ES_SAPLCNSH ES_SAPLCNSH
go to se18>select enhacement spot>ES_SAPLCNSH -->Display
The above enhacement is available in FM 'FUNCTION cn_sh_goods_movement_data.'
And also Enhacement spot avaialbel in NCLUDE LCNSHFM2 .
try to write your code in above two enhacement spots and check whether it will work for requirement.
Prabhudas

User exit or badi for me52n transaction.

Hi all,
i have a requirement to write a user exit or badi for me52n transaction. the requirement is in header section, only one plant should be accepted. that is in the first row one plant will be inserted. in the second row if we are inserting another plant other the first row plant, it should not accept it and it should raise an error.
that is from the second row onwards, every plant should match with the first row plant.
if any part of this issue is unclear, plz let me know so that i can explain it clearly
this is urgent requirement.
please let me know the solution as soon as possible.
points will be awarded.
thanking u in advance.
A.srinivas.

In this version exit EXIT_SAPLMEREQ_005 should exists (look at OSS <a href="https://service.sap.com/sap/support/notes/843446">Note 843446 - MEREQ001: Cannot call up external service data in user exit</a> this note refers to the exit and is applicable in 4.70. Look also at OSS <a href="https://service.sap.com/sap/support/notes/310154">Note 310154 - ME21N/ME51N: Customer-specific check, generating error log</a>
Regards

User exit or Badi for VL31N (create inbound delivery)

Similar Messages

Maybe you are looking for