User exit or BADI for determining the output type inme21n orme22n

hi all,
i have used the user exit 'exit_sapmm06e_012', it is getting triggered in me22n, i am able to check whether the vendor email id is present or not, but this is happening all the time that is even when the user dont want to send a email to the vendor i.e. he just wants to print the purchase order, even at that time this user exit is getting triggered and giving a message that the vendor email id is not maintained.
the reson why this is happening is there is no import parameter to this user exit which gives the "medium of data transfer" the user has entered. if i get this parameter visible inside the user exit, then i can check this parameter inside the user exit and do the required operation. i checked up with all the user exits in "me" package and even the other related packages but none of them is getting triggered,
do antone know a user exit or badi which imports this parameter and also gets triggered at the time of creation of purchase order.
plz give me a solution.
regards,
santosh.

Hi Santosh,
Why not continue the other post ?
Anyway, i am not sure to understand your requirement.
Do you want to check that vendor email exist and issue a message only if email is not available ?
Kind regards,
Yann

Similar Messages

User Exit or BADI for catch the document number after saving the document

Hi ,
I am working on data conversion where Document number(BELNR),BKPF and BSEG data should
transfer to my Z table(Containes fileds of BKPF and BSEG) after SAVE the document related to
Tcodes F-01 , F-22 , F-28 , F-43 , FB01 , FB02, FB60 ) . It need to go through by any user-exit or
BADI.So Could you please suggest me any User exit or BADI ASAP.
Waiting for reply.
Thanks
Lakshmi

You should use BTE (Business transaction event). This concept is used especially for FI related enhancements...
Study this document to know how to use BTE
http://www.todoabap.com.ar/archives/FI%20Enhancement%20Technique%20-%20How-To-Guide%20on%20the%20Usage%20of%20Business%20Transaction%20Events%20(BTE).pdf
Let me know if you face any specific issues..

User exit or Badi for changing the lead time in ATP check in VA01/VA02

Hi All,
Currently, SAP standard functionality takes up the lead times maintained in material master to create the schedule lines in the sales order in VA01. I am looking for some user exiit/Badi/Enhancement point where I can change the lead time. This is somewhat urgent so any help in this regard is appreciated.
Regards,
Sandeep
Edited by: Sandeep Gaitonde on Sep 1, 2011 9:16 PM

Hi Sandeep,
These are the user exits will trigger in va01 .
SDTRM001 Reschedule schedule lines without a new ATP check
V45A0001 Determine alternative materials for product selection
V45A0002 Predefine sold-to party in sales document
V45A0003 Collector for customer function modulpool MV45A
V45A0004 Copy packing proposal
V45E0001 Update the purchase order from the sales order
V45E0002 Data transfer in procurement elements (PRreq., assembly)
V45L0001 SD component supplier processing (customer enhancements)
V45P0001 SD customer function for cross-company code sales
V45S0001 Update sales document from configuration
V45S0003 MRP-relevance for incomplete configuration
V45S0004 Effectivity type in sales order
V45W0001 SD Service Management: Forward Contract Data to Item
V46H0001 SD Customer functions for resource-related billing
V60F0001 SD Billing plan (customer enhancement) diff. to billing plan
Please check this and post .
Regards,
Madhu.

User exit or badi for saving the data in mm01

Hi All,
I added one custom screen in mm01 using SPRO ,as well as i added 2 new fields in makt table using Append statement, now the problem is am not able to save the custom screen data in standard makt table can any one help me in this ,tell me which Badi or Exit is useful for this requirement.
Thanks,
Priyanka
Edited by: priyankanukala on Feb 21, 2012 7:55 AM
Edited by: priyankanukala on Feb 21, 2012 8:01 AM
Edited by: priyankanukala on Feb 21, 2012 8:04 AM

Hi
You don't need them. See Note 44410 - Integrating cust.-specific fields in matl master for further information, and copy the code for PAI event in your custom dynpro. You need something similar to this:
process after input.
*coding......
chain.
    field: mara-zzfield1,
           mara-zzfield2.
    module checks_on_zz on chain-request.
endchain.
* coding .......
I hope this helps you
Regards
Eduardo
Edited by: E_Hinojosa on Feb 21, 2012 9:26 AM

EXIT/BADI for enhancing the output of the transaction S_ALR_87013532

Hi,
greetings to all!! I have a problem here guys-I need to find any exit or badi for enhancing the output of the tcode S_ALR_87013532.This tcode is used for seeing the planned/actual/variance of project cost.
In the output we have got 3 columns-total of years, previous years and 2009. Under each column we have Plan, Actual, Variance and VAR %. Our requirement is to show Functional Location(PRPS-TPLNR), Budget Number(TCN01-SWRT0), SBU (TCN01-SWRT1) and Region (TCN01-SWRT2) in each of the clolumns-you can also get the last 3 fields in PRPS table as USR00, USR01 and USR02.
Can anyone help please?could not find anything worthwhile on SDN. Thnx a lot !

Hi,
Check these User-Exits..
Exit name Short text
KAHFEX01 Selection data for commercial reporting in PS
KAP10001 PS: Hierarchy Reports for Projects
KAP60001 PS: Export Project Key Figures into R/3 EIS
Also check the BADI
WBS_USER_FIELDS_F4
Regards
Raghu
Edited by: Raghavendra Rao G on Sep 2, 2009 12:26 PM

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 Framework Release PO

Anyone could tell me about any user exit or BADI for storing the calculated value in Frameork order.
Since it is storing the GNETW in CEKKO and that is used in releasing procedure.
First of all i want to calculate the total price according to srat date and end date and then only for framework order put that value in CEKKO-KTWRT field.
Please Help and suggest some thing about this.
Thanks & Regards,
Nitin Malhotra

Hi,
Check the following PDF .
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/9cd334f3-0a01-0010-d884-f56120039915
May be useful to you.
Regards
Sachin

How to find the list of USER-EXITS or BADI for the transaction ABSO

Hi all,
Please help me to find the list of USER-EXITS or BADI for the transaction ABSO & find the exact user-exit which meets the requirement.
Thanks & Regards,
gyanaraj

Hi,
Copy the problem in SE38 and Execute it
Enter the Tcode u want
this will the list of Userexits and badis
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.

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 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-exit or BADI for F-51

Dear All,
My client needs bkpf-xref1_hd(Reference Key 1 Internal for Document Header) in F-51,as a input field in initial screen.
I have tried each following BADI and user-exits, but that is of no use.
exits
F050S001
F050S002
F050S003
F050S004
F050S005
F050S006
F050S007
F180A001
FARC0002
FEDI0001
RFAVIS01
RFEPOS00
RFKORIEX
SAPLF051
BADI
AC_QUANTITY_GET
AC_QUANTITY_GET
BADI_ENJ_ALT_ADR
BADI_ENJ_ALT_ADR
BADI_F040_SCREEN_600
BADI_FDCB_SUBBAS01
BADI_FDCB_SUBBAS02
BADI_FDCB_SUBBAS03
BADI_FDCB_SUBBAS04
BADI_FDCB_SUBBAS05
BADI_MIRO_SPLT_ADD
BADI_PRKNG_NO_UPDATE
F050S008
FBAS_CIN_LTAX1F02
FBAS_CIN_MF05AFA0
FI_AUTHORITY_ITEM
FI_DOC_DISP_LI
FI_GET_INV_PYMT_AMT
FI_HEADER_SUB_1300
FI_PAYREF_BADI_010
FI_TRANS_DATE_DERIVE
INVOIC_FI_INBOUND
RFESR000_BADI_001
Pls help.
<Priority normalized by moderator>
Thanks in advance.
Raj Patel
Edited by: Vinod Kumar on Jul 26, 2011 11:00 AM

Hi Check any one of the below badi which suits your requirement.
Business Add-in
FI_AUTHORITY_ITEM Extended Authorization Check for Document Display (FB03)
FI_GET_INV_PYMT_AMT BAdI for Determining the Payment Amount for an Invoice
BADI_DRB_CONV_AWREF DRB: Additional AWTYPE to BORIDENT conversions
BADI_DRB_CONV_BORID DRB: Additional Conversions of BORIDENT to AWTYP
FI_PAYREF_BADI_010 BAdI: Payment Reference Number
FI_TRANS_DATE_DERIVE Derive BKPF-WWERT from Other Document Header Data
FBAS_CIN_MF05AFA0 EWT - Downpayment Clearing - Tax transfer for CIN
FBAS_CIN_LTAX1F02 Tax interface
AC_QUANTITY_GET Transfer of Quantities to Accounting - Customer Exit
Regards
Abhii

User Exits or BADI for RMWB

Hello Experts,
I want to put a check on material code while forming the composition for recipe in transaction RMWB. I am entering the material uner the input and output tab. Can anyone please tell the available user exits or BADI for this. I checked few, however, the material no. is not getting captured.
Thanks in advance.
Regards,
Sonal

Hello Sonal,
You can make use of field symbol to read the value of a variable in BADI.Press F1 on field and read the program name and screen field name of a variable and the use below things in the BADI code.
Field-symbol <fs> type any.
ASSIGN ('(program name)variable name') TO <fs>.
IF sy-subrc EQ 0 AND <fs> IS ASSIGNED.
..you will get the variable value here in <fs>
ENDIF.
Thanks,
Pawan

User-exit or BADI for transaction MRRL to modify FI

Hello,
I need to find user-exit or BADI to modify the exchange rate when we execute MRRL transaction.
I already try user-exit MRMH0001 (Logistics Invoice Verification: ERS procedure), but it didn't work.
Thanks for any help.
regards
Zbigniew

Following are the available suer exits provided by SAP. Try if any of these helps -
Exit Name           Description
LMR1M001            User exits in Logistics Invoice Verification
LMR1M002            Account grouping for GR/IR account maintenance
LMR1M003            Number assignment in Logistics Invoice Verification
LMR1M004            Logistics Invoice Verification: item text for follow-on docs
MRMH0001            Logistics Invoice Verification: ERS procedure
MRMH0002            Logistics Invoice Verification: EDI inbound
MRMH0003            Logistics Invoice Verification: Revaluation/RAP
MRMN0001            Message output and creation: Logistics Invoice Verification

User Exit or Badi for F-47

Hi,
I want to validate PO net value with down payment amount for t-code F-47.
Pl help me to find proper user exit or BADI.
Thanks.

Hi Check any one of the below badi which suits your requirement.
Business Add-in
FI_AUTHORITY_ITEM                       Extended Authorization Check for Document Display (FB03)
FI_GET_INV_PYMT_AMT                     BAdI for Determining the Payment Amount for an Invoice
BADI_DRB_CONV_AWREF                     DRB: Additional AWTYPE to BORIDENT conversions
BADI_DRB_CONV_BORID                     DRB: Additional Conversions of BORIDENT to AWTYP
FI_PAYREF_BADI_010                      BAdI: Payment Reference Number
FI_TRANS_DATE_DERIVE                    Derive BKPF-WWERT from Other Document Header Data
FBAS_CIN_MF05AFA0                       EWT - Downpayment Clearing - Tax transfer for CIN
FBAS_CIN_LTAX1F02                       Tax interface
AC_QUANTITY_GET                         Transfer of Quantities to Accounting - Customer Exit
Regards
Abhii

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 determining the output type inme21n orme22n

Similar Messages

Maybe you are looking for