User Exit or BADI for ml81n - Service Entry Sheet

Hi all,
I would like to find a user exit or BADI or enhancement upon saving.
The requirement is posting to specific GL A/C from the Service No. given.
Please don't provide me a list of unnecessary user exit or BADI.
Urgently need for solution, Thanks.

Hi,
Check out the various exits for ml81n
INTERFAC            Interface for data transfer
SRVDET              User screen on tab strip of service detail screen
SRVEDIT             Service list control (maintenance/display)
SRVENTRY            Unplanned part of entry sheet (obsolete since Rel. 3.1G)
SRVESI              Data conversion entry sheet interface
SRVESKN             Set account assignment in service line
SRVESLL             Service line checks
SRVESSR             Set entry sheet header data
SRVEUSCR            User screen on entry sheet tabstrip
SRVKNTTP            Setting the account assgnmt category when reading in, if
SRVLIMIT            Limit check
SRVMAIL1            Processing of mail before generation of sheet
SRVMSTLV            Conversion of data during importing of standard service c
SRVPOWEB            Purchase order for service entry in Web
SRVQUOT             Service export/import for inquiry/quotations
SRVREL              Changes to comm. structure for release of entry sheet
SRVSEL              Service selection from non-SAP systems
SRV_FRM             SRV: Formula calculation (obsolete since 4.0A!)

Similar Messages

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 Exits or BAdis' for the Service Order create Transaction

Hi all,
 I need to Replace a field, "Product" in the "Item Details" area of the create Service Order Transaction(CRMD_BUS2000116) with some custom field.
Are there any Exits/BAdi which will help me in doing this..
Thanks in advance
Sethu

Hi Sethu,
The user exits / BADI's for the Transaction(CRMD_BUS2000116 are not avaliable:
The following info from one forum to search user exits / BADI's that you can use: There are multiple ways of searching for BADI.
Finding BADI Using CL_EXITHANDLER=>GET_INSTANCE
Finding BADI Using SQL Trace (TCODE-ST05).
Finding BADI Using Repository Information System (TCODE- SE84).
1. Go to the Transaction, for which we want to find the BADI, take the example of Transaction VD02. Click on System->Status. Double click on the program name. Once inside the program search for CL_EXITHANDLER=>GET_INSTANCE.
Make sure the radio button In main program is checked. A list of all the programs with call to the BADIs will be listed.
The export parameter EXIT_NAME for the method GET_INSTANCE of class CL_EXITHANDLER will have the user exit assigned to it. The changing parameter INSTANCE will have the interface assigned to it. Double click on the method to enter the source code.
Definition of Instance would give you the Interface name.
2. Start transaction ST05 (Performance Analysis).
Set flag field "Buffer trace"
Remark: We need to trace also the buffer calls, because BADI database tables are buffered. (Especially view V_EXT_IMP and V_EXT_ACT)
Push the button "Activate Trace". Start transaction VA02 in a new GUI session. Go back to the Performance trace session.
Push the button "Deactivate Trace".
Push the button "Display Trace".
The popup screen "Set Restrictions for Displaying Trace" appears.
Now, filter the trace on Objects:
V_EXT_IMP
V_EXT_ACT
Push button "Multiple selections" button behind field Objects
Fill: V_EXT_IMP and V_EXT_ACT
All the interface class names of view V_EXT_IMP start with IF_EX_. This is the standard SAP prefix for BADI class interfaces. The BADI name is after the IF_EX_.
So the BADI name of IF_EX_CUSTOMER_ADD_DATA is CUSTOMER_ADD_DATA
3. Go to Maintain Transaction (TCODE- SE93).
Enter the Transaction VD02 for which you want to find BADI.
Click on the Display push buttons.
Get the Package Name. (Package VS in this case)
Go to TCode: SE84->Enhancements->Business Add-inns->Definition
Enter the Package Name and Execute.
Here you get a list of all the Enhancement BADIs for the given package MB.
Also have a look at below report which will list BADIs.
REPORT Z_FIND_USER_EXITS.
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.
Hope it will help you.
Regards,
Arjun
Reward points if it helps

User exit Or Badi for creating Service order while modifying sales order.

Hi Experts,
I am creating Notification using transaction IW51.
In IW51 there is a button to create a sales order.
I click on sales order button and create a sales order.
Now notification and sales order are created.
Now i go in transaction VA02 and click on avalibility check push button .It gives me some popups in which i select copy all options.Then i click on save button
.At this point service order gets created.
My requirement :
Before the service order gets created i want to pass the notification data ; for ex- Equnr(Equipment number) to service order.
Thanks & Regards,
Chetan

Hi,
Are you saying first create notification,then service order
and then Sales order.
But the requirement is create notification then sales order and when you go in va02 and while modifying the sales order and create service order.
Thanks & regards,
chetan.

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

Autorisation object for accepting service entry sheet in ML81n

Dear Sapiens,
What is the authorisation object for accepting service entry sheet in ML81n, here with my client some users are not getting the acceptance flag.
kindly guide.
Viji kantha

Hi,
I would like to share with you additional information on activities 75 and 76 to the different release objects:
To accept the service entry sheet the user has to have both
activities 75 and 76. Please note that it is not possible to accept an entry sheet
without activity 76.
Activity 76 means maintain service entry sheets,
Activity 75 means accept service entry sheets.
In order to accept the entry sheet, you must change into the
change mode. In order to change into the change mode, you
need the activity 76.
This activity 76 will be used in both creating and changing of the
entry sheet.
Regards,
Edit

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 MIRO

Hi
I need add some validations to data entry in MIRO for send their respective error messages and stop data saving.
Does somebody knows some User Exit or Badi for make validations in MIRO ?
Regards
Frank

Hi,
you can use badi MRM_HEADER_CHECK. In order to put error message you can use function module
PROT_FILL.
* If there is any error do not allow posting
 DATA: gt_errtab TYPE TABLE OF mrm_errprot,
 gs_errtab TYPE mrm_errprot.
 CONSTANTS: c_errprot(23) TYPE c VALUE '(SAPLMRMF)TAB_ERRPROT[]'.
 FIELD-SYMBOLS: <fs_errprotj_dt> TYPE table.
 ASSIGN (c_errprot) TO <fs_errprotj_dt>.
 REFRESH gt_errtab[].
 gt_errtab[] = <fs_errprotj_dt>[].
 IF NOT gt_errtab[] IS INITIAL.
 READ TABLE gt_errtab INTO gs_errtab WITH KEY msgty = 'E'.
 IF sy-subrc = 0.
 DATA: c_okqx(17) TYPE c VALUE '(SAPLMR1M)OK-CODE'.
 FIELD-SYMBOLS: <fs_okqx> TYPE ANY.
 ASSIGN (c_okqx) TO <fs_okqx>.
 CASE <fs_okqx>.
 WHEN 'BU'. "POST
* This is optional: you can either search for a particular message or
* do not allow any error message
* Here search for the message triggered in badi INVOICE UPDATE
 READ TABLE gt_errtab INTO gs_errtab WITH KEY msgty = 'E'
 msgid = 'ZXX' msgno = '030'.
 IF sy-subrc = 0.
 CLEAR <fs_okqx>.
 MESSAGE s030(zxx). "While errors exist document will not be posted
 ENDIF.
 ENDCASE.
 ENDIF.
 ENDIF.
This is used to give error message in case before posting the document.
KR Jaideep,

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 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 CN22

Hi All
Can anyone tell me an user exit or badi for Tcode CN22 which gets triggered when i save a network.
whenever i make changes in the WBS assignment of the network in the activity level then the i need to copy dates to other networks whenever a change in WBS element is done. Please treat this as pretty urgent
Thanks
Sowjanya

Hello,
Please check and see if the BADI
"AFABD_CHANGE" suits your requirement
it has
AFABD
Network: Dialog table for AFA
as a changable parameter....
and import parameter as
CAUFVD
Dialog Structure for Order Headers and Items
Reward if helpful
Regards
Byju

User exit or BADI for ME22N

Hi,
I need a user exit or Badi for defaulting Plant at line item level.
The scenario goes like this: when ever user tries to change an existing Purchase order and tries to add a new line item in it, I need to trigger USEREXIT or BADI , so that it reads the previous line Plant and updates the current line with the same plant.
I tried with user exit MM06E005 but it didnt seem to work.
Can any one please help me?
I am new to BADI, so I am not sure how to find the BADI and use it. It would be great if anyone can help me i this.
Thanks
Ramya

Hello
The BAdI ME_PROCESS_PO_CUST is the right one. The method PROCESS_ITEM should be triggered whenever the user changes something in the purchase order at item level and executes any kind of function (e.g. ENTER, CHECK or SAVE).
However, instead of overwriting the user input via the BAdI you should implement method CHECK ( Closing Check ) where you can validate the user input. If any of your validation fails you can send an error message and set CHANGING parameter CH_FAILED = 'X'. This approach is much more transparent for the user.
NOTE: In order to "send" an error message you need to add the include mm_messages_mac to your implementing class. For an example see class CL_EXM_IM_ME_PROCESS_PO_CUST (should be available on ERP 6.0):
METHOD if_ex_me_process_po_cust~process_item .
DATA: ls_mepoitem TYPE mepoitem,
        ls_customer TYPE mepo_badi_exampl,
        ls_tbsg     TYPE tbsg.
INCLUDE mm_messages_mac. "useful macros for message handling
* here we check customers data
ls_mepoitem = im_item->get_data( ).
IF ls_mepoitem-loekz EQ 'D'.
* check field badi_afnam
    IF ls_customer-badi_afnam IS INITIAL.
      mmpur_metafield mmmfd_cust_02.
      mmpur_message_forced 'W' 'ME' '083' text-003 '' '' ''.
    ENDIF.
ENDIF.
ENDMETHOD.                    "IF_EX_ME_PROCESS_PO_CUST~PROCESS_ITEM
Regards
Uwe

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 COR1/COR2

Dear Experts,
Can you please tell me if we have any user-exit or BADI for chaning the value of the technical completion date field
i.e. AUFK-IDAT2 while saving the Process Order in COR1 or COR2?
Thanks,
Praveen

Hi Praveen,
Implement the customer exit EXIT_SAPLCOKO_006 in enhancement
PPCO0020 Process order: Display/change order header data
This is only importing one field I_AUFNR.
but try the logic below.
data: lv_fnam type char16 value '(SAPLCOKO)caufvd'.
field-symbols : <fs_caufvd> type caufvd.
your checks for changing the field IDAT2 (Technical completion date).
Try to change <fs_caufvd>-IDAT2 field value.
Regards,
Dwarakanath.S

User Exit or BADI for ml81n - Service Entry Sheet

Similar Messages

Maybe you are looking for