Reg: User exits used in pa40 and pb10

Hi Experts,
I need to find user exit in pa40 and pb10 main program ,where i can capture fields like RCINS (vendor ID) and offid (advertisement ) and need to update applicant details into my z table.

Try the one in with +: Both of Tcodes have Same user Exits
Exit Name           Description
+ HRPBAS01          User Exit for HR Master Data*
HRPC0001            HR: PC download authorization
HRRPAI01            User exit for FB HR_ENTRY_DATE and HR_LEAVING_DATE
PARA0001            Enhancement for Determining the Number of Periods
PARA0002            Enhancement for Calculating Annual Salary; IT0008,14,15
+ PBAS0001            PA: Pers.Admin./Recruitment: Default values and checks*
PBAS0002            PA: Enhancements for Personnel Administration - Menu
PBASRP01            PA: User exit distributed reporting
PBAS0004            Spanish Data Privacy Law: User Exit for Recording
Regards
Shital

Similar Messages

User exits used in sales and distribution?

i need some user exits   that we commonly used in sd. please if somebody has worked on user exits . and how are they used..
points will be awarded to all for replying...
thanks in advance
Neha.

Hi refer below
It is most common that one or other time we need to use this function while configuring multi tasking & complex Prcing Architecture.
Here Iam giving a simple guide to add fields to the Pricing Field Catalogues:
For example you want to use field PSTYV ('Sales document item category') that is included in structure KOMP ('Pricing Communication Item') as a key for a condition table.
When you create a condition table (Transaction V/03), however, the system does not propose the field in the field catalog.
Condition access, field catalog, allowed fields, KOMG, KOMK, KOMP, KOMPAZ, KOMKAZ, PSTYV are the other terms which we need to know about, to add Fields.
Reason and Prerequisites
For technical reasons, field PSTYV was included in structure KOMP, however, not in structure KOMG ('Allowed Fields for Condition Structures').
Proceed as follows:
1. Call up the ABAP Dictionary (Transaction SE11) and create data type ZZPSTYV. Choose PSTYV as a domain.As a short text, you can use, for example, 'ZZ - sales document item category' and as a field label, you can use the field labels of PSTYV.Save, check and activate your entries.
2. Call up structure KOMPAZ in the ABAP Dictionary (Transaction SE11) in the change mode and make the following entry:
Component   Component type
ZZPSTYV     ZZPSTYV
Save, check and activate the change you made.
3. Note:Because of the change in structure KOMPAZ, field ZZPSTYV is now known in structures KOMG and KOMP because structure KOMPAZ is included in both structures.
4. Call up Transaction SPRO. Navigate to 'Sales and Distribution -> Basic Functions -> Pricing -> Pricing Control' and execute 'Define Condition Tables'.
Choose 'Conditions: Allowed fields' and include ZZPSTYV as a new entry.
5. Note:Now you can use field ZZPSTYV as a key field when you create a condition table Axxx.
6. Supply the new field you defined by including the following source code line in USEREXIT_PRICING_PREPARE_TKOMP:
              MOVE xxxx-PSTYV TO TKOMP-ZZPSTYV.
In order processing you find the user exit in Include MV45AFZZ, and in billing document processing you find it in Include RV60AFZZ.
Consider that you can also use this note as a help if you want to use other customer-specific fields as key fields in a condition table.
For header fields, use structure KOMKAZ instead of structure KOMPAZ and USEREXIT_PRICING_PREPARE_TKOMK instead of USEREXIT_PRICING_PREPARE_TKOMP.
For more information, see Transaction SPRO via the path 'Sales and Distribution -> System Modifications -> Create New Fields (Using Condition Technique) -> New Fields for Pricing' and OSS Note 21040.
USEREXIT
Userxits allow us to add our own functionality to SAP standard program
without modifying it . These are implemented in the form of subroutines and hence are also known as FORM EXITs. The userexits are generally collected in includes and attached to the standard program by the SAP.
    All Userexits start with the word USEREXIT_...
FORM USEREXIT_..
z..
ENDFORM.
The problem lies in finding the correct userexit and how to find it if one exists for the purpose. Once the correct userexit is found the necessary
customer code is inserted in the customer include starting with the z..
in the form routine.
e.g. USEREXIT_SAVE_DOCUMENT_PREPARE
Certain application like SD still provide this form of enhancement using userexit but this practice is no longer being followed for newer extensions
instead they are using EXITs which come bundeled in enhancement packages . Neverthiless existing USEREXITS will be supported by SAP an all the newer versions of SAP.
HOW TO FIND USEREXITS
Userexits can be found in number of ways:
1) To find userexits in SD module , goto object navigator(SE80) and select
    development class from the list and enter VMOD in it. All of the userexits in SD are contained in the development class VMOD. Press
enter and you will find all the includes which contain userexits in SD for
different functions like PRICING, ORDER PROCESSING etc. Select the userexit according to the requirement and read the comment inserted in it
and start coding .
Some examples of userexits in SD(SALES & DISTRIBUTION ) are:
1)ADDING OF NEW FIELDS IN PRICING
In Pricing in SD the fields on the basis of which pricing is done are derived from the FIELD CATALOG which is a structure KOMG .This structure is used to transfer transaction data to the pricing procedure in SD and is also known as communication structure.This structure KOMG consists of two tables KOMK for Header related fields and KOMP for item related fields.
   The fields which are not in either of the two tables KOMK and KOMP
cannot be used in pricing .Sometimes a need arises when the pricing
is to be based on some other criteria which is not present in the form of fields in either of the two tables.
This problem can be solved by using USEREXITS which are provided for pricing in SD.
Pricing takes place both when the SALES ORDER ( Transaction VA01) is created as well as when INVOICING ( Transaction VF01) is done.Hence SAP provides 2 userexits ,one for sales order processing which is
USEREXIT_PRICING_PREPARE_TKOMP or
USEREXIT_PRICING_PREPARE_TKOMK
Depending upon which table (KOMK or KOMP) the new fields were inserted we use either of the above two userexits.These userexits are found in include MV45AFZZ of the standard SAP sales order creation program SAPMV45A.
In the case of userexit which will be called when invoicing is done ,these
are provided in the include RY60AFZZ which is in the standard SAP
program SAPMV45A. The name of the userexits are same. i.e
USEREXIT_PRICING_PREPARE_TKOMP or
USEREXIT_PRICING_PREPARE_TKOMK
These userexits are used for passing the data from the communication structure to the pricing procedure, for this we have to fill the newely
created field in the communication structure KOMG for this we fill the code in the above userexit using the MOVE statement after the data that
has to be passed is taken from the database table by using the SELECT statement. The actual structure which is visible in these userexits and which is to be filled for that particular field is TKOMP or TKOMK.
Before the coding for these userexits is done ,it is necessary to create a new field in either of the two tables KOMK or KOMP .For this purpose
includes are provided in each of them .
To create the field in header data(KOMK) the include provided is KOMKAZ
and to create the field in item data(KOMP) the include provided is KOMPAZ.
One possible example for the need of creating new fields can be e.g. Frieght to be based upon transportation zone ,for this no field is available in field catalog and hence it can be created in KOMK and then above userexits can be used to fill the transportation data to it.
2)The other method of finding userexit is to find the word USEREXIT in the
associated program of the transaction for which we want to determine userexit using SE38.
3)The other method of finding userexits is to find the include in case of SD/MM applications where the userexits are located ,this can be found in the SAP reference IMG generally in the subfolder under SYSTEM MODIFICATION.
Some other examples of userexits in SD are:
USEREXIT_NUMBER_RANGE
This userexit is used to assign a different internal document number to the
sales order(VA01) when it is created depending on some criteria like a different SALES ORGANIZAION(VKORG) .
USEREXIT_SAVE_DOCUMENT_PREPARE
This userexit is used to insert the ABAP code which will be called when
the document (sales order VA01) is just about to be saved.This userexit is used generally for custom checks on different fields , to display some information before the order will be saved or for making changes to certain fields before the sales order will be saved.
Exits & Enhancements
There are mainly six types of EXITs in sap which have been collected in the form of enhancement packages and attached to standard code in SAP.
These are different from USEREXIT in the way that they are implemented
in the form of FUNCTIONs while in USEREXITS we use form routines for their implementation. These are also sometimes known as function exits .
   These start from the word EXIT_ followed by the program name and then followed by a three digit number.
e.g. EXIT_SAPMV45A_002
This exit is found in SD in enhancement V45A0002.
TYPES OF EXITS
1)MENU EXITS
2)FUNCTION EXITS
3)TABLE EXITS
4)SCREEN EXITS
5)KEYWORD EXITS
6)FIELD EXITS
We use SAP transactions CMOD and SMOD to manage exits. Before implementing an exit , it is required to create the project by using CMOD
selecting the enhancement e.g. V45A0002 and selecting the component
(one which fulfills our need) i.e the exit which will be implemented in SMOD and after coding has been done the project has to be activated.
An exit can be coded only once.
FUNCTION EXITS
These are used to add functionality through ABAP code . These start from the word EXIT_programname_NNN ending in a 3 digit number. No access code is required to implement any tupe of exit including function exits.
   The function exits are called from the standard SAP program in the form
of ABAP statement
CALL CUSTOMER-FUNCTION 'NNN'
This is in contrast to USEREXITs where PERFORM statement is used to call
the required userexit.
To implement the FUNCTION EXITs first of all the project is created and a suitable enhancement package is selected and from its compnents the function exit to be implemented is selected and on double clicking it the exit code will appear in ABAP EDITOR(se38) where a Z include will be found and the customer code should be entered in this include.
e.g.
ADDING A DEFAULT SOLD-TO-PARTY in Sales Order Creation
    To show a default sold-to-party in this field when the user creates a sales order (VA01) we can use a function exit .This function exit is located
in enhancement no V45A0002 . Before we can choose the exit we have to
create a project in CMOD after that enter V45A0002 in the enhancement field and click on the components . In the components you will see the
exit EXIT_SAPMV45A_002 . This exit is used for our purpose.
Double clicking on this exit will takes us to function builder (SE37) . This
function exit has one exporting parameters and two importing parameters, we are interested in exporting parameter which is E_KUNNR
of type KNA1-KUNNR i.e if we move the desired customer name to this
structure(E_KUNNR) it will be shown in the field as the default value when we create the sales order.
This function also contains a customer include ZXVVA04 . This include
will be used to write our custom code .
Double clicking on this include and it will prompt us that this include does not exists do you want to create this object ,select yes and the include will be created .In this include we can write our own code that will fill the field E_KUNNR.
e.g. E_KUNNR = 301.
Activate the include and Activate the project. Now when ever the SALES ORDER will be created , sold-to-party field will come up with a predefined
customer .
FIELD EXITS
The field exits are managed,created,activated through program RSMODPRF. The field exit is associated with a data element existing in ABAP dictionary and hence to the screen field using that data element.
The format of field exit is :
FIELD_EXIT_dataelement_A-Z or 0-9
   If a particular screen and program name is not specified than the field exit will effect all the screens containing that data element.
   The function module associated with field exit shows two parameters
INPUT and OUTPUT. Input parameter contains the data passed to the field exit when the field exit was invoked by the R/3 , We can write our own code to change the output parameter depending upon our requirements.
    Before the field exit can have any effect the system profile parameter
ABAP/FIELDEXIT in all the application servers should be set to YES
ABAP/FIELDEXIT = YES.

Reg user exit used for reading VB items

Dear all,
Please give me the details of user exit used when we run plant level MRP by MDBT, so that it will create
purchase requisitions only for consumables VB items, please explain how it works.
Thanks in advance

Hi,
Can you explain what you mean by
create purchase requisitions only for consumables VB items
So for others you want to have planned orders?
Regards,
Vivek

How to find out the 'z' user exit used in a Particular Transaction

Hi,
I have requirement to analyse all the user exits used in a transaction say 'VA01' . How can i find the user exits in a VA01 transaction. Can anyone suggest how to find the User exits
Thanks in Anticipation.
With Best Regards
mamatha

you can execute the following program , give the transaction name and execute
*& Report YCHATEST                                                    *
REPORT z_find_userexit NO STANDARD PAGE HEADING.
*& Enter the transaction code that you want to search through in order
*& to find which Standard SAP User Exits exists.
*& Tables
TABLES : tstc,     "SAP Transaction Codes
         tadir,    "Directory of Repository Objects
         modsapt, "SAP Enhancements - Short Texts
         modact,   "Modifications
         trdir,    "System table TRDIR
         tfdir,    "Function Module
         enlfdir, "Additional Attributes for Function Modules
         tstct.    "Transaction Code Texts
*& Variables
DATA : jtab LIKE tadir OCCURS 0 WITH HEADER LINE.
DATA : field1(30).
DATA : v_devclass LIKE tadir-devclass.
*& Selection Screen Parameters
SELECTION-SCREEN BEGIN OF BLOCK a01 WITH FRAME TITLE text-001.
SELECTION-SCREEN SKIP.
PARAMETERS : p_tcode LIKE tstc-tcode OBLIGATORY.
SELECTION-SCREEN SKIP.
SELECTION-SCREEN END OF BLOCK a01.
*& Start of main program
START-OF-SELECTION.
* Validate Transaction Code
SELECT SINGLE * FROM tstc
    WHERE tcode EQ p_tcode.
* Find Repository Objects for transaction code
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 = enlfdir-area.
        MOVE : tadir-devclass TO v_devclass.
      ENDIF.
    ENDIF.
* Find SAP Modifactions
    SELECT * FROM tadir
      INTO TABLE jtab
      WHERE pgmid    = 'R3TR'
        AND object   = 'SMOD'
        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:/(95) sy-uline.
      FORMAT COLOR COL_HEADING INTENSIFIED ON.
      WRITE:/1 sy-vline,
      2 'Exit Name',
      21 sy-vline ,
      22 'Description',
      95 sy-vline.
      WRITE:/(95) sy-uline.
      LOOP AT jtab.
        SELECT SINGLE * FROM modsapt
        WHERE sprsl = sy-langu AND
        name = jtab-obj_name.
        FORMAT COLOR COL_NORMAL INTENSIFIED OFF.
        WRITE:/1 sy-vline,
        2 jtab-obj_name HOTSPOT ON,
        21 sy-vline ,
        22 modsapt-modtext,
        95 sy-vline.
      ENDLOOP.
      WRITE:/(95) sy-uline.
      DESCRIBE TABLE jtab.
      SKIP.
      FORMAT COLOR COL_TOTAL INTENSIFIED ON.
      WRITE:/ 'No of Exits:' , sy-tfill.
    ELSE.
      FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.
      WRITE:/(95) 'No User Exit exists'.
    ENDIF.
ELSE.
    FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.
    WRITE:/(95) 'Transaction Code Does Not Exist'.
ENDIF.
* Take the user to SMOD for the Exit that was selected.
AT LINE-SELECTION.
GET CURSOR FIELD field1.
CHECK field1(4) EQ 'JTAB'.
SET PARAMETER ID 'MON' FIELD sy-lisel+1(10).
CALL TRANSACTION 'SMOD' AND SKIP FIRST SCREEN.

User exit for tcode ME21N and ME22N

Hi everyone
Can anybody tell me the user exits found in the tcodes ME21N nad ME22N, when saving a PO?
Regards
Anjali

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            Individual customer 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
M06B0004            Number range and document number
M06B0005            Changes to comm. structure for overall release of requisn.
M06E0004            Changes to communication structure for release purch. doc.
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., preview)
MEFLD004            Determine earliest delivery date f. check w. GR (only PO)
MELAB001            Gen. forecast delivery schedules: Transfer schedule implem.
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
MEQUERY1            Enhancement to Document Overview ME21N/ME51N
MM06E011            Activate PReq Block
LMEKO001            Extend communications structure KOMK for pricing
LMEKO002            Extend communications structure KOMP for pricing
If useful reward.
Vasanth

User exit used

Hi,
what is the user exit used and what is the requirement.
Thi s was a ninterview question .
What would be the best answer

Hi Soumya,
Check out the following links for user exits
Reward points if helpful.
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://expertanswercenter.techtarget.com/eac/knowledgebaseAnswer/0,295199,sid63_gci982776,00.html

User-exit using the dispatcher

Hi,
I am creating outbound files with file adapter and I need to generate the name of files dinamically. Where can I found documentation and examples about user-exits using the dispatcher?
Tks,
Douglas

You can BADI ME_PROCESS_PO_CUST to make the changes to PO Line items.
Use the method PROCESS_ITEM to get the values of the Line item conditions and populate the Items. In this method, you have an access to the item object using the parameter IM_ITEM. Use method GET_CONDITIONS, to get the conditions. Set the value of your field and use method SET_DATA to set values at line item.
Regards,
Naimesh Patel

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.

REG : user exit

hi,
    i am writing this code in user exit MV45AFZZ for va32 and va02 transaction.it is working fine but the problem is whatever i select the first line item it is not responding corectly.ther then first line item the other line items are working properly and in va32 transaction when i select item overview tab then also the program is not working properly please help me out
LOOP AT XVBAP.
IF TCTRL_U_ERF_AUFTRAG-CURRENT_LINE = SY-TABIX
OR TCTRL_U_ERF_LIEFERPLAN-CURRENT_LINE = SY-TABIX.
SELECT VBELN POSNR ZEILE MATNR VTWEG WERKS DISPO
         M1QTY M1QTY01 M1QTY02 M1QTY03 M1QTY04 MONYR KUNNR
         INTO CORRESPONDING FIELDS OF TABLE IDEMAND
         FROM ZSDDEM WHERE VBELN EQ VBAK-VBELN
                     AND   POSNR EQ XVBAP-POSNR
                     AND   MATNR EQ XVBAP-MATNR
                     AND   KUNNR EQ KUAGV-KUNNR.
SORT IDEMAND BY VBELN POSNR ZEILE DESCENDING.
LOOP AT IDEMAND.
SELECT MAX( ZEILE ) INTO WA_ZEILE
                FROM ZSDDEM WHERE MONYR EQ IDEMAND-MONYR
                            AND   VBELN EQ IDEMAND-VBELN
                            AND   POSNR EQ IDEMAND-POSNR.
                           AND   KUNNR EQ IDEMAND-KUNNR
                           AND   MATNR EQ IDEMAND-MATNR
IF SY-SUBRC = 0.
IF WA_ZEILE EQ IDEMAND-ZEILE.
TOTQ = TOTQ + IDEMAND-M1QTY.
ELSE.
DELETE IDEMAND INDEX SY-TABIX.
ENDIF.
ENDIF.
ENDLOOP.
IF TOTQ > 0.
    MESSAGE E020(ZSD_AMP) WITH TOTQ.
ENDIF.
ENDIF.
ENDLOOP.
ENDIF.

Hi,
Can you please check the below sap note?
Note 414421 - Creating or transferring simulat. version: CONVT_NO_NUMBER
Please also check
2.      0.410      PS-ST-WBS      449922      CJVB_PRPS_POST: ERR_UPDATE during update on table PRPS      27.02.2002
     3.      0.400      PS-SIM      805384      CJV2; network structure graphic; create activity: NOT_FOUND      30.12.2004
     4.      0.370      PS-SIM      379157      CJV4: SAPSQL_ARRAY_INSERT_DUPREC in SAPLV60F      24.03.2003
     5.      0.340      SV-SMB-AIO-BP-IMC      612325      Coll.note: BP Industrial Machinery & Components (IM&C)V3.46C      25.08.2003
Thanks,
Ramakrishna

User Exits in entire BW and R/3

Hi all
Can anyone please tell me in how many places we can write user exits in entire BW and R/3.
I know two places where we can write user exits
1. While enhancing the datasources in R/3
2. For variables while creating reports
Apart from these two, are there any other places where we can write user exits.
Thanks,
Sabrina.

hi NB,
seems nobody knows your email you didn't mention nor maintain it in your business card.
you can try to download pdf 'enhancements in sap bw' from sdn
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/59069d90-0201-0010-fd81-d5e11994d8b5
also check following
/people/sap.user72/blog/2005/02/14/logistic-cockpit--when-you-need-more--first-option-enhance-it
http://www.ko-india.com/content/weblogs/weblog_custom_fields_1.pdf
Enhancement
User exit
to get better response, create new thread instead of replying closed/solved one

Reg:User Exit Programm

Hi Gurus,
In purchasing order what r the user exits available in sap?
regards
T.Reddy

See the below user exits available for purchase 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            Individual customer 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
M06B0004            Number range and document number
M06B0005            Changes to comm. structure for overall release of requisn.
M06E0004            Changes to communication structure for release purch. doc.
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., preview)
MEFLD004            Determine earliest delivery date f. check w. GR (only PO)
MELAB001            Gen. forecast delivery schedules: Transfer schedule implem.
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
MEQUERY1            Enhancement to Document Overview ME21N/ME51N
MRFLB001            Control Items for Contract Release Order
Thanks
Seshu

User exit Used while defining the storage type

Hi all,
Can anybody tell me about the user exit Used while defining the storage type.
or what is the user exit name?
i want to define my own strategy.
i.e combine manual sut entry with strategy 'k'

HI all I Got the Exit MWMTO003.
Now ,
Following Logic is to be built. (Storage type strategy is K for putaway.)
u201CManually selection of SUTu201D while Putaway , For Strg -K SUT selection is
system guided.
Which componant is required for this. Pls guide.
Is the above requirement is possible?
Edited by: dev .. on Feb 19, 2009 1:58 PM

User exits : How to build and use through our form application ?!

Hi ,
Im trying to build a user exit based on a C++ program , to be used within our application.
I installed from the Oracle 8 Client CD the Oracle Pro*C/C++ ver 8.0.5 , i have Developer 2000 rel 6.0 patch 7 installed also .
Can anyone please provide me with the steps to build a user exit from A-Z , i read many Documents regarding that but all seems to me complicated , since also im not a C programmer , what i did for the time bieng i searched for file that ends *.pc on my hard disk and i found some of these files , i opend the Pro* C/C++ and it generates for me a *.C file , i reached this stage , then what should i do then to complete the task , for me i went directly to Forms and added a Button that calls the USER_EXIT built-in function , but simply it gave me an error message : User exit doesn't exist .
So Please if you could list for me the steps one by one i would be so graetful to you .
Thanx all in advance for all your efforts .
Islam

Why not make a stored procedure or PL/SQL-procedure? What you have to do is, to build a new version of runform, where you including your user-exits.
But if you insist: Use the help system. They have a description of how to do it on windows. It's more or less the same on unix.

Reg user exits exit_saplogdl_005 and exit_saplogsl_007 for va01 tcode

Hi All,
I have a requirement to add new fields to additional dataB fields for the transactions va01,va02 and all that we can do with screens 4462 of main screen 8459 and we can write the code in the user exit userexit_move_field_to_vbap in program MV45AFZZ. But in our requirement they also mentioned we have to write the code in the fun mod exits "exit_saplogdl_005" and "exit_saplogsl_007"
These exits I am able to find only in my version ECC6.O not in 4.7 and all and also I don't find any parameters for this function module exits. Can any body throw some idea how I can use of this fun mod exits.
Thanks&Regards
Mahesh

Hi All,
I have a requirement to add new fields to additional dataB fields for the transactions va01,va02 and all that we can do with screens 4462 of main screen 8459 and we can write the code in the user exit userexit_move_field_to_vbap in program MV45AFZZ. But in our requirement they also mentioned we have to write the code in the fun mod exits "exit_saplogdl_005" and "exit_saplogsl_007"
These exits I am able to find only in my version ECC6.O not in 4.7 and all and also I don't find any parameters for this function module exits. Can any body throw some idea how I can use of this fun mod exits.
Thanks&Regards
Mahesh

Reg:User-Exit In Sales Order to Invoice

Hi All,
I have An requirement that to create automatic sales order and invoice in one go, i have used BAPI_SALESORDER_CREATEFROMDAT2 to create sales order and bdc invoice to create invoice its worked fine.
My problem is now i got an requirement as after creating sales order it should not create invoice as such because they will manually check whether the sales order is correct then only i should proceed to invoice also they need the option to create,change,delete sales order and same too invoice how can i acheive this scenario through user exits?
Since am new to user exit can any one tell me how to use user exits and what user exits need like this scenario?

Hi Suresh,
For sales order following user exits can be used. These are available in include MV45AFZZ.
USEREXIT_DELETE_DOCUMENT : At the time of deletion of sales order
USEREXIT_SAVE_DOCUMENT : At the time of updations or creation of sales order.
Following are the user exits available in smod.
SDVFX007 User exit: Billing plan during transfer to Accounting
SDVFX008 User exit: Processing of transfer structures SD-FI
SDVFX009 Billing doc. processing KIDONO (payment reference numbe
SDVFX010 User exit item table for the customer lines
SDVFX011 Userexit for the komkcv- and kompcv-structures
V05I0001 User exits for billing index
V05N0001 User Exits for Printing Billing Docs. using POR Procedu
V60A0001 Customer functions in the billing document
V60P0001 Data provision for additional fields for display in lis
V61A0001 Customer enhancement: Pricing
Please check this exits which will help you for your requirement.
Thanks,
Naveen Kumar.

Reg: User exits used in pa40 and pb10

Similar Messages

Maybe you are looking for