Sales order forceful completion using the USER-EXIT

Hi all,
We have a requirement as follows: As soon as the sales order is created a smartform should get triggered. the configurations are done in nace. It is working fine. But in our case we dont enter the PO number in the sales order this will show an incompletion log throwing a warning message. So we need to do modification in the user exit MV45AFZZ for the forceful completion of the sales order
This is to be done for the order type Zxxx. As i have not worked in the userexits before can anyone help me with the code.
Thanks and Regards
venu.mulaparthi

Hi,
Try this..
Create a new incompletion procedure in SPRO without that PO number field..
In the user exit USEREXIT_SAVE_DOCUMENT_PREPARE in the include MV45AFZZ..
IF VBAK-AUART = 'Zxxx'.
* Switch the incompletion procedure.
  TVAK-FEHGR = 'ZZ'.   " New incompletion procedure..
* Then call the function module with the new incompletion procedure..
* I believe the function module name RV_CHECK_DOCUMENT.
* Or check RV*check*document in SE37..
* This will make sure the sales order to recognize
* the new incompletion procedure..
ENDIF.
Thanks
Naren

Similar Messages

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

    We’re implementing macros with the user exit EXIT_SAPMMCP6_002, but we see that the parameter table T_TAB doesn’t contain all lines and columns viewed in the grid of transaction MC94 (Change Plan – Consistent Planning).
    Nevertheless, files and columns that are contained, aren’t 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.

  • Stoping process of saving purchase order(ME21/ME21N) in the user exit.

    Hi,
    I am using user exit "EXIT_SAPMM06E_016" of purchase order. While creating PO and after user enters 1st line item or more items and presses save button, then this user exit will be called.
    Now my requirement is I have to check "item delivery date" , if it is more than 300 days from creation date then I have to show popup for warning the user for the same and if user want to make the changes then this user exit should stops the process of saving the PO and returns and allows to change the PO.
    Please help me in this.
    how I can stop the saving process.
    Thanks,
    Deepak

    Hi Deepak,
    You can do it in IM_ITEM method
    DATA: ls_mepoitem TYPE mepoitem.
    ls_mepoitem = im_item->get_data( ).
    if you check ls_mepoitem-quantity field it will give your required value....pls Go through the documentation below for the method
    Documentation for the method
    Processing of Item Data
    Functionality
    The PROCESS_ITEM method enables you to change the item data and check it
    for correctness.
    Parameters
    The following parameters are available:
    o IM_ITEM - Document item
    The interface reference is of the category
    IF_PURCHASE_ORDER_ITEM_MM. You can use all methods defined there.
    Note
    Please note the general hints on Error Handling.
    If you wish to mark the document item as invalid, use the
    INVALIDATE() method of the IF_PURCHASE_ORDER_ITEM_MM interface.
    Regards
    Byju

  • Download sales order data in Text format -User exit

    Hi Experts
    I am very new to user exits, my requirement is if i go to sales order change mode and then press save, some of the details about the sales order needs to be downloaded in text format. Please give me the steps and procedures.
    How to do this, please help me on this.
    Regards
    Rajaram

    Hi,
    Go to include MV45AFZZ,u will find USEREXIT_DOCUMENT_SAVE.In this exit
    u can get all the data from strcutures availabel thre..declare an internal table and fill the internal table with the data u want..andthen try for FM "GUI_DOWNLOAD" and pass the internal table data.I hope it might work..
    Regards,
    Nagaraj

  • Iam not getting the data on screen after using the user exit zxpadu01

    Dear Freinds
                As per my requirement when the user enters value Ansal  it should get defaulted to Amount field (bet01 ) based on the wage type
    i have written calculation ( q0008-bet01 = ansal/100) before it getting defaulted to bet01, i found that value is not getting default  on the screen for bet01 once i enter value for Ansal , please any body correct my code
    in   ZXPADU02 i have written the code as  below :
    data : wa_p0008 like p0008,
            i0008 like p0008,
           l_v_ANSAL type ANSAL_15,
           l_v_amount type PAD_AMT7S.
    CASE innnn-infty.
    when '0008'.
    CALL METHOD cl_hr_pnnnn_type_cast=>prelp_to_pnnnn
    EXPORTING
    prelp = innnn
    IMPORTING
    pnnnn = wa_p0008.   -- HERE I GOT ALL THE DATA EXCEPT BET01
    if wa_p0008-lga01 = 'MFPY'.
    l_v_ansal =  wa_p0008-ansal.
    l_v_amount = l_v_ansal / 100.
    move l_v_amount to wa_p0008-bet01.
    CALL METHOD cl_hr_pnnnn_type_cast=>pnnnn_to_prelp
    EXPORTING
    pnnnn = wa_p0008  --- HERE I CAN SEE EVEN THE BET01 IS FILLED
    IMPORTING
    prelp = innnn.         --- HERE I CAN SEE LGART BUT NOT AMOUNT VALUE
    endif.
    when others.
    endcase.
    IN ZXPADU01 I HAVE WRITTEN AS BELOW:
    data : wa_p0008 like p0008,
            i0008 like p0008,
           l_v_ANSAL type ANSAL_15,
           l_v_amount type PAD_AMT7S.
    CASE innnn-infty.
    when '0008'.
    MOVE-CORRESPONDING  innnn to wa_p0008.
    CALL METHOD cl_hr_pnnnn_type_cast=>prelp_to_pnnnn
    EXPORTING
    prelp = innnn
    IMPORTING
    pnnnn = wa_p0008.
    if wa_p0008-lga01 = 'MFPY'.
    l_v_ansal =  wa_p0008-ansal.
    l_v_amount = l_v_ansal / 100.
    move l_v_amount to wa_p0008-bet01.
    CALL METHOD cl_hr_pnnnn_type_cast=>pnnnn_to_prelp
    EXPORTING
    pnnnn = wa_p0008   --- I CAN SEE ONLY WHEN I COME AGAIN
    IMPORTING
    prelp = innnn.
    endif.
    when others.
    endcase.
    Now my problem is as follows :
                   i have entered the value for Ansal (ex: p0008-Ansal = 1000) ..........and i say enter then i should found the calculated value for the ansal through my coding
    and it should  display in bet01 as 10 ( q0008-bet01 =  p0008-ansal /100)
    but i dont find the value 10 being displayed for the field bet01 on the screen  when
    user enters Ansal  as 1000 .........even then i have saved it to test the scenario......
    now i came in displayed mode (pa20 ) for the infotype 008 for the same personnel no for the same  dates .....where i created the record........i found that the value
    bet01 is there i.e i can see  the value bet01 as 10 ( my requiremnt here matching)
    but when the user say enter during the time of creation of the record the value
    bet01 is not getting defaulted with 10 .........why iam not able to understand
    PLEASE ANY BODY HELP ME IN THIS REGARD 
    regards
    shanti.

    Hi Pranesh,
                   i have used the logic which you hav given as below
    in ZXPADU02
      FIELD-SYMBOLS <fs>  TYPE ANY.
    ASSIGN ('(MP000800)Q0008-betrg') TO <fs>.
    if <fs> is assigned.
    <fs> = l_v_amount .  ---  amount as (ansal /100 i.e 1000/100 = 10) 10
    endif.
    still iam not getting the data for the field bet01
    this is the coding i am using
    data : wa_p0008 like p0008,
            i0008 like p0008,
           l_v_ANSAL type ANSAL_15,
           l_v_amount type PAD_AMT7S.
      FIELD-SYMBOLS <fs>  TYPE ANY.
    CASE innnn-infty.
    when '0008'.
    MOVE-CORRESPONDING  innnn to wa_p0008.
    CALL METHOD cl_hr_pnnnn_type_cast=>prelp_to_pnnnn
    EXPORTING
    prelp = innnn
    IMPORTING
    pnnnn = wa_p0008.
    if wa_p0008-lga01 = 'MFPY'.
    l_v_ansal =  wa_p0008-ansal.
    l_v_amount = l_v_ansal / 100.
    move l_v_amount to wa_p0008-bet01.
    ASSIGN ('(MP000800)Q0008-betrg') TO <fs>.
    if <fs> is assigned.
    <fs> = l_v_amount .
    endif.
    CALL METHOD cl_hr_pnnnn_type_cast=>pnnnn_to_prelp
    EXPORTING
    pnnnn = wa_p0008
    IMPORTING
    prelp = innnn.
    endif.
    when others.
    endcase.
    please help me as iam still not getting (value in bet 01) when i press enter once i enter value in ansal feild.
    regards
    shanti.

  • 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

  • How to get the program where the User exit is use

    Hi,
       Could anyone let me know how to get the program which is using the user exit
    EXIT_SAPLFMR4_002 .
    Thank you.
    Donny~

    You can do a where used on the functino module EXIT_SAPLFMR4_002 in SE37.
    In this case, you user exit is called from a function module FMRE_FI_BELEG_CHECK.  Which in my system, doesn't appear to be called directly. It could be called dynamically.
    Regards,
    RichHeilman

  • Debugging the user exit in ECC

    hi
    we have enabled ATP check in system. when we create a sales order in ECC the call  goes to SCM and it creates the purchase requisition in ECC. we need to capture this purchase requisition number somewhere when we create the sales order. we figured out several user exits that are called during CIF transfer for example  in ECC system
    EXIT_SAPLCPUR_001
    EXIT_SAPLMEPI_001
    EXIT_SAPLMEPI_002
    EXIT_SAPLMEPI_003
    EXIT_SAPLMEPI_004
    EXIT_SAPLMEPI_005
    EXIT_SAPLMEPI_006
    EXIT_SAPLMEPI_007
    but when i put a session/external break point nothing happens. it does not stop. any suggestions
    thanks
    sankar

    If you are trying to set the breakpoint inside the user exit FM ,then the breakpoint will be caught only if an active project exists.
    Try putting a breakpoint outside the user exit FM at some statement.
    Also when you get into the debugger, activate the "update debuggeR"
    Hope this helps!

  • Changes in the user exit for VL01N dont reflect..

    Hello all,
                 I need a user-exit for restricting display ( and ultimately the delivery )of line-items while creating outbound delivery doc , depending on whether a particular line item is approved or not. I am currently using the user-exit (function exit)-exit_saplv50p_001 -> enhancement V50PSTAT. but the changes made to the work area is_lips in the include dont reflect in the final delivery 'item data' table . Is there any other way I can delete the unapproved line item form the final item-data table? The tables that are used in the main VL01N transaction are FXLIPS,XLIPS,L_LIPS etc. Please help me out here.
    Regards,
    me.

    Hi
    In user exit EXIT_SAPLV50P_001, IS_LIPS is an inporting parameter and changes made to this structure wont affect in any way.
    You need to find an enhancement where the LIPS structure or table parameter is being exported by the function module. so that changes done to it will affect and values will be carried forward.
    Regards,
    Dwaraka.S

  • Accessing Global data in the User exits.

    Dear All,
    I want to change some fields by using the user exit "EXIT_SAPLPC61_001" for Tcode ( 1KEK ) The fields which I wanted to access are global variables, so I couldnt able to access it .so  I used field symbol and did the change  ,by calling (SAPLPC61)t_fod[] .
    But Once I change the fields and put the record back to its memory , it just posting only 2 records instead of 50 records ..
    What I understood while debugging is,  it starts the first loop and goes to user exit and change the global variable values , once the value gets changed instead of going to second loop , the loop ends ..
    we got fifty records but it just shows only 2 records as posted .
    Just throw me some lights on this issue
    Thanks
    Vivek.

    Hi VRMan,
    I do not think it's possible to use Global Variables or Functional Globals in custom Express VIs. Is there a reason why you might want to use global variables/functional global in Express VI that you've created? Perhaps you want to try just passing data to the Express VI through the connector block.
    Regards,
    Stanley Hu
    National Instruments
    Applications Engineering
    http://www.ni.com/support

  • How to use/activate user exits

    Hi all,
    i wish to use user exit COZF0001...
    however i have no experience how to do it.  do i need an ABAPer or other consultant to do it or can i just activate it and make it work with minimal instructions?
    kindly give procedure/overview how to activate/use user exits.
    thanks in advance

    Hi Ramesh,
    Go to transaction CMOD . Create a project called ZVA01. Choose the Enhancement assign radio button and press the Change button. In the first column enter COZF0001.
    Note that an enhancement can only be used in 1 project. If the enhancement is already in use, and error message will be displayed
    Click on  Save . Go to Components. You can now see that enhancement uses the user exit EXIT_SAPLCOZF_001.  Double click on the exit and add your code.
    Activate the include program. Go back to CMOD and activate the project.
    -- Shivaji

  • 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

  • Creating delivery, can I check the sales order's field using user-exit or ?

    Hi dear.
    When I create a delivery in VL01N or other transactions, I want automatically to check the sales order's some field and to decide whether create or not.
    Can I use user-exit for that?
    Or other solutions is there?
    Thanks regards

    Yes your requirement can be achieved thru a User Exit.
    There are many User Exits available in Delivery as listed in the link below:
    https://wiki.sdn.sap.com/wiki/display/ERPLO/SDUserexits
    The selection of necessary User Exit is based on your specific requirement.
    Also if you want to check some feild of Sales Order whether it is completed or not, then you can also use Incompletion Procedure in Sales Order, which will make sure that no Sales Order is saved until the end-user enter data in those feilds.
    Hope this helps...
    Thanks,
    Jignesh Mehta

  • To populate condition in the sale order or a scenario in the USER Exit

    Hi Experts,
    I want to write the code in the USER EXIT to add a condition type in the Sale order when the ship-to-party address is changed in the transaction level from the address maintained in the Master data,
    So can anyone let me know is there any function module or how will i populate condition type.
    I found that the internal table XKOMV contains all the condition types.
    Thanks,
    Prem

    i saw the answer provided by u, i was pleased to find the answered way, so i writing back to u regarding my requirements.
    my requirement.
    while creating sale order, before entering the screen 4001 where we enter sold to party and material and order quantity, i need to populate these fields from my exit.
    i am able to populate the sold to party field from the exist  EXIT_SAPMV45A_002 and
    INCLUDE ZXVVAU04 .
    in the same fashion i need to populate my material filed.
    how do i do it

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

Maybe you are looking for

  • Print Logo in Report

    Hi All I want to print the report along with Logo in the reporting. Is it possible via ALV or Classical reporting or whether we should go for Smartform or Adobe Regards MD

  • My AC Power Cord is not working! What should I do?

    I realised that my Macbook Pro was not charging today, so I tried to reset my SMU and PRAM. It didn't work. I took out the AC Power Cord and used the 60W MagSafe Power Adapter instead (I attached the AC Power Cord to the adapter to increase the lengt

  • BPM Wait step!

    Friends, I have BPM which has the FOR-EACH Block in it. After the first message processed I have to wait for atleast 5 seconds to process the next message in FOR-EACH Block. The default BPM wait step has minimum of 1 Minute. Is there any other way we

  • Is there any SAP tool to run reports on different report server versions

    Hi, I have to run crystal reports on different report server versions. This is a repetition of the tasks as it requires installation of report servers and executing reports on both. Is there any SAP reporting tool which simplifies all these tasks , r

  • Field Short Text and long Text not displayed in SKA1 in Se17

    When try to extract chart of account data from SAP using Tcode se17 and table ska1. Short text and G/L acc long text are not displayed where as these are displayed when we use t code se16 and table ska1. My client want to use specifically se17 for ex