What is the user exit to change segment version at the run time of an IDOC

Dear Experts
Please can some one help on this ...
Which is the user exit to change segment version at the run time of an outbound IDOC.
For example
Suppose we have a IDOC segment with two version 620 and 46C.
By default the IDOC pick the 620. But Our requirement is to use 46C.
What user exit we can use for outbound IDOC to change the version used at run time for a segment.
Appreciate your response.
Thanks

Hi,
ALE00001 EXIT_SAPLBD11_001
User exit for the IDOC version changer
Regards,
Ravi

Similar Messages

USER EXIT FOR CHANGING POSTING DATE IN THE MATERIAL DOCUMENT

Hi,
Pls advise any USER EXIT FOR CHANGING POSTING DATE IN THE MATERIAL DOCUMENT.
Regards,

Hi,
There is another user exit for updating material document data Upon posting is MB_CF001
I hope this will fullfill you.
Prem

Need to know the user exit to change unlimited check box in delivery tag

Need to know the user exit,
To change the unlimited check box(EKPO-UEBTK) in delivery tag of item details for tcode ME21N/ME22N on SAVE.
Thanks in Advance.
Baburaj

HI Baburaj,
Use the BADI ME_PROCESS_PO_CUST to change the unlimited check box(EKPO-UEBTK)
Implement the BADI and insert the code in the method PROCESS_ITEM
Example code :
*Data Declarations
DATA: ls_mepoitem TYPE mepoitem,
 ls_mepoitemx type mepoitemx,
 ls_customer TYPE mepo_badi_exampl,
 ls_tbsg TYPE tbsg.
INCLUDE mm_messages_mac. "useful macros for message handling
*here we get item data
ls_mepoitem = im_item->get_data( ).
*work area for price value
data : begin of it_eban,
banfn type mepoitem-banfn,
bnfpo type mepoitem-BNFPO,
pries type mepoitem-NETPR,
end of it_eban.
*Get the Purchase requisition price from EBAN table
select single banfn bnfpo preis from eban into it_eban
 where
 banfn = ls_mepoitem-banfn
 and bnfpo = ls_mepoitem-bnfpo.
*if entry is available.
if sy-subrc eq 0.
*check if price is zero
 if it_eban-pries EQ 0.
*if zero, set FREE field of PO to 'X'.
 ls_mepoitem-uebtk = 'X'.
 endif.
 endif.
*Set updated fields
CALL METHOD im_item->set_data
EXPORTING
im_data = ls_mepoitem
Reward if Helpful*****

MC94 - How to use the User exit EXIT_SAPMMCP6_002 to develop custom macros

Were implementing macros with the user exit EXIT_SAPMMCP6_002, but we see that the parameter table T_TAB doesnt contain all lines and columns viewed in the grid of transaction MC94 (Change Plan Consistent Planning).
Nevertheless, files and columns that are contained, arent shown in the order that they are visualized in the screen (MC94 - program SAPLMCPA screen 707).
Does somebody know how to update the grid visualized in that screen?
Thanks in advance for any help!

Hi,
Have you any luck with this yet. I am actually looking to do something similar but on the planning level.
To get the detailed level, you can try the following:
get the lines for this macro
CLEAR I_LINES. REFRESH I_LINES.
LOOP AT T_LINES WHERE KRIT1 = I_STRAT-AKT_PLOBJ
                    AND FLGIS IS INITIAL
                    AND STRUL = 'X'.
    I_LINES = T_LINES.
    APPEND I_LINES.
ENDLOOP.
get columns for this macro
LOOP AT T_COLS.
    LOOP AT I_LINES.
      READ TABLE T_TAB WITH KEY Z = I_LINES-LINE
                                C = T_COLS-COLUMN
                                BINARY SEARCH.
      IF SY-SUBRC EQ 0.
        I_COLS = T_COLS.
        APPEND I_COLS.
      ENDIF.
    ENDLOOP.
ENDLOOP.
SORT I_COLS.
DELETE ADJACENT DUPLICATES FROM I_COLS.
this should pull the values that are visually seen on the screen.
What i need is the values for ALL levels? I cant seem to figure this out.
Anyways, lemme know if the above was helpful.

User Exit for ME21 PO Creation at the time of saving--Urgent

Hi,
Can some one help me out in finding the user exit for PO creation at the time of saving.
The Requirement is:
I need to create a custom field in EKKO table.
After appending the structure with the field to the EKKO table, i need to create a PO.
Now i need to update the field which has been created at the time of pressing the SAVE button.
I need to update the EKKO table it self.
I could find the user exits but none of them have the EKKO table either in Changing or in Tables.
Thanks,

Hi,
You may want to check this user exits.
EXIT_SAPMM06E_012 - Check Customer-Specific Data Before Saving
EXIT_SAPMM06E_013 - Update Customer-Specific Data in Purchasing Document
Here is the list of available user exits for ME21.
EXIT_SAPMM06E_001 - Other Number Range or Own Document Number
EXIT_SAPMM06E_004 - User Exit for Cust.-Specific Control of Import Data Screens in Purchasing
EXIT_SAPMM06E_005 - Field Selection Control: Vendor Address Screen
EXIT_SAPMM06E_006 - Export Data to Customer Subscreen for Purchasing Document Header (PBO)
EXIT_SAPMM06E_007 - Export Data to Customer Subscreen for Purchasing Document Header (PAI)
EXIT_SAPMM06E_008 - Import Data from Customer Subscreen for Purchasing Document Header
EXIT_SAPMM06E_009 - Reset Customer Data at Beginning of New Document (Without Dialog)
EXIT_SAPMM06E_012 - Check Customer-Specific Data Before Saving
EXIT_SAPMM06E_013 - Update Customer-Specific Data in Purchasing Document
EXIT_SAPMM06E_014 - Read Customer-Specific Data when Importing Purchasing Document
EXIT_SAPMM06E_016 - Export Data to Customer Subscreen for Purchasing Document Item (PBO)
EXIT_SAPMM06E_017 - Export Data to Customer Subscreen for Purchasing Document Item (PAI)
EXIT_SAPMM06E_018 - Import Data from Customer Subscreen for Purchasing Document Item
EXIT_SAPMM06E_020 - User Exit: Change Document for Requisitions (Conversion into PO)
EXIT_SAPMM06E_021 - Fulfillment of Target Value: Release Orders Against a Contract
Reward points
Regards

User exit to change item level data in purchase order

Hi,
Can anyone let me know the user exit to change item level data in purchase order . there is a badi ME_PROCESS_PO_CUST for this but the issue is its method process_item gets triggered only when the item is changed. My requirment is
For purchase order document types u201CZSOu201D and u201CZCOu201D, where the purchase order is a u201CLimits Orderu201D only i.e. no materials or services on the purchase order, the print price indicator field should be set to u201Cblanku201D (unchecked). now i cant use ME_PROCESS_PO_CUST because process_item wont get triggered if there is no change in itemlevel data.
Regards,
Rahul

Hi Rahul,
Probably EXIT_SAPLMEKO_002.
hope it helps,
Edgar

Help - User exit to change item level data in Purchase Order

Hi,
Can anyone let me know the user exit to change item level data in purchase order . there is a badi ME_PROCESS_PO_CUST for this but the issue is its method process_item gets triggered only when the item is changed. My requirement is For purchase order document types u201CZSOu201D and u201CZCOu201D, where the purchase order is a u201CLimits Orderu201D only i.e. no materials or services on the purchase order, the print price indicator field should be set to u201Cblanku201D (unchecked). now i cant use ME_PROCESS_PO_CUST because process_item wont get triggered if there is no change in item level data.
Thanks,
Rahul

Hi Rahul,
Probably EXIT_SAPLMEKO_002.
hope it helps,
Edgar

How to find the user exit for order cancellation

I want to find the user exit for order cancellation. And also to ensure that no one amends the order once the canellation has taken place. The cancellation shall be deemed to be affected only if the vendor has confirmed the acknowledgement of the order cancellation.
I have got a Zreport where this order should not come as open order item.
Please tell me the method of finding the users exit for order cancellation and stop the order from getting modified. And also how to find the tables in which the data has to be updated that the order has to be cancelled.
In the PO header i want an additional tab <cancellation> by which the user by the help of userid and password should be able to cancel the order. An order once cancelled cannot be undone. A new order has to be placed. The new order can be placed refencing the cancelled purchased order.
My client has got a very stringent requirement. In the past cancelled order has been undone and caused lot of problems.
Regards.

hi
pls tell me t.code so that i will send all user exits related to that particular t.codes
Thanks & Regards
phaneendra

To find the User Exits for a particular Transaction.

hi,
    I want to find the number of User Exits for a The Transaction MM01 or MM02,
    I serched in the forums but could not find satisfactory ans,
    I tried with:
             T.Code-> System>Status->Prog Name>SE38>find Call Customer-Exit.
    But its not helping me,
    Please help me.
Thanks and Regards
Suraj S Nair.

hi ,
if you are new to user exist use --> follw the below methos to find the user exit for a particular transaction or t-code
create one custom pgm in se38 and execute >selection screenenter t-code and execute it will return all the user exists for a specific transaction..
Finding the user-exits of a SAP transaction code
* Finding the user-exits of a SAP transaction code
* Enter the transaction code in which you are looking for the user-exit
* and it will list you the list of user-exits in the transaction code.
* Also a drill down is possible which will help you to branch to SMOD.
* Written by : SAP Basis, ABAP Programming and Other IMG Stuff
*              http://www.sap-img.com
report zuserexit no standard page heading.
tables : tstc, tadir, modsapt, modact, trdir, tfdir, enlfdir.
         tables : tstct.
data : jtab like tadir occurs 0 with header line.
data : field1(30).
data : v_devclass like tadir-devclass.
parameters : p_tcode like tstc-tcode obligatory.
select single * from tstc where tcode eq p_tcode.
if sy-subrc eq 0.
   select single * from tadir where pgmid = 'R3TR'
                    and object = 'PROG'
                    and obj_name = tstc-pgmna.
   move : tadir-devclass to v_devclass.
      if sy-subrc ne 0.
         select single * from trdir where name = tstc-pgmna.
         if trdir-subc eq 'F'.
            select single * from tfdir where pname = tstc-pgmna.
            select single * from enlfdir where funcname =
            tfdir-funcname.
            select single * from tadir where pgmid = 'R3TR'
                               and object = 'FUGR'
                               and obj_name eq enlfdir-area.
            move : tadir-devclass to v_devclass.
          endif.
       endif.
       select * from tadir into table jtab
                     where pgmid = 'R3TR'
                       and object = '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.
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.
*---End of Program
Regards,
Prabhudas

Determine which validation step called the user exit, possible?

Hello all,
We have a a validation with different steps that use the same user exit in their respective check.
My functional analyst asked me if there is a way to programmatically determine in the user exit which step is executing the user exit.
So I am asking the same question here.
As an example:
Validation FI100 has step 001, 002, and 003.
Each of these steps use the user exit U100 from module pool ZGGBR001 in their check.
I haven't found a way in the code of U100 to determine which step called U100.
Does anyone know if this can be done?
I have used the following technique to get a variable from the program's call stack.
data: var_name(30) type c value '(Z_CALLING)VARIABLE' .
field-symbols: <fs> type any.
assign (var_name) to <fs>.
write: / 'Variable from Z_CALLING', <fs>.
But I'm not sure how this might work with validation steps/user exits.
Thanks
Bruce

Vinod,
I did some debugging after I posted my question. I came to the same solution, use FM 'SYSTEM_CALLSTACK'.
VALCHCK_2FI100##001
loop at i_callstack into w_callstack
where EVENTNAME+0(9) = 'VALCHCK_2'.
FI110 is the validation
001 is the step
Thomas,
Thanks for the caveats.
Bruce

What are the User Exits for Sales Order creation process?

Hi,
what are the User Exits for Sales Order creation process? how can I find them?
thanks in advance,
will reward,
Mindaugas

Please check this info:
User Exits In Sales Document Processing
This IMG step describes additional installation-specific processing in sales document processing. In particular, the required INCLUDES and user exits are described.
Involved program components
System modifications for sales document processing affect different areas. Depending on the modification, you make the changes in the program components provided:
MV45ATZZ
For entering metadata for sales document processing. User-specific metadata must start with "ZZ".
MV45AOZZ
For entering additional installation-specific modules for sales document processing which are called up by the screen and run under PBO (Process Before Output) prior to output of the screen. The modules must start with "ZZ".
MV45AIZZ
For entering additional installation-specific modules for sales document processing. These are called up by the screen and run under PAI (Process After Input) after data input (for example, data validation). The modules must start with "ZZ".
MV45AFZZ and MV45EFZ1
For entering installation-specific FORM routines and for using user exits, which may be required and can be used if necessary. These program components are called up by the modules in MV45AOZZ or MV45AIZZ.
User exits in the program MV45AFZZ
The user exits which you can use for modifications in sales document processing are listed below.
USEREXIT_DELETE_DOCUMENT
This user exit can be used for deleting data which was stored in a separate table during sales document creation, for example, if the sales document is deleted.
For example, if an additional table is filled with the name of the person in charge (ERNAM) during order entry, this data can also be deleted after the sales order has been deleted.
The user exit is called up at the end of the FORM routine BELEG_LOESCHEN shortly before the routine BELEG_SICHERN.
USEREXIT_FIELD_MODIFICATION
This user exit can be used to modify the attributes of the screen fields.
To do this, the screen fields are allocated to so-called modification groups 1 - 4 and can be edited together during a modification in ABAP. If a field has no field name, it cannot be allocated to a group.
The usage of the field groups (modification group 1-4) is as follows:
Modification group 1: Automatic modification with transaction MFAW
Modification group 2: It contains 'LOO' for step loop fields
Modification group 3: For modifications which depend on check tables or on other fixed information
Modification group 4: is not used
The FORM routine is called up for every field of a screen. If you require changes to be made, you must make them in this user exit.
This FORM routine is called up by the module FELDAUSWAHL.
See the Screen Painter manual for further information on structuring the interface.
USEREXIT_MOVE_FIELD_TO_VBAK
Use this user exit to assign values to new fields at sales document header level. It is described in the section "Transfer of the customer master fields into the sales document".
The user exit is called up at the end of the FORM routine VBAK_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBAP
Use this user exit to assign values to new fields at sales document item level. It is described in the section "Copy customer master fields into the sales document".
The user exit is called up at the end of the FORM routine VBAP_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBEP
Use this user exit to assign values to new fields at the level of the sales document schedule lines.
The user exit is called up at the end of the FORM routine VBEP_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBKD
Use this user exit to assign values to new fields for business data of the sales document. It is described in the section "Copy customer master fields into sales document".
The user exit is called up at the end of the FORM routine VBKD_FUELLEN.
USEREXIT_NUMBER_RANGE
Use this user exit to define the number ranges for internal document number assignment depending on the required fields. For example, if you want to define the number range depending on the sales organization (VKORG) or on the selling company (VKBUR), use this user exit.
The user exit is called up in the FORM routine BELEG_SICHERN.
USEREXIT_PRICING_PREPARE_TKOMK
Use this user exit if you want to include and assign a value to an additional header field in the communication structure KOMK taken as a basis for pricing.
USEREXIT_PRICING_PREPARE_TKOMP
Use this user exit if you want to include or assign a value to an additional item field in the communication structure KOMP taken as a basis for pricing.
USEREXIT_READ_DOCUMENT
You use this user exit if further additional tables are to be read when importing TA01 or TA02.
The user exit is called up at the end of the FORM routine BELEG_LESEN.
USEREXIT_SAVE_DOCUMENT
Use this user exit to fill user-specific statistics update tables.
The user exit is called up by the FORM routine BELEG-SICHERN before the COMMIT command.
Note
If a standard field is changed, the field r185d-dataloss is set to X. The system queries this indicator at the beginning of the safety routine. This is why this indicator must also be set during the maintenance of user-specific tables that are also to be saved.
USEREXIT_SAVE_DOCUMENT_PREPARE
Use this user exit to make certain changes or checks immediately before saving a document. It is the last possibility for changing or checking a document before posting.
The user exit is carried out at the beginning of the FORM routine BELEG_SICHERN.
User exits in the program MV45AFZA
USEREXIT_MOVE_FIELD_TO_KOMKD
Use this user exit to include or assign values to additional header fields in the communication structure KOMKD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
USEREXIT_MOVE_FIELD_TO_KOMPD
Use this user exit to include or assign values to additional item fields in the communication structure KOMPD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
USEREXIT_MOVE_FIELD_TO_KOMKG
Use this user exit to include or assign values to additional fields in the communication structure KOMKG taken as a basis for material determination and material listing. This is described in detail in the section "New fields for listing/exclusion".
USEREXIT_MOVE_FIELD_TO_KOMPG
Use this user exit to include or assign values to additional fields in the communication structure KOMPG taken as a basis for material determination and material listung. This is described in detail in the section "New fields for listing/exclusion".
USEREXIT_REFRESH_DOCUMENT
With this user exit, you can reset certain customer-specific fields as soon as processing of a sales document is finished and before the following document is edited.
For example, if the credit limit of the sold-to party is read during document processing, in each case it must be reset again before processing the next document so that the credit limit is not used for the sold-to party of the following document.
The user exit is executed when a document is saved if you leave the processing of a document with F3 or F15.
The user exit is called up at the end of the FORM routine BELEG_INITIALISIEREN.
User-Exits in program MV45AFZB
USEREXIT_CHECK_XVBAP_FOR_DELET
In this user exit, you can enter additional data for deletion of an item. If the criteria are met, the item is not deleted (unlike in the standard system).
USEREXIT_CHECK_XVBEP_FOR_DELET
In this user exit, you can enter additional data for deletion of a schedule line. If the criteria are met, the schedule line is not deleted (unlike in the standard system).
USEREXIT_CHECK_VBAK
This user exit can be used to carry out additional checks (e.g. for completion) in the document header. The system could, for example, check whether certain shipping conditions are allowed for a particular customer group.
USEREXIT_CHECK_VBAP
This user exit can be used to carry out additional checks (e.g. for completion) at item level.
USEREXIT_CHECK_VBKD
The user exit can be used to carry out additional checks (e.g. for completion) on the business data in the order.
USEREXIT_CHECK_VBEP
This user exit can be use to carry out additional checks (e.g. for completion) on the schedule line. During BOM explosion, for example, you may want certain fields to be copied from the main item to the sub-items (as for billing block in the standard system).
USEREXIT_CHECK_VBSN
You can use this user exit to carry out additional checks (e.g. for completion) on the serial number.
USEREXIT_CHECK_XVBSN_FOR_DELET In this user exit, you can enter additional criteria for deletion of the serial number. If the criteria are met, the serial number is not deleted (unlike in the standard system).
USEREXIT_FILL_VBAP_FROM_HVBAP
You can use this user exit to fill additional fields in the sub-item with data from the main item.
USEREXIT_MOVE_FIELD_TO_TVCOM_H
You can use this user exit to influence text determination for header texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
USEREXIT_MOVE_FIELD_TO_TVCOM_I
You can use this user exit to influence text determination for item texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
User-Exits for product allocation:
The following user exits all apply to structure COBL, in which the data for account determination is copied to item level.
USEREXIT_MOVE_FIELD_TO_COBL
Option to include new fields in structure COBL.
USEREXIT_COBL_RECEIVE_VBAK
Option to assign values from the document header to the new fields.
USEREXIT_COBL_RECEIVE_VBAP
Option to supply values from the item to the new fields.
USEREXIT_COBL_SEND_ITEM
A changed field can be copied from the structure into the item. You could use the user exit to display a certain field in the account assignment block (see also MV45AFZB).
USEREXIT_COBL_SEND_HEADER
A changed field can be copied from the structure to the header (see source text MV45AFZB)
USEREXIT_SOURCE_DETERMINATION
You can use this user exit to determine which plant will be used for the delivery. In the standard system, the delivering plant is copied from the customer master or the customer-material info record. If you want to use a different rule, then you must enter it in this user exit.
USEREXIT_MOVE_FIELD_TO_ME_REQ
With this user exit you can include additional fields for the following fields:
EBAN (purchase requisition)
EBKN (purchase requisition-account assignment)
USEREXIT_GET_FIELD_FROM_SDCOM
Option to include new fields for the variant configuration. Fields that are included in structure SDCOM can be processed and then returned to the order.
USEREXIT_MOVE_WORKAREA_TO_SDWA
You can use this user exit to format additional work areas for the variant configuration. You will find notes on the user exit in MV45AFZB.
User-Exits for first data transfer:
The following user exits can only be used for the first data transfer.
Note
Only use the user exits if the names/fields do NOT have the same name.
USEREXIT_MOVE_FIELD_TO_VBAKKOM
Option to include additional fields in structure VBAKKOM (communiction fields for maintaining the sales document header)
USEREXIT_MOVE_FIELD_TO_VBAPKOM
Option to include additional fields in structure VBAPKOM (communication fields for maintaining a sales item)
USEREXIT_MOVE_FIELD_TO_VBEPKOM
Option to include additional fields in structure VBEPKOM (communication fields for maintaining a sales document schedule line)
USEREXIT_MOVE_FIELD_TO_VBSN
You can use this user exit to include fields in structure VBSN (scheduling agreement-related change status).
USEREXIT_MOVE_FIELD_TO_KOMKH
You can use this user exit to include new fields for batch determination (document header).
USEREXIT_MOVE_FIELD_TO_KOMPH
You can use this user exit to include new fields for batch determination (document item).
USEREXIT_CUST_MATERIAL_READ
You can use this user exit to set another customer number in the customer material info record (e.g. with a customer hierarchy)
USEREXIT_NEW_PRICING_VBAP
Option for entry of preconditions for carrying out pricing again (e.g. changes made to a certain item field could be used as the precondition for pricing to be carried out again). Further information in MV45AFZB.
USEREXIT_NEW_PRICING_VBKD
Option for entry of preconditions for carrying out pricing again (e.g. changes to the customer group or price group could be set as the preconditions for the system to carry out pricing again). Further information in MV45AFZB.
User-Exits in Program MV45AFZD
USEREXIT_CONFIG_DATE_EXPLOSION
The BOM is exploded in the order with the entry date. You can use this user exit to determine which data should be used to explode the BOM (explosion with required delivery date, for example).
User exits in the program FV45EFZ1
USEREXIT_CHANGE_SALES_ORDER
In the standard SAP R/3 System, the quantity and confirmed date of the sales document schedule line is changed automatically if a purchase requisition is allocated, and it or the sales document is changed (for example, quantity, date).
If you want to change this configuration in the standard system, you can define certain requirements in order to protect your sales orders from being changed automatically. Use this user exit for this purpose. Decide at this point whether the schedule lines are to be changed.
User-Exits in Program RV45PFZA
USEREXIT_SET_STATUS_VBUK
In this user exit you can you can store a specification for the reserve fields in VBUK (header status). Reserve field UVK01 could, for example, be used for an additional order status (as for rejections status, etc.).
The following workareas are available for this user exit:
VBUK (header status)
FXVBUP (item status)
FXVBUV (Incompletion)
USEREXIT_SET_STATUS_VBUP
In this user exit you can you can store a specification for the reserve fields for VBUP (item status).
The following workareas are available for this user exit:
FXVBAP (Item data)
FXVBAPF (Dynamic part of order item flow)
FXVBUV (Incompletion)
USEREXIT_STATUS_VBUK_INVOICE
You can use this user exit to influence billing status at header level.
User exits in the screens
Additional header data is on screen SAPMV45A 0309, additional item data on screen SAPMV45A 0459. These screens contain the Include screens SAPMV45A 8309 or SAPMV45A 8459 as user exits.
Fields which are also to be included in the sales document for a specific installation should be included on the Include screens for maintaining. If an application-specific check module is needed for the fields, this can be included in the Include MV45AIZZ. The module is called up in the processing logic of the Include screens.
For field transports, you do not have to make changes or adjustments.
Example
A new field, VBAK-ZZKUN, should be included in table VBAK.
If the check is defined via the Dictionary (fixed values or check table) the field must be included with the fullscreen editor in the Include screen SAPMV45A 8309. In this case, no change has to be made to the processing logic.
User Exits in Program MV45AFZ4
USEREXIT_MOVE_FIELD_TO_KOMK
You can use this user exit to add or edit additional header fields in the communication structure - KOMK- for free goods determination. For more information, see the New Fields for Free Goods Determination IMG activity.
USEREXIT_MOVE_FIELD_TO_KOMP
You can use this user exit to add or edit additional item fields in the communication structure KOMP for free goods determination. For more information see the New Fields for Free Goods Determination IMG activity.
User Exits in the SAPFV45PF0E and SAPFV45PF0C Programs
EXIT_SAPFV45P_001
You can use this user exit to decide whether intercompany billing data is used in the profitability segment for cross-company code sales, or whether the data comes from external billing (external customer, sales data from the selling company code.
Regards
Eswar

Is there any user exit to change the UOM of a material while creating sales

Hi experts,
I have a requirement to change the UOM of the item material in sales order while creating. Could anybody help me in finding the correct user-exit to change the UOM.
Thanks,
srinivas.

Hi Ravish,
I am already changing the UOM in the same include and in the subroutine "USEREXIT_MOVE_FIELD_TO_VBAP". But it is again over writing in the standard program. What I need to do, to remain same UOM.
Thanks,
srinivas.

What are the user-exits which will trigger on saving Sales Order

Hello Experts!!!
I am working on Sales Order VA01. The requirement is I need to pre populate Sold-to-Party field. I find out user-exit (V45A0002 Predefine sold-to party in sales document ). So it is working fine.
Now second requirement is I need to capture all the date once user saves Sales Order. Also the time or Sales Order creation I have to make u2018GRAYu2019 some of the fields so user cannot change the value. Can anybody tell me which user-exits should I use to retrieve the entire information user entered and lock fields in Sales Order screen?
Thanks a lot on advance.

Hi
U can't find it there,because it's a include, not enanchement.
So u need to use the trx SE38, not CMOD.
For sales ored there aren't the enanchements, but only some FORMs defined in particular includes.
U need to get the access key by OSS in order to change them.
These are the rest of the includes where u can find other exits:
 INCLUDE MV45ATZZ. " Data definitions in MV45ATOP
 INCLUDE MV45AOZZ. " User-modules PBO
 INCLUDE MV45AIZZ. " User-modules PAI
 INCLUDE MV45AFZA. " User-forms < 3.0
 INCLUDE MV45AFZB. " User-forms
 INCLUDE MV45AFZC. " User-forms < 3.0D
 INCLUDE MV45AFZD. " User-forms 3.0E
 INCLUDE MV45AFZF. " User-forms 3.0F
 include mv45afzg. " User-forms 3.1G
 INCLUDE MV45AFZH. " User-forms 4.6B
 INCLUDE MV45AFZZ. " User-forms
 INCLUDE MV45AFZ4. " User-forms 4.0
Anyway u can find some information about these exit in customizing (trx SPRO):
Sales and Distributions->System modifications->User exits
Max

Find the user exit while creation and change of sales order

Hi Team
Below mentioned requirement , in which user exit i have to put below logic while creaion and change of sales order?
u2022     The logic for the user exit to explode should consider the following assumptions and validations
o     Customer master to have the entry at KNVV-KVGR1
o     Material master to have the entry at MVKE
o     UoM in the Sales order item (VBAP- VRKME) should be = Pallets PAL or tonnes (TES)
o     Should have more than one line item or number of line items with UoM PAL or tonnes TES should be > 1
for example :-->
Product A with Scales mentioned below
Product A     Quantity / Scale     UoM     Price(£)
     0-10     PAL/TES     20
     11- 20     PAL/TES     10
     21- 30     PAL/TES     5
     31-40     PAL/TES     2.5
     >41     PAL/TES
Product B with Scales mentioned below
Product B     Quantity / Scale     UoM     Price(£)
     0-15     PAL/TES     25
     16-20     PAL/TES     20
     21- 30     PAL/TES     15
     31-40     PAL/TES     10
     > 41     PAL/TES     5
u2022     Product A (qty 10PAL) + Product B (qty 15 pal) ordered in a single order with 2 line items.
u2022     The expected results should be
o     Product A qty 10 + B qty 15 added = 25Pal
o     The system user exit should add the total number of pallets on the order line items and point towards the respective scales, so in this example prices against each line item should be the respective price against 25 Pal = 5£ for product A per pal and £15 for product B.
Thanks in Advance.
Puneet.

Hi Team
Below mentioned requirement , in which user exit i have to put below logic while creaion and change of sales order?
u2022 The logic for the user exit to explode should consider the following assumptions and validations
o Customer master to have the entry at KNVV-KVGR1
o Material master to have the entry at MVKE
o UoM in the Sales order item (VBAP- VRKME) should be = Pallets PAL or tonnes (TES)
o Should have more than one line item or number of line items with UoM PAL or tonnes TES should be > 1
for example :-->
Product A with Scales mentioned below
Product A Quantity / Scale UoM Price(£)
0-10 PAL/TES 20
11- 20 PAL/TES 10
21- 30 PAL/TES 5
31-40 PAL/TES 2.5
>41 PAL/TES
Product B with Scales mentioned below
Product B Quantity / Scale UoM Price(£)
0-15 PAL/TES 25
16-20 PAL/TES 20
21- 30 PAL/TES 15
31-40 PAL/TES 10
41 PAL/TES 5
u2022 Product A (qty 10PAL) + Product B (qty 15 pal) ordered in a single order with 2 line items.
u2022 The expected results should be
o Product A qty 10 + B qty 15 added = 25Pal
o The system user exit should add the total number of pallets on the order line items and point towards the respective scales, so in this example prices against each line item should be the respective price against 25 Pal = 5£ for product A per pal and £15 for product B.
Thanks in Advance.
Puneet.

Need the user exit/BADI name for Reverese order MIGo- ME21N(changing item)

Hi
I have the below requirement.
I am changing the item details in the transaction MIGO transaction,the value of MSEG entries
are got changed.and also it should change in the Purchase order level also(in the table EKKO).
Can anybody tell me the User Exit /BADI name which is triggered in the Reverse order
i.e MIGO -> ME21N.So that i can implement my code in the reverse order in the User Exit/BADI.

hi I did not find any paramater type EKPO in the Exporting or changing of any methods in the BADI's given by you...........

What is the user exit to change segment version at the run time of an IDOC

Similar Messages

Maybe you are looking for