Plant determination user exits

Hi,
Can anyone please suggest me a proper user exit that can be used for plant determination in SD (specifically during order creation)?
Thanks,
Amit

Hi
The user exit is MV45ATZZ. My project has used this to determine plant at VA01/VA02 level. If you need some specific info, please mail me.
Kind Regards
Sandeep
[email protected]

Similar Messages

  • FI MM account determination user exit

    Dear All,
    In FI-MM integration, GL account for material movements is determined based on the settings in OBYC. The GL account is determined based on chart of accounts, valuation class, general modifier, transaction key etc.
    The transaction key is in turn determind through the Movement type. However our requirement is that for same movement type say 201, i want different GL accounts to be determined based on "Reason for movement".
    Is there any user exit available in MM to derive the different GL accounts based on reason for movement.
    Thanks and Regards
    Partha

    Hi
    Try with enhancement LMR1M002. See these notes
    Note 523495 - FAQ: Account determination.
    Note 165692 - Documentation: Enhancement LMR1M002 (MM-IV)
    Note 301477 - Accnt determintn for WRX for materl grp not possble
    I hope this helps you
    Regards
    Eduardo

  • User Exit M06B0002 - EXIT_SAPLEBND_001

    Hi,
    We are using a release strategy that should check the field "Quantity" in the purchase requisition (MEREQ3321-MENGE).
    The Release Strategy is using a communication structure called CEBAN in which this field does not exist.
    We would like to populate the field CEBAN-USNR1 with the value in the field "Quantity" in the Purchase Requisition (MEREQ3321-MENGE).
    We activated user exit EXIT_SAPLEBND_001 and we try to import the value from EBAN-MENGE. The problem is that EBAN-MENGE is not filled until the document is saved.
    We don't know how to import the value of the "quantity" field into the CEBAN communication structure so that the release strategy can work.
    The CEBAN communication structure does not have key fields to help...
    Does anyone have an idea on how to do that ?
    Thank you very much.
    Best regards,
    Remi

    In SAP standard user exit, we cannot access information which is not defined in the import parameter of user exit.
    To overcome this problem, we can use following technique for accessing information outside of the User exit scope.
    For Example:
    In partner determination user exit EXIT_SAPLV09A_004 we cannot access document type or any sales document header information.
    Go in debugging mode inside the exit. Click "Calls"..
    When you check calls in user exit, then you will find SAPMV45A where VBAK or other sales document information structure are avaliable. then you can use this informaiton as follows:
    Example:
    CONSTANTS: C_VBAK(14) TYPE C VALUE '(SAPMV45A)VBAK',
    FIELD-SYMBOLS: <FS_VBAK> TYPE VBAK.
    ASSIGN (C_VBAK) TO <FS_VBAK>.
    CHECK <FS_VBAK>-AUART = C_ZSQT OR
    <FS_VBAK>-AUART = C_ZDQT.
    SELECT SINGLE AUART
                          FROM VBAK
                          INTO V_AUART
                          WHERE VBELN = <FS_VBAK>-VGBEL.
    In your case, go in debugging mode of user exit.. EXIT_SAPLEBND_001..
    Click "calls"... check the programs.. and try to find out which program contains the required variable and its value..
    then you can use it as explained above....
    I hope it is solved...

  • Brief about enhancements and user exits

    hai,
    can any  one tell me what are enhancements and user exits in sap sd,
    their  signifcance & configuration
    regards
    sriram

    hi,
    an example of user exit
    In case of Inbound DELINS IDOC (830 type) once there was a requirement of taking the “Target *** Qty required” and the “Target *** Date” for a specific customer who was not sending “*** Qty Received” by him.
    So for that specific customer we used the search term and added the same in the “Data 4” field of the IDOC under segment E1EDK09.
    There was one user exit available in IDOC_INPUT_DELINS_START Function module of SAP. We triggered this logic by the search term of customer and reached the user exit where we had made some code changes. (User Exits are used to make code changes when we are running standard programs or reports or function modules). With this we were able to reach the desired point of calculating “*** Issued” and then find out the difference from “Target *** Qty” and get “*** Qty Received” for the scheduling agreement. We did not copy the standard function module into Z . Instead the same was done using a user exit.
    <b>User exits in SD</b>
    Menu Path:
    SPRO- IMG- SD- System Modification- User Exists. User Exists are available in SD for the following processes:
    • User exits for price determination
    • User exits for partner determination
    • User exits for credit check & risk management
    • User exits in sales:
    o User exits in sales doc processing
    o User exits for contract processing
    o User exits for product allocation processing
    o User exits for availability checking
    o User exits for component supply processing
    o User exits for product selection
    o User exits for billing plan
    • User exits for shipping
    • User exits for transportation
    • User exits for billing
    • User exits for general billing interface
    • User exits for sales support
    • User exits for lists.
    The topic of user exits is a subject that concerns ABAP development & extensive experience in ABAP is required to understand and use the user exits.
    A customer user exit is essentially a function module using a unique naming convention, in which set import and export parameters are defined to limit the data that can be manipulated. This is to protect certain data from being changed. This function module is attached to an enhancement that may contain other function modules. A user exit should only be used if the possibilities for customizing or application-specific user exits are inadequate.
    NEW FIELDS IN PRICING:
    To use a field in pricing, one creates a cond table. This cond table is created using the allowed fields from the field catalog. Should the fields one requires not be included in the list of allowed fields, one can add the fields from the list of available fields. However, one may find that a new field may not be in the list of available fields. For this reason, one must create new fields for pricing. The document & item data in SD is stored in data tables such as VBAK & VBAP (for the order transaction). Many of the fields from these tables are available in the field catalog.
    The field catalog is a structure (KOMG) that consists of 2 tables (KOMK & KOMP). These tables contain the header & item data for pricing respectively. They are called KOM”x” because they are communications structures used to communicate the transaction data with the pricing procedure. Table KOMG contains the field KOMK & KOMP.
    If you require a field that is not in KOMG, it means that it is not in KOMK or KOMP. This means that the field you require cannot be used in pricing because there is no communication of this field from the transaction to the pricing procedure via the communication structures.
    To use a field not defined in the field catalog, you need to add this field to KOMK or KOMP structures, and then write the ABAP code to transfer the data in the field from the transaction tables to the communication structure. Follow these steps:
    Create the field in the KOMK (header data) & KOMP (item data) tables using the standard includes provided for this requirement.
    Write the code in the user exit to read the transaction data & transfer it to the KOM”x” structures.
    Menu Path:
    SPRO- IMG- SD- System Modification- Create New Fields (using the cond tech)- New fields for Pricing.
    Adding the field to KOMK & KOMP:
    This process requires some knowledge of the ABAP dictionary & how to use the ABAP dictionary to create & change fields & tables. If the field is from the header table (for e.g. the order table: VBAK), you will need to add it to the include table KOMKAZ in the table KOMK. If the field is from the item table (for e.g. the order item table: VBAP), you will need to add it to the include table KOMPAZ in table KOMP.
    Let’s say you need to use the ‘base material’ to define a price & the base material is no in the pricing field catalog. The base material is a field on the MMR basic data screen & is defined as MARA-WRKST. Since this relates to the material, it is at the item level, so you would add the field to KOMKAZ include table.
    • When you add a field to these tables, it must start with ‘ZZ’. Therefore, the field you add would be ZZWRKST. In ABAP, when you add the field, use the same domain as in the field in the original table MARA-WRKST.
    • After adding the field, generate the structure KOMP. This field is not available in the field catalog & can be used in condition tables.
    Menu Path:
    SPRO- IMG- SD- System Modification- User Exists. User Exists are available in SD for the following processes:
    • User exits for price determination
    • User exits for partner determination
    • User exits for credit check & risk management
    • User exits in sales:
    o User exits in sales doc processing
    o User exits for contract processing
    o User exits for product allocation processing
    o User exits for availability checking
    o User exits for component supply processing
    o User exits for product selection
    o User exits for billing plan
    • User exits for shipping
    • User exits for transportation
    • User exits for billing
    • User exits for general billing interface
    • User exits for sales support
    • User exits for lists.
    The topic of user exits is a subject that concerns ABAP development & extensive experience in ABAP is required to understand and use the user exits.
    A customer user exit is essentially a function module using a unique naming convention, in which set import and export parameters are defined to limit the data that can be manipulated. This is to protect certain data from being changed. This function module is attached to an enhancement that may contain other function modules. A user exit should only be used if the possibilities for customizing or application-specific user exits are inadequate.
    NEW FIELDS IN PRICING:
    To use a field in pricing, one creates a cond table. This cond table is created using the allowed fields from the field catalog. Should the fields one requires not be included in the list of allowed fields, one can add the fields from the list of available fields. However, one may find that a new field may not be in the list of available fields. For this reason, one must create new fields for pricing. The document & item data in SD is stored in data tables such as VBAK & VBAP (for the order transaction). Many of the fields from these tables are available in the field catalog.
    The field catalog is a structure (KOMG) that consists of 2 tables (KOMK & KOMP). These tables contain the header & item data for pricing respectively. They are called KOM”x” because they are communications structures used to communicate the transaction data with the pricing procedure. Table KOMG contains the field KOMK & KOMP.
    If you require a field that is not in KOMG, it means that it is not in KOMK or KOMP. This means that the field you require cannot be used in pricing because there is no communication of this field from the transaction to the pricing procedure via the communication structures.
    To use a field not defined in the field catalog, you need to add this field to KOMK or KOMP structures, and then write the ABAP code to transfer the data in the field from the transaction tables to the communication structure. Follow these steps:
    Create the field in the KOMK (header data) & KOMP (item data) tables using the standard includes provided for this requirement.
    Write the code in the user exit to read the transaction data & transfer it to the KOM”x” structures.
    Menu Path:
    SPRO- IMG- SD- System Modification- Create New Fields (using the cond tech)- New fields for Pricing.
    Adding the field to KOMK & KOMP:
    This process requires some knowledge of the ABAP dictionary & how to use the ABAP dictionary to create & change fields & tables. If the field is from the header table (for e.g. the order table: VBAK), you will need to add it to the include table KOMKAZ in the table KOMK. If the field is from the item table (for e.g. the order item table: VBAP), you will need to add it to the include table KOMPAZ in table KOMP.
    Let’s say you need to use the ‘base material’ to define a price & the base material is no in the pricing field catalog. The base material is a field on the MMR basic data screen & is defined as MARA-WRKST. Since this relates to the material, it is at the item level, so you would add the field to KOMKAZ include table.
    • When you add a field to these tables, it must start with ‘ZZ’. Therefore, the field you add would be ZZWRKST. In ABAP, when you add the field, use the same domain as in the field in the original table MARA-WRKST.
    • After adding the field, generate the structure KOMP. This field is not available in the field catalog & can be used in condition tables.
    Pl reward if helpful.
    Thanks
    Sadhu Kishore

  • User Exit for Updating Delivery Plant at Item Level in Sales Order

    Hello Experts
    There is a requirement to determine the delivery plant for each item level and than update the items with newly determined plant.  There is a user exit MV45AFZZ routine FORM USEREXIT_MOVE_FIELD_TO_VBAP. to update the item level entries in Sales Order in VA01 or VA02. Is this the right place to do this?, if yes , do i need to perform any other standard logic (like re determine Shipping points , schedule lines ) for newly determined plant? If not , can you please suggest any other place , BADI or user exit to change the delivery plant of sales order.
    Thanks a lot....
    -Harkamal

    Best place is MV45AFZZ-USEREXIT_SAVE_DOCUMENT_PREPARE. Populates the values just before saving the document. You can have your own deriving logic. Make sure that peice of code is trigger only for Sales Order create or change (VA01/VA02).
    Are you kidding???  You do realize that this is AFTER all validations against configuration, ATP, pricing, etc. have been performed??!!!  Never, ever change a critical value like plant in the SAVE user exits...

  • User exit for partner determination in delivery document

    Hi,
    Can some one suggest an user exit for partner determination in delivery document.
    We have a scenario of excluding certain plants for few of the partner determinations in delivery document..
    Please suggest
    Regards
    Ravikumar

    Hello Ravikumar,
    Please ceck if these userexits help
    Normally there are 2 userexits available in function kopierte_partner_pruefen:
       - EXIT_SAPLV09A_003
       - EXIT_SAPLV09A_004
    Regards,
    Raghavendra YN

  • Sales Area Determination in Stock Transfer Order - user exit

    Dear SD gurus,
    We have different distribution channels for inter company and intra company stock transfers; since only one sales area can be set in the configuration (setup STO -> shipping data for plants), we want to use a user exit to determine the sales area dynamically.
    We have created an enhancement of function exit V02V0001 (Sales area determination for stock transport order); but the program flow doesn't seem to stop in this exit despite setting break-points.
    Can someone suggest why this exit is not fired during runtime or if this can be used at all for our purpose.
    Regards,
    KC

    Is user exit required, as the sales area will be different. Incase of Intra company stock transfer the process will be as under:
    Create Purchase Order (ME21N)
    Create Delivery in background (VL04, VL10a, VL10C, etc)
    Change Delivery for picking / packing & PGI (VL02n)
    Create Billing Document (VF01)
    Assumption: Stock Transfer configuration is in place. Assistance can be taken from SAP Best Practices in help.sap.com
    Incase of Inter-company, the process will be as under:
    Create Sales Order (VA01)
    Create Delivery (VL01N, etc)
    Change Delivery (VL02N)
    Create Billing Document (VF01)
    Assumption: Configuration is in place. Assistance can be taken from SAP Best Practices in help.sap.com
    Regards,
    Rajesh Banka

  • User exit in VF01 for plant validation while taking the output smartform

    Hi Gurus,
    I am in a typical situation..
    We ahve a scenario where for one specific plant we need to trigger a different output type(smartform) where the billing type is being common for all plants...
    example: billing type : A00 ( same for all plants)
                  outout type (billing) : B00 ( one smartform)
                                                 C00 (another smartform)
    For all the plants, Boo triggers as the layout is same for all Except for One specific plant where it should trigger C00 i.e., different smartform i.e., layout...
    Any user exit for validating Plant at the time of saving the billing document to trigger a different outout type as above for the same billing type ???
    Please help me..
    regards
    Ravikumar

    Dear Ravikumar,
              You can do like this with out using User exit.
    -->Take field Plant in to the output condition table
    -->Put that condition table in to access sequence
    -->Define two condition type as you mentioned B00 and C00
    -->Assign access sequence to that condition types.
    -->Put those output condition types in the output determination procedure.
    -->Assign that output determination procedure to the billing type.
    -->Main the condition records for that conditon types with one of the key combination PLANT
    I hope it will help you
    Regards,
    Murali.

  • User Exit to check whether chapter id for Material and Plant combination is maintained while creating sales order

    Hello all,
    my requirement is, system should give error message while creating sales order, if chapter ID is not maintained for a material and plant combination.
    please suggest the user exit.

    Hi
    CASE 1 : All Plants are excisable.
    In Material master , Foreign Trade data tab-  mentioned Control code field mandatory. ( i.e nothing but Chapter ID)
    CASE 2 : Few Plants are excisable
    In the Case 2 you need to go for Enhancement
    Program Name : MV45AFZB 
    User Exit:            USEREXIT_CHECK_VBAP ( Item Level Check )
    By using above user exit you write a logic with the help of ABAPer
    Plant and Chapter ID combination table : J_1IMTCHID

  • User Exit for Partner Determination in VA01, VA02 transaction ( Sales order

    Dear All,
    I have an issue in which i need to determine partner for every change in ship to party both at header and item level during sales order creation or change.
    Can you please suggest an appropriate user exit for the same.
    I have tried
    EXIT_SAPLV09A_003
    EXIT_SAPLV09A_004
    but they get triggered only when we enter into VA01 transaction and not when the ship to party is manually changed.
    If possible i want to avoid MV45 exits as there are chances of regression due to too many different functionalities already present in my system.
    In worst case scenario please specify the place wherein i need to code in MV45 exits and what are the fields i need to change.
    Most probably i filtered out on "USEREXIT_MOVE_FIELD_TO_VBAP" but i am not 100 percent sure on this, please suggest.
    Thanks in advance
    Ronak

    Hi,
    please use User exit function: EXIT_SAPMV45A_003
    Put your coding in include: ZXVVAU05 (create it by double clicking, if not already created) and activate.
    Regards,
    Sanjay Gogikar

  • User Exits for Item Category Determination based on Item Category Usage

    Hi Gurus,
    If I need to create a new item category usage code and perform item category determination using the new item category usage code, is there a user exit or function module which is able to perform this?
    Thanks & Regards

    Hi Lawrence Tam,
             If you are going to create a new item category usage to determine an item category, you need to add a new line in transaction VOV4 for the new combination of sales document type + Item Cat. group + usage + high leve item cat. to determine the item category.
    Thanks in advance,
    Mariano.

  • BADI/User Exit suggestion - for determining Partner in PO header

    Hi All,
    I want to be able to automatically populate and determine a manual partner function within the header of a purchase order creation.
    Example, when PO is allocated against account assignment 'P' then go to the WBS element assigned and retrieve the specific partner number for partner function type XX. Then populate this into the relevant header partner function of the PO.
    Any ideas of which BADI/User exit could be used in ME21N?
    Thanks
    Steve

    Hi Steve
    Before going to search the UserExit/BADI, please remember your account assignment will be at item level and the partner will be at Header level.If you have number of line items with different account asssginments or different WBS elements under account assignment P, it is difficult to determine the partner functional at Header level.Please think on how can you build logic? There are number of BADI/Exits available for Purchase order.
    Regards
    Ramakrishna

  • User exits/ BADI for batch determination

    Hi,
    I need any user exits or BADI's which are triggered even before the batch determination is done.
    In One of my requirement ,during TO creation i need to pass, ship to KOMPH table( since SHIP TO is not available during a TO) to make it available for batch selection. Where can I do it? Please help!

    Hello Priya,
    Your post is very old but do you remember if you found a solution?
    Thank you in advance.
    Best regards,

  • What is the user exit for automatic account determination in PO

    Hi Experts
       I ned to know  what is the user exit for automatic account determination in PO
    my client needs the document type to defines Account Assignment Category.
    choosen a document type Account Assignment Category is defined automatically.  you can't choose
    a wrong  Account Assignment Category from the drop down list.
    thanks form you help.

    If this is the case than why don't you use the Transaction variant
    SHD0: http://www.mortenhjorthnielsen.dk/Security/transactionvariants.htm
    If you have knowledge of Transaction variant then you can use SHD0 tcode and generate the transaction using default type and give that transaction to user instead of ME21N so they will not have the issue.
    The exact solution for your problem is as follows
    Go to Tcode SHD0 and enter the transaction variant
    In T code field enter ME21N and then enter the ZXXXX or the name you want to keep in transaction variant field and hit create button
    This will take you to ME21N transaction and here you just enter the data but make sure you enter the A/c which you want to default.
    Once you finish system will save this one as a variant
    Every time you hit or enter the pop up screen comes here you just hit enter and whichever data you want to default that you have to select in the Popup by checking the Box
    W content and output only for your case the field XXXXXXXX should be selected for W content and output only
    Make sure you have value 1 in contents field
    If not then restart the variant again and on the ME21Nscreen reselect the invoice field
    Later exit and save (save in the object which you can transport)
    Then from SHD0 transaction select GOTO create variant transaction and here you careate the tcode and use that tcode for ME21N (e.g ZTRAN - For specifix sto)

  • Purchase order output determination thru User exit

    Hi,
    We are trying to find a way to determine the output for PO while creation (me21n) or modification (me22n).
    We do not want to maintain output condition records for each fax/print/email etc..cases.
    Can we do below thru a user exit or any other method ?
    While creating PO, an OA partner will be chosen, so instead of maintaining the output condition records,
    - user exit can access to OA's vendor master record and read Standard Comm.Method in Address section.
    - according to comm.method, the PO message should be determined..
    i.e: if comm.method is Fax, then message should be sent to OA thru Fax.
    can this be done thru an exit ?
    Thanks and Regards,
    Ocal

    Hi Stefan,
    The steps are as follows:
    Output of Purchase Order
    1. Condition Table
    SPRO > Material Management> Purchasing -> Message -> Output Control->Condition Tables->Define Condition Table for Purchase Order
    Select: 
    Purchasing Doc. Type,
    Purch. Organization,
    Vendor
    2. Access Sequences
    SPRO -> Material Management-> Purchasing -> Message -> Output Control->Access Sequences->Define Condition Table for Purchase Order
    3. Message Type
    SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Types->Define Message Type for Purchase Order
    *4. Message Determination Schemas*
    4.1. Message Determination Schemas
    SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Maintain Message Determination Schema
    4.2. Assign Schema to Purchase Order
    SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Assign Schema to Purchase Order
    5. Partner Roles per Message Type
    SPRO -> Material Management-> Purchasing -> Message -> Output Control-> Partner Roles per Message Type ->Define Partner Role for Purchase Order
    6. Condition Record
    Navigation Path: SAP Menu-> Logistics -> Material Management -> Purchasing-> Master data->Messages-> Purchase Order-> MN04-> Create
    Now you create PO (ME21N) and save it. Go to ME22N and print the PO by giving output type.
    Reward me if it helpful
    ASHOK

Maybe you are looking for