User exits that change invoice price?

Are you aware of any user exits that change invoice price?  Thanks.

Hi,
Pl use MV45AFZZ include. It has many user exists.
FORM userexit_pricing_prepare_tkomk.
Here you may your code
ENDFORM.              "USEREXIT_PRICING_PREPARE_TKOMK
FORM userexit_pricing_prepare_tkomp.
Here you may your code
ENDFORM.             "USEREXIT_PRICING_PREPARE_TKOMP
FORM userexit_save_document.
Here the code while saving the document
ENDFORM.                    "USEREXIT_SAVE_DOCUMENT
FORM userexit_save_document_prepare.
ENDFORM.                "USEREXIT_SAVE_DOCUMENT_PREPARE
Check the below enhancesments components also from SMOD.
V45A0001
V45A0002
V45A0003
V45A0004
V45E0001
V45E0002
V45L0001
V45P0001
V45S0001
V45S0003
V45S0004
V45W0001
V46H0001
V60F0001
Cheers
Hema

Similar Messages

  • User exit to change rbpk-zlspr prior to invoice save

    Hi,
       I need to locate a user exit that will lett me force my will on the setting of the payment block (rbkp-zlspr) in a Vendor Invoice that is being parked. Parking is being done vi FM MRM_INVOICE_PARK.
    I have looked at the methods in badi invoice_update but the rbkp structures are import only so that will not do it. Anyone had any experience.
    The reason I need to do this is that this is the second invoice that is being parked for a particular PO.
    The first invoice has been fully processed and some GR exists for that first invoice.
    The parking is being done using the MRM function modules and somewhere these decide that as the PO already has GR then this new invoice should have a block code that reflects existing GR, however that GR is not for this invoice and later custome programming for the new invoice requires it to have a particuar payment block code to proceed. Therefore I need to force that block code into RBKP when parking the invoice regardless of the MRM modules decision.
    Cheers,
    Ross
    Edited by: Ross Goodman on Nov 24, 2010 10:13 PM

    Hi Pranjali,
    1. Since break point is  getting reached in case of ME22n it will definitely reach in case of ME21n as well ( I have already worked on it).
    2. Now as far as the GR invoice or MIRO transaction is concerned,  I have checked with INVOICE_UPDATE BADI having method CHANGE_AT_SAVE. Break point is getting reached here as well.
    3. For IDoc thing what you can do is, find an appropriate exit in FM IDOC_INPUT_INVOIC_MRM. Since I don't have the IDoc setup which can replicate your scenario. It would be difficult to find the appropriate exit. So, to find the appropriate exit in this FM what you can do is to find string CALL CUSTOMER FUNCTION in the main program. This string will be followed by 001 or 002 etc. Out of this pick your appropriate FM and hence the proper exit.
    4. Similar is the case with BAPI_INCOMINGINVOICE_CREATE.
    I hope now it will definitely help you in resolving your queries to greater extent.
    Come up with queries if any.
    Cheers
    VJ
    Edited by: Vishal Jindal on Oct 25, 2010 7:55 AM

  • User Exit to avoid invoice splitting

    Hi Experts,
    I need a user exit to change this setting on invoice splitting to omit partner function if it is different.
    Does anyone has any idea on that?
    Thanks in advance.
    Best regards,
    Chris Gu

    Hi,
    Check SAP Note 11162 - Invoice split criteria in billing document, it tells you all reasons that happens in invoice splitting.
    I hope this helps you
    Regards
    Eduardo

  • User exit for changing Sales order lines.

    Hello experts ,
    I want to delete the field "ROUTE" from all of the orders lines in sales orders, I have been using "USEREXIT_SAVE_DOCUMENT_PREPARE"  but it does not seems to do the job.
    What is the name of  user exit that i have to use for this task and which structure should be used,  is it xvbap ? is it vbap ?
    Thanks for the help.
    Avi.

    Hi,
    find the user exit u required.
    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
    Best regards,
    venkatawamy.y

  • MIRO User - Exit to Change the Profit Centre..?

    I need to change the Profit Centre in the Accounting document(for Vendor Line Item) and Profit Centre Accounting Document(For Payable Line Item) Created by MIRO Transaction.Can any one let me know if there is anyuser-exit or badi to achieve the same
    Thanks a lot for your help .
    Regards,
    Gopi.K

    hi
    These are all the user exits avalilable for MIRO transaction.
    LMR1M001            User exits in Logistics Invoice Verification
    LMR1M002            Account grouping for GR/IR account maintenance
    LMR1M003            Number assignment in Logistics Invoice Verification
    LMR1M004            Logistics Invoice Verification: item text for follow-on docs
    LMR1M005            Logistics Inv. Verification: Release Parked Doc. for Posting
    LMR1M006            Logistics Invoice Verification: Process XML Invoice
    MRMH0001            Logistics Invoice Verification: ERS procedure
    MRMH0002            Logistics Invoice Verification: EDI inbound
    MRMH0003            Logistics Invoice Verification: Revaluation/RAP
    MRMN0001            Message output and creation: Logistics Invoice Verification
    I think you can use this exit.
    LMR1M002 
    Regards.
    Lavanya.

  • User exit  to change material availability date

    Hi Gurus,
       my requirement is like I need to change the material availability date based on some conditions.
    Is there any User Exit to change the availability date so that I can dump my code in the user exit .
    If not is there any alternative process to get the solution.
    Thanks,
    Sudhaa.............

    Hi Sudha,
    Can you tell me your requirement clearly please.
    Regards,
    Dhanunjaya Reddy

  • 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

  • User Exit for Changing G/L account in Accounting Document

    hi all,
    This one is urgent for me. If you guys can help.
    Iam looking for a user-exit to change the G/L account while posting the accounting document.
    If someone has worked on a similar user-exit Kindly help.
    Thanks and Regards
    Varun

    Hi Experts,
    The requirement is to change the GL account when PGI is done for a delivery.
    I have coded in the above user exit for changing the GL account. I am facing the issue here.
    I am changing the GL account through a user exit, but even before the user exit is  called the standard SAP is throwing a error.
    the Error is GL account is blocked for posting in the company code. This check is happening for the GL account what standard SAP proposes from the customization. The GL account that is getting picked is blocked in SPRO for posting in the mentioned company code. Because of the error message, our z code is not getting executed.
    Kindly suggest if some user exits that can be used even before this error message. or let me know if you have any suggestions to over come this.
    I have coded this in the enhancement point. Include  MM07MFK0_KONTIERUNG_PRUEFEN and subroutine kontierung_pruefen.
    Thanks,

  • User exit to change account assignments

    Hi gurus!
    Can anyone tell me a user exit to change some fields in Logistics Invoice (MIRO), when a an  fixe asset PO is made:
    BSEG-BSCHL - Posting Key
    BSEG-UMSKZ - Special G/L Indicator
    BSEG-UMSKS - Special G/L Transaction Type
    BSEG-HKONT - General Ledger Account
    I apreciate any help, expecially because we already achieved GO LIVE.
    Thanks in advance, Pedro Mariano

    Hello Pedro,
    We have the same requirement, how did you solve it?
    I would really apreciate your help.
    Thank you,
    Elisa

  • User Exit to Change Conditions Type into PO

    Hi Experts,
    Does anybody know a user exit to change of a condition's currency into a Purchase Order?
    I need to change currency type of manually entered conditions, so the user exit should be determinated by specifics conditions types and called up during a redetermination of all or individual price components.
    I'll appreciate any information.
    Best Regards.
    José

    Use BADI ME_PROCESS_PO_CUST

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

    Need to know the user exit,
    To change the <b>unlimited check box(</b>EKPO-UEBTK) in <b>delivery tag</b> of <b>item details</b> for tcode <b>ME21N/ME22N</b> on <b>SAVE</b>. 
    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*****

  • User exit to change shi-from address

    Hi Guys,
          Help me if you know an user exit for changing ship-from address while creating sale order.
    Thanks.

    Hi
    EXIT_SAPLV09A_001
    You can use this user exit to control whether an address that was entered manually and has already been used in other documents (referenced), should be referenced again if it changes or whether a new address should be created (duplicated).
    Hope this may help you
    Regards
    Srinath

  • USER EXIT to change VBAP-VSTEL

    Hi all, i have a question
    i'm fighting with consultant about this issue.
    We have a order type (ZRI0) with many Order Reasons, for a specific order reason (Z30) i want to change the default Shipping Point (VBAP-VSTEL)from V_TVSTZ-VSTEL (FAM1) to V_TVSTZ-VSTE1 (FAM2)
    the customization of table TVSTZ is that FAM1 is the default Shipping Point and FAM2 is the Manual Shipping Point
    So i asked an user exit that for the specific order reason changes Shipping Point to  V_TVSTZ-VSTE1 (FAM2)
    they say it's impossible , they can modify only exit MV45AFZZ FORM userexit_move_field_to_vbap
    i tried to modifying exit MV45AFZZ FORM userexit_save_document but nothing change, it seems that the customizing overwrites our modifications.
    So the question is : where can i insert this modification on document saving?

    Hi,
    There's no flag as such.
    What you can try is :
    Along with the modification of VBAP structure try modifying XVBAP too using the following code.
    SELECT SINGLE mtart INTO mara-mtart FROM mara WHERE matnr = vbap-matnr.
    IF mara-mtart 'DI' .
    if vbak-vkorg = 'FA01' and vbak-augru = 'Z30' and vbak-auart = 'ZRI0'.
    move 'FRGA' to vbap-lgort.
    move 'FAM2' to *X*vbap-vstel.
    move 'FA01' TO VBAP-WERKS.
    loop at xvbap.
    xvbap-vstel = 'FAM2'.
    xvbap-lgort = 'FRGA'.
    modify xvbap.
    endloop.
    endif.
    endif.
    Hope you are still writing this logic under save_document_prepare. It should work.
    Make sure my syntax is proper. Its been a while I lost tocuh with ABAP.
    Regards,
    Amit
    Edited by: Amit Iyer on Jun 10, 2011 1:07 PM

  • User-Exit to change/Calculate the Exchange Rate

    Hi ALL,
                 I am looking for an user-exit that can be used to change the Exchange Rate during the billing cycle. I want to claculate the exchange rate based on the translation date (BKPF-WWERT).
    BR,
    Tanmoy

    Hi ALL,
                This is a very tricky issue.
    The table BKPF has a field called WWERT (Translation Date). Now we want to calculate the Exchange rate based on the translation date. The table BSET has two fieds LWSTE (Tax Amount in Country Currency) &
    LWBAS (Tax Base in Country Currency)  and they must get updated with correct values based on the translation date, but thats not happening as the exchange rate is calculated based on the posting date/billing date. The exchange rate is determined from the TCURR table but its taking the incorrect Exchange rate.  I need to find out the way so that I can correct it.
    BR
    Tanmoy

Maybe you are looking for