BADI for RF Queue Determination

Dear all,
I am playing with the RF Queue Determination BADI and I woul like to share my thoughts with you.
I am considering using the RF Queue BADI for something else than Queue Determination:
IF Queue is XXX, AND the Two Step Confirmation status is yellow (ls_TAP-PVQUI = 'x'), then I want to CLEAR the current document number as shown in Transaction LRFMD.
So, rather than determining a Queue, I want to perform a CLEAR.
Will it let me use this BADI for this purpose? Am still strugling the term after CLEAR
IF ls_tap-queue = 'KLEXP-05'
    AND ls_TAP-PVQUI = 'X'.
      clear LRF_WKQU-DOCNUM.
      ENDIF.
Thank you for your time,
Best regards,
Nick

Nick,
As fas as I know this badi is used during TO creation. At that time no document number is assigned to a RF user.
I wouldn't advise clearing from this badi enhancement. It is not ment to be used for this purpose.
Regards.
Ronald

Similar Messages

BADI For Inbound Queue in CRM

Hi All,
I am replicating Product Listings (VB02 in ECC) data from ECC to CRM.
Now I need to Update a Z table in CRM System with the data coming from ECC when the Inbound Queue in CRM System is processed via SMQ2.
Can Anybody please tell me what BADI will be useful
I found one CRM_DATAEXCHG_BADI but not sure how it goes.
I also tried in Debuging the inbound Queue. It will take Long time to find out BTE or BADI in this way.
So please help me with the BADI or BTE Name.
Thanks
Venkat

Hi Gautham,
No good, It did not help me Gautham.
Can you please suggest me some other way of dong it.
I have 2 badis to use one is address_update and the other is addres_check.
I implemented address_check which had a address structure as a changing parameter and I update it there, it works absolutely fine.
But my requirement is to update the structure based on the condition of BUT000. That is the BUT000-type, which means I need to update the structure only for person and not for organization and group.
so in the badi address_check i need the BUT000 details, which I am not able to trace even from the local memory as I am getting the error saying "Memory is not yet instantiated"
and If i use the other badi address_update.
I have the problem the other way round here. I have all the BUT000 details here I can put the condition to update only for person, but I am not able to update the address structure.
Please help me. This is required very urgent.
Maximum points will be rewarded.
Thanks in advance.
Arul.

BADI for storage location restriction in IW32

Dear All,
I am working on one scenario in this user has to get the error message :-
1. Whenever he doesn't enter the Storage Location in Component Tab (in IW32) and also he should not be able to save the Maintenance Order.
2. There is ZTABLE (ZTPM058) , if there is no entry of the Storage location in the ZTABLE then also he should get the error.
I have used the BADI BADI_DI_PCS2_1 to do this but the problem is when the user enter the component manually then it works fine , but when he selects the component from List button (it is in the bottom of the component tab screen) , then this BADI doesn't work correctly.
Basically when the user selects component from List then it should first put data into the component tab and then give the error . but this is not happening.
Please suggest what can be done.
Below is the code that I have written :-
l_ucomm = sy-ucomm.
if diad_resbd-MENGE is not INITIAL.
SELECT SINGLE ingpr "Plant Section
 lgort "Storage Location
 INTO (l_ingpr,
 l_lgort)
 FROM ztpm058
 WHERE lgort = diad_resbd-lgort
 AND ingpr = diad_caufvd-ingpr.
IF sy-subrc <> 0.
if l_ucomm <> 'IMKL'.
 CONCATENATE 'FOR ITEM NO' diad_resbd-posnr
 ', COMPONENT' diad_resbd-matnr
 'AND PLANNER GROUP' diad_caufvd-ingpr
 'THERE IS NO STORAGE LOCATION' diad_resbd-lgort INTO txtmgs SEPARATED BY space.
 clear l_ucomm.
 clear sy-ucomm.
 MESSAGE txtmgs TYPE 'E' .
 elseif l_ucomm = 'IMKL'. (OK CODE when user press List button)
 CONCATENATE 'FOR ITEM NO' diad_resbd-posnr
 ', COMPONENT' diad_resbd-matnr
 'AND PLANNER GROUP' diad_caufvd-ingpr
 'THERE IS NO STORAGE LOCATION' diad_resbd-lgort
INTO txtmgs SEPARATED BY space.
 clear l_ucomm.
 clear sy-ucomm.
 MESSAGE txtmgs TYPE 'W' .
 endif.
 endif.
 ELSE.
 message 'Please enter the Quantity' type 'W'.
 clear l_ucomm.
 clear sy-ucomm.
 endif.
Thanks and Regards,
Rachit Khanna

Dear Rajesh Kumar Raju
Go to IMG-->Logistics Execution >Shipping> Picking -->Determine Picking Location -->Define Rules for Picking Location Determination. There you have to assign the MALA rule to your delivery type
Also maintain in OMJ8 and in material master under MRP2 view the default storage location in the field "Prod. stor. location"
thanks
G. Lakshmipathi

User exit / BADI for training and event management

Hi all,
Can anybody tell me if there is any user exit / BADI for training and event management module?
Thanks & regards,
LOI

Hi
BADI's for Training and Event Management
HRTEM00MASTERDATA      HR: Training and Event Management - Master Data
HRTEM00NET_ACTIVITY      Determine Activities of an Attendee (e.g. ESS PV8I)
HRTEM00NET_WEBST      Set Cancellation Reason in ESS PV8I
HRTEM_CORR_NOTIF_REQ      Customer Enhancement:Confirmation on Send (R/3 Mail, E-Mail)
HRTEM_HANDLE_BOOKING      HR-TEM BAdI: Employee Leaves Company - Update TEM Data
HRTEM_INT_ZW           HR-TEM: Badi for Integration TEM - Time Management
HRTEM_READ_OBJECT      Customer Enhancement: Name Format
RHPV0001 Customer      Enhancement for Additional Checks for Booking
Enhancemnet Spot:
HRTEM00MASTERDATA      HR: Training and Event Management - Master Data
~~~Ganesh Kumar K.

Project settlement to CO-PA and BAdI for automatic creation of rules

Hello SAP experts!
I have managed to implement settlement rule strategy to CO-PA for sales project WBS-elements, which automatically creates the settlement rules for WBS-elements with billing indicator. One or more sales order items are assigned to the WBS-elements. When the system derives settlement rules, it generates profitability segments that contain the characteristic values of the WBS elements and the sales orders assigned to them. The problem is, that only one single settlement receiver is determined for each WBS-element. And if more that one sales order item is assigned to the same WBS-element only those characteristics are copied to the settlement rule that are same in all sales order items.
For example; it products are different in all sales order items, the automatically created settlement rule does not contain the characteristic value product or neighter other caracteristics derived from product.
Do You have experience of using BAdI for influencing the generation of settlement rules? What it actually makes possible?
Br, Nina

Dear Waman,
thank you for your reply !
Yet - this still does not solve our problem. In that note (and also in the related note 201445) there is no valuable information included concerning transaction currency:
Our WBS elements (and also other cost objects, e.g. sales order items) are being debited in all of the three currencies.....but the credit (during settlement) only takes place in two of them: object and CO area currency.
I really appreciate additional help on this. It would be hard to believe that we are the only SAP customer having this kind of problem.
Best regards,
Thomas

BADI for Address Check in PA30 in ECC6.0

Hi Friends,
Is there any BADI for Address Check in PA30 in ECC6.0 similar to what we have in BP transaction in ECC6.0.
Thanks,
Pradeep

check these...
Enhancement/ Business Add-in            Description
Enhancement
PBASRP01                                PA: User exit distributed reporting
PBAS0002                                PA: Enhancements for Personnel Administration - Menu
PBAS0001                                PA: Pers.Admin./Recruitment: Default values and checks
PARA0002                                Enhancement for Calculating Annual Salary; IT0008,14,15
PARA0001                                Enhancement for Determining the Number of Periods
HRRPAI01                                User exit for FB HR_ENTRY_DATE and HR_LEAVING_DATE
HRPC0001                                HR: PC download authorization
HRPBAS01                                User Exit for HR Master Data
Business Add-in
HRPAD00_PREM                            Definition of User Exit for Collective Search Help PREM
HRPAD00_RECOG_SCREEN                    Employee Recognition Screen
HRPADUS_PBAS_0001                       Customer Exit for Message handling
HRPAD_SUBTY_CHECK                       HR: Master Data, Subtype Check
HR_F4_GET_SUBTYPE                       HR: Entry help for subtypes
HR_FAST_ACTION_CHECK                    Check fields on the fast entry screen
HR_INDVAL                               HR: Indirect wage type valuation
HR_SET_PKGAB
HRPAYXX_DELETE_PERNR                    BAdI for Reports Deleting Personnel Numbers
HRPAD00_PAPM                            Definition of User Exit for Collective Search Help PAPM
HRPAD00_GET_AF_0008                     Additional Fields for Basic Pay Infotype (0008)
HRPAD00_ENTRY_LEAVE                     HR_ENTRY_DATE and HR_LEAVING_DATE
HRPAD00_ADRS                            HR: Address formatting
HRPAD00MGEACTIVATION                    Activation Action BAdI for Global Employees
HRPAD00INFTY                            Update / Infotype maintenance
HRPAD00AUTH_TIME                        Time Logic in the PA Authorization Check
HRPAD00AUTH_RECORD                      Spanish Data Privacy Law: Exit for Recording
HRPAD00AUTH_CHECK                       HR: Authorization Check
HRIV_REDUCE_AMOUNT                      Reduction within Indirect Valuation
No.of Exits:          8
No.of BADis:         19

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

EXIT or BADI for Post Goods Issue

Hello Experts,
I need help in finding a USER EXIT, or BADI to change the contents of MSEG at PGI moment in VL02N.
I'm using version 4.6c.
When I click at Post Goods Issue, I need to insert the customer number at MSEG for certain documents that the standard does not use this field.
Can anyone PLEASE help?
Will reward points!
Thanks a lot and regards,
Fernanda

Hi
Enhancement/ Business Add-in            Description
Enhancement
V02V0004
User Exit for Staging Area Determination (Item)
V02V0003
User exit for gate + artl staging area determination (headr)
V02V0002
User exit for storage location determination
V02V0001
Sales area determination for stock transport order
VMDE0004
Shipping Interface: Message SDPACK (Packing, Inbound)
VMDE0003
Shipping Interface: Message SDPICK (Picking, Inbound)
VMDE0002
Shipping Interface: Message PICKSD (Picking, Outbound)
VMDE0001
Shipping Interface: Error Handling - Inbound IDoc
V53W0001
User exits for creating picking waves
V53C0002
W&S: RWE enhancement - shipping material type/time slot
V53C0001
Rough workload calculation in time per item
V50S0001
User Exits for Delivery Processing
V50R0004
Calculation of Stock for POs for Shipping Due Date List
V50R0002
Collective processing for delivery creation
V50R0001
Collective processing for delivery creation
V50Q0001
Delivery Monitor: User Exits for Filling Display Fields
V50PSTAT
Delivery: Item Status Calculation
Business Add-in
DELIVERY_PUBLISH
Announcement of delivery data during database update
If it is helpful rewards points
Regards
Pratap.M

User exit/BADI for Return PO item delivery Address

Hi Guyz,
We have a requirement where in when a PO item is marked as return PO item(In ME21n/ME22n/ME23n We have check box at item level) and click on enter/Check/Save, In delivery address of item details we have to populate Vendor address. By default SAP populates Plant address. If we manually give Vendor number in item details=>Delivery address tab then it populates vendor address. We want to automate this functionality.
Is there any Exit/BADI which serve this purpose.
Note: We need this functionality for few doc types(i.e PO doc type should also be available in the exit).
Any ideas could be really helpfull.
Thanks,
Vinod.

Hi,
there are some user-exit & enhancements....
MEQUERY1                                Enhancement to Document Overview ME21N/ME51N
MEVME001                                WE default quantity calc. and over/ underdelivery tolerance
MM06E001                                User exits for EDI inbound and outbound purchasing documents
MM06E003                                Number range and document number
MM06E004                                Control import data screens in purchase order
MM06E005                                Customer fields in purchasing document
MM06E007                                Change document for requisitions upon conversion into PO
MM06E008                                Monitoring of contr. target value in case of release orders
MM06E009                                Relevant texts for "Texts exist" indicator
MM06E010                                Field selection for vendor address
MMAL0001                                ALE source list distribution: Outbound processing
MMAL0002                                ALE source list distribution: Inbound processing
MMAL0003                                ALE purcasing info record distribution: Outbound processing
MMAL0004                                ALE purchasing info record distribution: Inbound processing
MMDA0001                                Default delivery addresses
MMFAB001                                User exit for generation of release order
MRFLB001                                Control Items for Contract Release Order
MELAB001                                Gen. forecast delivery schedules: Transfer schedule implem.
AMPL0001                                User subscreen for additional data on AMPL
LMEDR001                                Enhancements to print program
LMELA002                                Adopt batch no. from shipping notification when posting a GR
LMELA010                                Inbound shipping notification: Transfer item data from IDOC
LMEQR001                                User exit for source determination
LMEXF001                                Conditions in Purchasing Documents Without Invoice Receipt
LWSUS001                                Customer-Specific Source Determination in Retail
M06B0001                                Role determination for purchase requisition release
M06B0002                                Changes to comm. structure for purchase requisition release
MEFLD004                                Determine earliest delivery date f. check w. GR (only PO)
MEETA001                                Define schedule line type (backlog, immed. req., preview)
ME590001                                Grouping of requsitions for PO split in ME59
M06E0005                                Role determination for release of purchasing documents
M06E0004                                Changes to communication structure for release purch. doc.
M06B0005                                Changes to comm. structure for overall release of requisn.
M06B0004                                Number range and document number
M06B0003                                Number range and document number
Some BADI s:
ME_PROCESS_PO                           Enhancements for Processing Enjoy Purchase Order: Intern.
ME_PROCESS_COMP                         Processing of Component Default Data at Time of GR: Customer
ME_PO_SC_SRV                            BAdI: Service Tab Page for Subcontracting
ME_PO_PRICING_CUST                      Enhancements to Price Determination: Customer
ME_PO_PRICING                           Enhancements to Price Determination: Internal
ME_INFOREC_SEND                         Capture/Send Purchase Info Record Changes - Internal Use
ME_HOLD_PO                              Hold Enjoy Purchase Orders: Activation/Deactivation
ME_GUI_PO_CUST                          Customer's Own Screens in Enjoy Purchase Order
ME_FIELDSTATUS_STOCK                    FM Account Assignment Behavior for Stock PR/PO
ME_DP_CLEARING                          Clearing (Offsetting) of Down Payments and Payment Requests
ME_DEFINE_CALCTYPE                      Control of Pricing Type: Additional Fields
ME_COMMTMNT_REQ_RE_C                    Check of Commitment Relevance of Purchase Requisitions
ME_COMMTMNT_REQ_RELE                    Check of Commitment Relevance of Purchase Requisitions
ME_PROCESS_PO_CUST                      Enhancements for Processing Enjoy Purchase Order: Customer
SMOD_MRFLB001                           Control Items for Contract Release Order
MM_EDI_DESADV_IN                        Supplementation of Delivery Interface from Purchase Order
MM_DELIVERY_ADDR_SAP                    Determination of Delivery Address
ME_WRF_STD_DNG                          PO Controlling Reminder: Extension to Standard Reminder
ME_TRIGGER_ATP                          Triggers New ATP for Changes in EKKO, EKPO, EKPV
ME_TRF_RULE_CUST_OFF                    BADI for Deactivation of Field T161V-REVFE
ME_TAX_FROM_ADDRESS                     Tax jurisdiction code taken from address
ME_REQ_POSTED                           Purchase Requisition Posted
ME_REQ_OI_EXT                           Commitment Update in the Case of External Requisitions
ME_RELEASE_CREATE                       BAdI: Release Creation for Sched.Agrmts with Release Docu.
ME_PURCHDOC_POSTED                      Purchasing Document Posted
ME_PROCESS_REQ_CUST                     Enhancements for Processing Enjoy PReqs: Customer
ME_PROCESS_REQ                          Enhancements for Processing Enjoy PReqs: Internal
ME_COMMTMNT_PO_REL_C                    Check for Commitment-Relevance of Purchase Orders
ME_CCP_BESWK_AUTH_CH                    BAdI for authorization checks for procuring plant
ME_CCP_ACTIVE_CHECK                     BAdI to check whether CCP process is active
ME_BSART_DET                            Change document type for automatically generated POs
ME_BAPI_PR_CREATE_02
ME_BAPI_PR_CREATE_01
ME_BAPI_PO_CREATE_02
ME_BAPI_PO_CREATE_01
ME_BADI_DISPLAY_DOC                     BAdI for Internal Control of Transaction to be Invoked
ME_ACTV_CANCEL_PO                       BAdI for Activating the Cancel Function at Header Level
MEGUI_LAYOUT                            BAdI for Enjoy Purchasing GUI
EXTENSION_US_TAXES                      Extended Tax Calculation with Additional Data
ARC_MM_EKKO_WRITE                       BAdI: Enhancement of Scope of Archiving (MM_EKKO)
ARC_MM_EKKO_CHECK                       BAdI: Enhancement of Archivability Check (MM_EKKO)
ME_CCP_DEL_DURATION                     Calc. of Delivery Duration in CCP Process (Not in Standard)
ME_COMMTMNT_PO_RELEV                    Check for Commitment-Relevance of Purchase Orders
ME_COMMITMENT_STO_CH                    BadI for checking if commitments for STOs are active
ME_COMMITMENT_RETURN                    Commitment for return item
ME_CIP_REF_CHAR                         Enables Reference Characteristics in Purchasing
ME_CIP_ALLOW_CHANGE                     Configuration in Purchasing: Changeability Control
ME_CIN_MM06EFKO                         Copy PO data for use by Country version India
ME_CIN_LEINRF2V                         BADI for LEINRF03 excise_invoice_details
ME_CIN_LEINRF2R                         BADI for CIN India - Delivery charges
ME_CHECK_SOURCES                        Additional Checks in Source Determination/Checking
ME_CHECK_OA                             Check BAdI for Contracts
ME_CHECK_ALL_ITEMS                      Run Through Items Again in the Event of Changes in EKKO
ME_CHANGE_OUTTAB                        Enrich ALV Output Table in Purchasing
ME_CHANGE_CHARACTER                     Customer-Specific Characteristics for Product Allocation
No.of Exits:         35
No.of BADis:         55
Arunima

BADI for changing product catgory

Hello SRM Experts,
I am looking for an BADI for changing product category.
We use classic scenario with an external catalog. Our supplier delievers us some data. Some of this data are used for statitical reason for example new item matgroup from oci interface.
now I want to determine the product categorie in relation to the delivered new item matgroup.
I have found some BADI to manipulate the Data - but not possible for product category. Thank your for help
Regards Uwe

Hello Yann,
I have activated this BADI already. But I have not managed it to change product category.
Which field of this BADI has to be changed ?
Where do I get the GUID from ?
thank you

User exit/BADI for tracing change of User Status in IW22

Hello,
I am looking for a user exit or BADI that triggers whenever ther's a change made to User status field.
eg. changing user status to APTC(Approved to be executed)
I then need the exit/badi to trigger my workflow to send mails to list of reviewers. I can handle that but I am not able to find the suitable exit.
I have seen BADI IQS0_STATUS_MAINTAIN, but no use.
Can anyone help?

Hi..
Transaction Code - IW22                     Change PM Notification
Enhancement/ Business Add-in            Description
Enhancement
IWO10026                                User check on setting status 'Do not perform'
IWO10027                                User exit: Generate user-defined settlement rule
IWOC0001                                Create PM/SM notification: Determine reference object
IWOC0002                                PM/SM notification: Check whether status change is allowed
IWOC0003                                PM/SM authorization check of ref. object and planner group
IWOC0004                                Change single-level list editing PM/QM/SM ALV settings
Business Add-in
WOC_FL_DETERMINE                        Determine Date for Determining Installation Loc. Equi.
NOTIF_AUTHORITY_01                      Additional Authorization Checks for the Notification
IWOC_OBJECTINFO_CHNG                    Changes to Data of Object Info Screen
IWOC_LIST_TUNING                        Performance Tuning for Lists in PM/CS
IWO1_SUBSCREEN_0170                     Display Additional Data on Object Screen 0170 PhysicalSample
IQS_MASS_CHANGE                         BadI for Mass Changes to Notifications
IQS0_STATUS_MAINTAIN                    Control of Changeability of User Status
No.of Exits:          6
No.of BADis:          7
Arunima

User Exit/ BADI for ME01- Sourcelist creation

Hiii
We need a place exit/ BADi to do vendor validation before saving soource list in transaction ME01.
Please provide suitable exit / badi for above requirement.
Thanks ...in advance.!!
Regards,
Nilesh

EXIT_SAPLMBMP_003     AMPL0001     User subscreen for additional data on AMPL
EXIT_SAPLMEKO_001     LMEKO001     Extend communications structure KOMK for pricing
EXIT_SAPLMEKO_002     LMEKO002     Extend communications structure KOMP for pricing
EXIT_SAPLMEQR_001     LMEQR001     User exit for source determination
EXIT_SAPLMEQR_001     LMEQR001     User exit for source determination
EXIT_SAPLQBCK_002     QBCK0002     Extended check in procurement

User exit of\r badi for co11

Dear Gurus,
i need a user exit or badi for transcation co11 after creation of batch .
tx
raj

Hi Raj,
Following are the user exit for co11:
CONF0001            Enhancements in order confirmation
CONFPI01            Process order conf.: Calculate cust.specific default values
CONFPI02            Process order confirmation: Customer spec. input checks 1
CONFPI03            Process order conf.: Cust. spec. check after op. selection
CONFPI04            Process order conf.: Customer specific input checks 2
CONFPI05            Process order conf.: Cust. spec. enhancements when saving
CONFPI06            Process order confirmation: Actual data transfer
CONFPM01            PM/SM order conf.: Determine cust. specific default values
CONFPM02            PM/SM order confirmation: Customer specific input checks 1
CONFPM03            PM/SM order conf.: Cust. spec. check after op. selection
CONFPM04            PM/SM order conf.: Customer specific input check 2
CONFPM05            PM/SM order conf.: Cust. specific enhancements when saving
CONFPP01            PP order conf.: Determine customer specific default values
CONFPP02            PP order conf.: Customer specific input checks 1
CONFPP03            PP order conf.: Cust. specific check after op. selection
CONFPP04            PP order conf.: Customer specific input checks 2
CONFPP05            PP order conf.: Customer specific enhancements when saving
CONFPP06            PP Order Confirmations: Actual Data Transfer
CONFPP07            Single Screen Entry: Inclusion of User-Defined Subscreens
CONFPS01            PS confirmation: Determine customer specific default values
CONFPS02            PS confirmation: Customer specific input checks 1
CONFPS03            PS confirmation: Customer specific check after op. selection
CONFPS04            PS confirmation: Customer specific input checks 2
CONFPS05            PS confirmation: Customer specific enhancements when saving
Hope this will help you...

User Exit/BADI for Purchase Order and Purchase Requisitions

HI,
I have a requireent where i have to check the the user does not enter both Subitems and Over a Limit for a Service Purchase Requisition.
Is there a User Exit or Badi that i can use where this information is availaible.
also i have to check that release strategy is assigned to every purchase order where the version has been completed.
Is there a User Exit or Badi where Information of EREV table is availaible.
Regards,
Tarun Bahal

For Purchachase requisition , the BADIs and USER EXITS are
ME_COMMITMNT_PARKING BAdI for Redefining Commitment Interface When Parking
ME_MEREQ_PARKING BAdI Purchase Requisition: "Hold"
ME_REQ_HEADER_TEXT Copy Header Text: Enjoy Purchase Requisition
try with the above BADI's
MEREQ001 Customers' Own Data in Purchase Requisition
for Purchase order , the BADIs and USER EXITS are
ARC_MM_EKKO_CHECK BAdI: Enhancement of Archivability Check (MM_EKKO)
ARC_MM_EKKO_WRITE BAdI: Enhancement of Scope of Archiving (MM_EKKO)
EXTENSION_US_TAXES Extended Tax Calculation with Additional Data
MEGUI_LAYOUT BAdI for Enjoy Purchasing GUI
ME_ACTV_CANCEL_PO BAdI for Activating the Cancel Function at Header Level
ME_BADI_DISPLAY_DOC BAdI for Internal Control of Transaction to be Invoked
ME_BAPI_PO_CREATE_01
ME_BAPI_PO_CREATE_02
ME_BAPI_PR_CREATE_01
ME_BAPI_PR_CREATE_02
ME_BSART_DET Change document type for automatically generated POs
ME_CCP_ACTIVE_CHECK BAdI to check whether CCP process is active
ME_CCP_BESWK_AUTH_CH BAdI for authorization checks for procuring plant
ME_CCP_DEL_DURATION Calc. of Delivery Duration in CCP Process (Not in Standard)
ME_CHANGE_CHARACTER Customer-Specific Characteristics for Product Allocation
ME_CHANGE_OUTTAB Enrich ALV Output Table in Purchasing
ME_CHECK_ALL_ITEMS Run Through Items Again in the Event of Changes in EKKO
ME_CHECK_OA Check BAdI for Contracts
ME_CHECK_SOURCES Additional Checks in Source Determination/Checking
ME_CIN_LEINRF2R BADI for CIN India - Delivery charges
ME_CIN_LEINRF2V BADI for LEINRF03 excise_invoice_details
ME_CIN_MM06EFKO Copy PO data for use by Country version India
ME_CIP_ALLOW_CHANGE Configuration in Purchasing: Changeability Control
ME_CIP_REF_CHAR Enables Reference Characteristics in Purchasing
ME_COMMITMENT_RETURN Commitment for return item
ME_COMMITMENT_STO_CH BadI for checking if commitments for STOs are active
ME_COMMTMNT_PO_RELEV Check for Commitment-Relevance of Purchase Orders
ME_COMMTMNT_PO_REL_C Check for Commitment-Relevance of Purchase Orders
ME_COMMTMNT_REQ_RELE Check of Commitment Relevance of Purchase Requisitions
ME_COMMTMNT_REQ_RE_C Check of Commitment Relevance of Purchase Requisitions
ME_DEFINE_CALCTYPE Control of Pricing Type: Additional Fields
ME_DP_CLEARING Clearing (Offsetting) of Down Payments and Payment Requests
ME_FIELDSTATUS_STOCK FM Account Assignment Behavior for Stock PR/PO
ME_GUI_PO_CUST Customer's Own Screens in Enjoy Purchase Order
ME_HOLD_PO Hold Enjoy Purchase Orders: Activation/Deactivation
ME_INFOREC_SEND Capture/Send Purchase Info Record Changes - Internal Use
ME_PO_PRICING Enhancements to Price Determination: Internal
ME_PO_PRICING_CUST Enhancements to Price Determination: Customer
ME_PO_SC_SRV BAdI: Service Tab Page for Subcontracting
ME_PROCESS_COMP Processing of Component Default Data at Time of GR: Customer
ME_PROCESS_PO Enhancements for Processing Enjoy Purchase Order: Intern.
ME_PROCESS_PO_CUST Enhancements for Processing Enjoy Purchase Order: Customer
ME_PROCESS_REQ Enhancements for Processing Enjoy PReqs: Internal
ME_PROCESS_REQ_CUST Enhancements for Processing Enjoy PReqs: Customer
ME_PURCHDOC_POSTED Purchasing Document Posted
ME_RELEASE_CREATE BAdI: Release Creation for Sched.Agrmts with Release Docu.
ME_REQ_OI_EXT Commitment Update in the Case of External Requisitions
ME_REQ_POSTED Purchase Requisition Posted
ME_TAX_FROM_ADDRESS Tax jurisdiction code taken from address
ME_TRF_RULE_CUST_OFF BADI for Deactivation of Field T161V-REVFE
ME_TRIGGER_ATP Triggers New ATP for Changes in EKKO, EKPO, EKPV
ME_WRF_STD_DNG PO Controlling Reminder: Extension to Standard Reminder
MM_DELIVERY_ADDR_SAP Determination of Delivery Address
MM_EDI_DESADV_IN Supplementation of Delivery Interface from Purchase Order
SMOD_MRFLB001 Control Items for Contract Release Order
AMPL0001 User subscreen for additional data on AMPL
LMEDR001 Enhancements to print program
LMELA002 Adopt batch no. from shipping notification when posting
LMELA010 Inbound shipping notification: Transfer item data from
LMEQR001 User exit for source determination
LMEXF001 Conditions in Purchasing Documents Without Invoice Rece
LWSUS001 Customer-Specific Source Determination in Retail
M06B0001 Role determination for purchase requisition release
M06B0002 Changes to comm. structure for purchase requisition rel
M06B0003 Number range and document number
M06B0004 Number range and document number
M06B0005 Changes to comm. structure for overall release of requi
M06E0004 Changes to communication structure for release purch. d
M06E0005 Role determination for release of purchasing documents
ME590001 Grouping of requsitions for PO split in ME59
MEETA001 Define schedule line type (backlog, immed. req., previe
MEFLD004 Determine earliest delivery date f. check w. GR (only P
MELAB001 Gen. forecast delivery schedules: Transfer schedule imp
MEQUERY1 Enhancement to Document Overview ME21N/ME51N
MEVME001 WE default quantity calc. and over/ underdelivery toler
MM06E001 User exits for EDI inbound and outbound purchasing docu
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 P
MM06E008 Monitoring of contr. target value in case of release or
MM06E009 Relevant texts for "Texts exist" indicator
MM06E010 Field selection for vendor address
MMAL0001 ALE source list distribution: Outbound processing
MMAL0002 ALE source list distribution: Inbound processing
MMAL0003 ALE purcasing info record distribution: Outbound proces
MMAL0004 ALE purchasing info record distribution: Inbound proces
MMDA0001 Default delivery addresses
MMFAB001 User exit for generation of release order
MRFLB001
Regards,
Anirban

BADI for RF Queue Determination

Similar Messages

Maybe you are looking for