XK01 user exit or BADI in which LIFNR & BUKRS are available .

Hi experts,
Is there any user exit or BADI in which account no of vendor(lfa1-lifnr),company code(lfb1-bukrs)
purchasing organisation(lfm1-ekorg) available.
My requirement is to send a mail with these details when a vendor is created using XK01 transaction.
I tried with exit SAPMF02K and BADI VENDOR_ADD_DATA.But above deatils are not available in this exit since the exit is executed before the LIFNR is assigned.
Is there any solution for this problem???? Pls do reply...

Hi
The following are the BADIs available for XK01
VENDOR_ADD_DATA
VENDOR_ADD_DATA
VENDOR_ADD_DATA_BI
VENDOR_ADD_DATA_BI
VENDOR_ADD_DATA_CS
VENDOR_ADD_DATA_CS
VENDOR_FIELDACTIVE
User exits:
RFKRRANZ
SAPMF02K
If none of these satisfy your needs you can check upon the enhancement spots option if you ARE IN ecc 6.0
Regards,
Soumya.

Similar Messages

Is there any User Exit or BADI- Where LTAP-WDATU is as change parameter ,So during or after Transfer order creation GR date would be as per given logic not as current date

Dear All,
There is a requirement in which when the material (Not batch managed) is getting return from Non WM managed storage location to WM managed storage location than at the time of creating transfer order or after creation of transfer order would like to change LTAP-WDATU (GR date) automatically , So here i am unable to find the right user exit or BADI in which i can write the logic for same. Below is full description of the requirement.
Here we are following Removal strategy "FIFO" while picking the material (Not batch managed) from WM managed storage location (WMS1) & transferring to Non WM managed storage location (ODS) ( than from there it use to go to Production) , at certain times partial quantity use to come back from Non WM managed storage location (ODS) to WM managed storage location (WMS1) and while doing putaway of the same "GR date" use to change which was not the actual when the material 1st time comes to WM managed storage location (WMS1) (before getting transfer to Non WM managed storage location). So here i want the user exit or BADI in which i can write my logic so that GR date ( LTAP-WDATU) would automatically change while creating transfer order or after creation of transfer order as per the "GR date" of same material which last moved from WM managed Storage location (WMS1) to Non WM managed storage location(ODS) because as per FIFO material dated before that would not be exist in the warehouse.
Below is the flow of the material while transferring to production & returning from production.
WMS1 ( WM managed warehouse ) --> ODS ( Non WM managed warehouse) --> Production At the time of issue to production
Production --> ODS ( Non WM managed warehouse) --> WMS1 ( WM managed warehouse ) At the time of return from production
I hope i m clear on my requirement.
Thanks in advance.

1. You have to get a key from SAP to modify the two includes in which the user exits are present.
2. You have to enter statement 'INCLUDE z**. ' in both user exits in the MV45* includes. Then save and activate the MV45** includes.
3. You have to figure out the code that carries out the functionality described in your specifications.
3. Write the code in includes Z** .
4. Now the code written by you will be executed when you run the relevant SD transaction
Message was edited by: Sudhir Bhate

User-Exit of BADI in ME51n T-code

Hi All,
       I need an urgent help. I want to change the line items data of the purchase requisition before it is saved. When we press the SAVE button in the ME51n transaction, I should be able to add total value of the REQUISITION to some non-significant field of each ITEM in the requisition.
       What all I need at this stage is the user-exit or BADI in which I can do this and where I can get the item details that can be changed in that user-exit. I tried all the user-exits in MEREQ001 include but couldnt find where the item details are stored and where to change the data.
     Any inf. on this will be very very helpful.
   Thanks in advance.
   Raja Sekhar.

Hi friend,
Try this ampliation at CMOD:
WCOUP001
Try this BADI:
RDM_PROMOTION_WAK1
Regards,
Welinton Rocha

User Exit or BADI for ME21N

Hi All,
We are in a situation where in we need to Change the Distribution Channel in the Shipping tab of ME21N transaction.
Previously, the distribution channel is being picked up form the config (SPRO - Shipping data for plant) but before it picks up from the config we need to change it and update the other distribution channel in the PO.
We have tried with most of the User exits and BADIs but all of those are of no use for our requirement, as these user exits and badis are triggered after we click on save button. But we need to change the Distribution channel at the point of determination of Shipping data by the system i.e. before save.
Can any one please help me out with this situation with some User exits or BADIs that are triggered before save button.
Note: The Shipping data is in EKPV table. We need to change the VTWEG field in EKPV.
Thanks in Advance,
Asif Ali Khan

Asif,
see these are Exits and BADI for ME21n,
Enhancement/ Business Add-in            Description
Enhancement
MEFLD004                                Determine earliest delivery date f. check w. GR (only PO)
MELAB001                                Gen. forecast delivery schedules: Transfer schedule implem.
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
LMEKO001                                Extend communications structure KOMK for pricing
LMEKO002                                Extend communications structure KOMP for pricing
MM06E011                                Activate PReq Block
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
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
M06B0002                                Changes to comm. structure for purchase requisition release
M06B0001                                Role determination for purchase requisition release
Business Add-in
ME_PROCESS_PO                           Enhancements for Processing Enjoy Purchase Order: Intern.
ME_PROCESS_COMP                         Processing of Component Default Data at Time of GR: Customer
ME_PO_SC_SRV                            BAdI: Service Tab Page for Subcontracting
ME_PO_PRICING_CUST                      Enhancements to Price Determination: Customer
ME_PO_PRICING                           Enhancements to Price Determination: Internal
ME_INFOREC_SEND                         Capture/Send Purchase Info Record Changes - Internal Use
ME_HOLD_PO                              Hold Enjoy Purchase Orders: Activation/Deactivation
ME_GUI_PO_CUST                          Customer's Own Screens in Enjoy Purchase Order
ME_FIELDSTATUS_STOCK                    FM Account Assignment Behavior for Stock PR/PO
ME_DP_CLEARING                          Clearing (Offsetting) of Down Payments and Payment Requests
ME_DEFINE_CALCTYPE                      Control of Pricing Type: Additional Fields
ME_COMMTMNT_REQ_RE_C                    Check of Commitment Relevance of Purchase Requisitions
ME_COMMTMNT_REQ_RELE                    Check of Commitment Relevance of Purchase Requisitions
ME_PROCESS_PO_CUST                      Enhancements for Processing Enjoy Purchase Order: Customer
SMOD_MRFLB001                           Control Items for Contract Release Order
MM_EDI_DESADV_IN                        Supplementation of Delivery Interface from Purchase Order
MM_DELIVERY_ADDR_SAP                    Determination of Delivery Address
ME_WRF_STD_DNG                          PO Controlling Reminder: Extension to Standard Reminder
ME_TRIGGER_ATP                          Triggers New ATP for Changes in EKKO, EKPO, EKPV
ME_TRF_RULE_CUST_OFF                    BADI for Deactivation of Field T161V-REVFE
ME_TAX_FROM_ADDRESS                     Tax jurisdiction code taken from address
ME_REQ_POSTED                           Purchase Requisition Posted
ME_REQ_OI_EXT                           Commitment Update in the Case of External Requisitions
ME_RELEASE_CREATE                       BAdI: Release Creation for Sched.Agrmts with Release Docu.
ME_PURCHDOC_POSTED                      Purchasing Document Posted
ME_PROCESS_REQ_CUST                     Enhancements for Processing Enjoy PReqs: Customer
ME_PROCESS_REQ                          Enhancements for Processing Enjoy PReqs: Internal
ME_COMMTMNT_PO_REL_C                    Check for Commitment-Relevance of Purchase Orders
ME_CCP_BESWK_AUTH_CH                    BAdI for authorization checks for procuring plant
ME_CCP_ACTIVE_CHECK                     BAdI to check whether CCP process is active
ME_BSART_DET                            Change document type for automatically generated POs
ME_BAPI_PR_CREATE_02
ME_BAPI_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
Amit.

How to delete Remittance Advice through FB01 - which User exit or BADI?

I have created a BDC program for transaction FB01 to create an FI posting. During this BDC session, i need to delete the associated remittance advice using the function REMADV_DELETE.
Is there a user exit or BADI that i can use to call REMADV_DELETE once the FI posting is successful?
Thanks,
Jay

Jay,
In BTE there are two types of exit - Publish and Subscribe (P&S) and Process. Generally P&S give access to read data from a transaction and trigger your own processing as a result, while Process give access to change parts of the data in the SAP transaction. For what you want, P&S probably gives the functionality you need.
You need to copy the sample function to a Z function in a Z function Group. Put in your code, and activate the function and function group. As an initial test just a break-point in the code is useful to see when the exit executes and what data is available.
Then in transaction FIBF you need to insert customising to link in and activate the exit.
In the FIBF transaction, go to menu option Settings>Products>Of a Customer. Select New Entries and create a Z... entry with appropriate text. Leave other fields at this time and save.
Go to Settings>P/S Modules>Of a Customer. Select New Entries and create an entry for the relevant event number with the Z product you just created and add your function module name. Country and Appl can be filled or left blank for "All". Save the entry.
Go back to the Settings>Products>Of a Customer entry and selct the activate check box and save the entry.
Your function should now get executed at the relevant point. Remember this will get executed in all posting transactions, so include appropriate checks for your transaction code, document type, etc.
One note. Transaction FB01 performs some of its updates using "IN UPDATE TASK" so some records may not be created at the time some exits are executed. In the old style debugger a commit is performed when you debug so the update is triggered, but then when you run without the debugging things work differently. The new style debugger lets you debug these exits without the commit and thus gives a better picture of what will really happen.
Andrew

User Exit or BADI for Material,BOM,Customer,Vendor

Dear All,
I have requirement where if User A changes a Material X .It should go for approval by workflow.
When the Material X is waiting for approval no other User should be able to change the material .It should give him a message
and restrict him from changing the Material.
Is there any User Exit or BADI to restrict him from changing the material. The exit or BADI should be called as soon as the Material is entered in MM02.
I need exit or BADI for BOM, Vendor and Customer also.
Thank you.

Hi,
You can go to Transaction SE80 and check in Function Group MATF. There have been two User Exits which are called during MM02 Transaction execution (via Analysis Transaction SE30) - MATERIAL_FIELD_SELECTION_NEW and MATERIAL_FIELD_SELECTION_COMB.
BAdI called by FM MATERIAL_FIELD_SELECTION_NEW.
Thanks and Regards,
Prabhakar Dharmala

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 MK01 transaction (used for saving vendor amster data)

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

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

User exit or BADI for recruitment

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

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

User 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

User exit or BAdi for field update in ECC system for SUS supplier

Dear Guru's,
I am configuring MM-SUS scenario in our srm 7.01 scenario. Not all vendors of our client are going to be SUS vendors. For SUS vendors, the client will be using Purchase Order Acknowledgement and Advanced Shipping Notification key. I am thinking of configuring a confirmation control key which will incoporate requirement of PO acknowledgement and Inbound delivery document. The assignment of confirmation control key and PO Acknowledgement Required checkbox in the vendor master record will default it in the purchase order.
Now, the question is how to update the existing vendor master data record which will be SUS vendor. I am looking at a solution like user exit or BAdi which updates the confirmation control key and purchase order acknowledgement required check box when the client manually assigns the class 'Z_CRED_SUSMM' to the ERMS vendor master.
Could you please help me to find the required exit or BAdi?
Thanks and regards,
Ranjan
Ranjan Sutradhar

EXIT_SAPMF02K_001 definitely wont work as this is for custom checks. this does not update data in vendor master.
you can try using below method of VENDOR_ADD_DATA badi.
IF_EX_VENDOR_ADD_DATA~PRESET_VALUES_PORG
but you need to read the screen field for classification and then according to that i think you can change the LFM1 data inside this badi

User Exit or BADI for Blocking process orders from R/3 to APO?

Dear Experts,
I am looking for a user exit or badi to block the process orders from R/3 to APO. As per standard it is not transferring orders which are clsd(closed status). Means that it is not updating live cache but its reading from R3.
We are facing some problems in cif queues which are not correctly maintained in R3 side. We dont want to touch those orders bcoz its very old data which is not required for planning.
There will be huge data which needs to be deleted while transferring through cif.
Please give any user exit (outbound intial transfer) from R/3.
Or any sugg. I apprecite your inputs...
Thanks
Cris

Hi Cris,
You can use user exit APOCF004 - Inbound Processing: Production Order/Planned Order in APO to prevent orders coming to APO by deleting orders which are not intended to goto APO from internal tables IT_ORD and IT_OUT.
Hope this helps.
Best Regards,
Ramesh M

User Exit or BADI for Operation tab of IW32 Transaction

Hi All,
Currently I am working on the transaction IW32. I am looking for a user exit or BADI which can trace the item level changed data for operations.
Thanks in advance.
Regards,
Rajesh

hi,
User Exit IWO10012.
BADi's
IWO1_ORDER_BADI
IWO1_PREQ_BADI
IWO1_SCREEN_MODIFY
Hope this helps
Regards,
Shashank

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

User Exit or BADI for Post Goods Issue (VL02N)

Hello everyone!
I have an issue with one of my customers and I would like your help.
When we do a stock transfer, from one plant to another, if the Material has a serial number set up in Material Master in one of the plants, and haven't for the other one, the system is generating an error message saying they have different serial numbers.
I need to find a User Exit, or BADI, that can be used to force the system to ignore serial number validation during the goods issue (for one especifc plant), but still require serial numbers in the deliveries from the other plants.
Any ideas experts?

Hey Juan Carlos,
Any ideas on which user-exits I should use?
And by your answer, did you mean I should make the values look the same, and try to "fool" the system?
Thanks

XK01 user exit or BADI in which LIFNR & BUKRS are available .

Similar Messages

Maybe you are looking for