Manually trigger Availability Check in the Sales Order User Exit MV45AFZZ

Hi All,
As per the normal scenario where sales orders are created and the schedule line delivery dates are determined.
Based on some business logic for few customers we need to change the delivery priority and confirmation delivery date.
We are implementing this logic in the user exit MV45AFZZ in the routine USER_EXIT_SAVE_DOCUMENT_PREPARE.
The availability check logic is already implemented by then. Now we have scenarios where the date redetermined by the custom logic is greater than the one determined by the standard availability check done by SAP.
We have changed the values of the field VBEP-EDATU as per our logic but we still have 2 lines in the schedule line data where the requested date is greater than the confirmed date.
This can be tackled if we can redo the Availability Check.
Can someone provide pointers on how can we trigger the availability check manually in the code.
Regards,
Karthik

What was the solution?

Similar Messages

  • Customizing Availability Check in the sales order; EXIT_SAPLATPC_001, etc..

    Dear All.
    Looking for a way to automatically control what's chosen in the sales order Availability Dialog box depending upon certain conditions.
    This is the "Rule for transferring the results of the availability check", field TVTA-REVFP.
    The default is blank, which lets the user select what they want.  Under certain conditions though we do not want to display the dialog box, and just have the system automatically select "A" which is what's available on the requested date.
    Mainly I've been trying to find what REVFP translates to in USEREXIT_AVAILABILITY_IN, and EXIT_SAPLATPC_001.
    We've reviewing P_ATPCSX-RESMD, in EXIT_SAPLATPC_001.  And trying to set it to "A" in debug with no luck.
    Possibly this is too late or too early in process, or the wrong field.
    Has anyone done anything like this before or have any ideas on how to approach?
    Many Thanks!

    hey kharthik,
    i got the same requirement. hv u got the solution for this ..if so please provide me..
    Regds
    Satya

  • Retaining the old schedule lines after the ATP check in the sales order....

    Hi Experts,
    I would like to retain the old schedule lines after the ATP/GATP check in the sales order for certain conditions.
    I don't want to change XVBEP,IVBEP,VBEP contents in the user-exit..
    Is there any standard sub-routine or function module to reatain old schedule lines in the sales order so that the schedule lines will not update with the new values after the ATP check ?
    Thanks
    Rayudu

    In Include LV03VFMM, you have:
    * Userexit availability
          PERFORM USEREXIT_AVAILABILITY_IN USING DA_ATPPR.
    There may be an option to implement some logic in here. However, I tried changing the value of MVERF_POS-EINTEIL[1]-VFPKZ to initial. This will ensure that when FM AVAILABILITY_CHECK_CONTROLLER is called that the following IF statement is untrue:
    CHECK NOT P_ATPCSX[] IS INITIAL.
    as P_ATPCSX[]                     Table[0x648].....
    However, this will just mean that the 2nd confirmed schedule line (assuming we have > 1 schedule lines) will have a confirmed quantity to zero.
    EXIT_SAPLATPC_001 could also be used. However, when I removed the "X" from CHKFLG, I get the same result; the 2nd schedule line will revert to zero.
    They were the only tests I tried; I cannot think of any other ways around this....

  • Change Confirmed Qty in Sales Order User exit/ATP User exit

    HI
    We have a requirement to change the ATP Qty for certain meterials & Order Types  duing sales Order User exit(FORM USEREXIT_MOVE_FIELD_TO_VBEP.? ) or ATP User exit.( ATP...OUT?).
    Is this ok to update the XVBEP in FORM USEREXIT_MOVE_FIELD_TO_VBEP of MV45AFZZ ?
    Our requirement will be like this, for one order type ZSAL( and for certain Materials)  we need to reserve 4 qty, if any order comes with 10 qty and the confimed qty is only 6( total available stock at present) , then we should only confirm  2 qty for the other order type( For Non ZSAL Order Type), and reserve the 4 QTY for ZSAL Order Type.
    If there are multiple schedule lines for an Item, we need to reduce the qty equally( as possible) from all schdule lines.
    i.e. date1 qty 4
         date2 qty 6,
    in  this case we should confirm  Date1 QTY 2, date2 qty 4, so that the remaining 4 will be reserved for ZSAL Order type.
    Whats the Best way to achieve this ?
    Edited by: agrud agrud on Sep 8, 2011 4:01 AM

    Hi Agrud,
    Did you check the possibilities with configuration.If it is not possible with configuration then you can use that exit.Before i used this but only to display not to change any thing.
    Regards,
    Madhu.

  • PO Creation from Sales Order User Exit

    Hi,
    I have a business requirement where I need to  create a Stock Transport Order (STO) for a particular kind of sales order. I outlined different options for achieving this functionality.
    1. Trigger a workflow for creating STO.
    2. Configure it an EDI output for sales orders. Using the EDI document, create STO in the same system.
    3. Create STO using BAPI from the sales order exit 'USEREXIT_SAVE_DOCUMENT'.
    I am trying to understand the issues if I go with option of creating STO from sales order user-exit. I tested it and it is working fine. But what concerns is me transaction integrity. In other words I am trying to  execute another transaction within a transaction. Both Transactions (VA01 and ME21N/BAPI) may be trying to access same tables. Anyways I havent see any potential overlap.
    I would like to know anybody implemented such a solution?
    What could be the potential issues? Does it really affect transaction integrity?
    Thanks A Lot
    Anil

    I would also be concerned with the possibility of the order failing to update AFTER you call the BAPI.  You could create a custom output type that processes on order create for that order type.  You could add your BAPI call to the processing routine of the output type.

  • Disable Availability Check Based on Sales Order Type

    Hi All SD experts,
    Usually ( correct me if i'm wrong ) availability check is set via schedule lines item type. Is there any way that I can disable the availability check based solely on Sales Order Type ? Meaning no matter what item category or schedule lines assigned to materials, availability check will still be disable.
    Besides setting in schedule lines type, what are others config that might trigger availability check ? MRP settings ? Movement type ?
    Any valuable feedback will be great and much appreciated. A big thank you in advance.
    Warmest Regards,
    Edie

    HI EDIE
        In order for the availability check to happen,the following configuration settings are required.
    Availability check:
         a) you have to define requirement class & requirement type.
         b) you have to activate at scheduline category level
         c) in deleviry item.cat ,there is availability check off field,,,,, if  u dont mention any values here,then system checks for availability.if u mention 'x' here,then system dont check for availability.
        d) you define checking group and checking rule ,these determine how availability check is going to be performed
    MRP:
       MRP determines how material is planned,whether it is inhouse production or external procurement.MRP also determines the time taken for the material to become available for ready use.When ever an order is rised,the requirement is passed to MRP through  transfer of requirements(TOR), here MRP determines the inhouse production time or external procurement time.
    Movement Type: Movement type determines the type of material movement ,whether it is Goods Issue ,,, or ,, Goods Recipt,,,,, stock transfer between two plants etc.Movement type is determined in schedule line category level.
                      Award points if it is useful
                        Prasad.G

  • Availability check Problem in sales order according MRP sterategy

    hi,
    We are using strategy 56 for configurable final product and strategy 65
    for its variants.Requirement type is "ELV V". According this requirement type,
    it is not possible to confirm availability check and then deliver the
    sales order. We tried to mark availability check for requirement type ELV V in OVZG Tcode, but the
    following error came up: "Check against plan material can only be carried
    out w/o avail.check". Is there any setting to handle this problem to work
    with strategies 56 and 65? Is it some configuration that we forgot?
    Thanks,

    Yes, We have maintained planned del. time. and other fields also,
    My problem is that, To make assembly of material A we have two component material B and C.
    in the sales order of material A, system should check availability of component material B and C.
    please help
    vikas

  • Availability check problem in sales order

    Hi All,
    We have one material which is assembled by using two components (BOM).
    During avaiability check in sales order system should check components stock available in Stores.
    · If there is sufficient stock of the component materials is available, the availability check should report a fixed number of days to make assembly,
    · If there is insufficient stock of the component materials,  the availability check should report the longest lead time for the material which is short + fixed number of days to assembly.
    Please help
    Vikas

    Yes, We have maintained planned del. time. and other fields also,
    My problem is that, To make assembly of material A we have two component material B and C.
    in the sales order of material A, system should check availability of component material B and C.
    please help
    vikas

  • Changing Availability Checking Group in Sales Order.

    Hello Gurus:
    We changed the checking group in the material master.  The existing sales orders still shows the earlier checking group.  So how to change the checking group in existing sales order also (after it is changed in material master).  Also, once the checking group in sales order is changed, how to de-commit and re-commit material as per the new checking group.  Thanks.
    - Chetan

    Chetan,
    As you have changed Checking Group in MMR later on all ur availability check etc will be calculated as per previous MMR settings..
    Still go to OVZ9...See if your sales order has correct Check rule/Group..
    Then Go to sales order Carry out availability check again...See if Avalability Overview has changes as per your new Check Rule..
    Also Do Some R & D...
    Like test with change in quantity of line items...save and carry out avalability check gain..See if schedule line dates in Sales order Is there any change?
    See if any change is there...
    If not better create new  sales order...it will minimise your efforts and will be quicker way..
    REWARD IF U FINDS THIS AS USEFUL...
    Regds
    MM

  • Re ATP check in the Sales order

    Hi,
    I have one strange issue in SO ATP check. I have created a SO and it was cofirmed with Availability check:XX, which was maintained in material master  when the SO was created. Then I changed the Avail check to YY and did the Re-ATP check again in SO, but the system takes the old Avail check:XX.
    It takes the new Avail check if I create a new line item in the SO, but did not work for the exisitng line item.
    Regards
    Nagarajan.

    Hi Nagarajan,
    The master data changes will effect only for the future entries not for the already entered material in the sale order or any other transaction

  • Availability checking rule for sales orders

    Hi experts,
    To meet our useru2019s requirement I have switched off the availability check at the schedule line category level. But when I created a sales order the AVC is still happening. Upon checking I have noticed the availability checking group as u201C02u201D and checking rule as u201CBu201D in sales order. To my understanding the checking rule should be u201CAu201D for all sales orders. Could you please advise as to why it is happening so?

    Hi,
    I have done as what suggested and I created a new sales order. Upon checking (Sales screen --} environment --} availability) the availability checking group is 02 and checking rule is B. Please note that for the other sales document types we have, the checking group is 02 and checking rule is A

  • ATP check in the Sale order Processing and CO06 transaction (Confirm Qty)

    Hi All,
    While creating the Sale order, After performing the ATP check and saving the document i have called an user exit to make the confirmed Quantity equal to ZERO when the delivery block is set (As requested by customer). That is working fine...
    But the same confirmed Quantity of ZERO is not reflecting in CO06 transaction. Its showing the old value that the value before setting the delivery block.
    I have identified the table VBBE-VMENG which stores the confirmed quantity in CO06 transaction...
    Could you please help me know any USER EXITS or any other solution to change the confirmed quantity to ZERO in CO06 transaction also while delivery block is set in the sale order.
    Thanks &Regards,
    Navaneeth

    Hi All,
    Please help me by providing some clues on this issue...
    Regards,
    Navaneeth

  • Check if the Sales Order is credit block.

    Hello Everyone,
    I have a requirement related to third party sales order and delivery. In the first system, a sales is created and then the PO gets created. Upon the creation of the PO a IDOC gets generated. The inbound IDOC in the other system triggers and a sales order gets created. The requirement is that if sales order in the first system is on credit block then automatically the sales order in the second system should go on delivery block.
    The solution that I have thought is that when the IDOC gets created after PO generation there itself add a flag to IDOC in case of credit block in sales order. BUT HOW TO CHECK CREDIT BLOCK of the SALES ORDER IN THE CUSTOMER EXIT?
    Any help is appreciable.

    Hi Rahul,
    Need some more clarification on why sales order is created in the second system, if it is a third party process ?
    are you creating delivery from the corresponding sales order of second system to replenish sales order of first system ?
    are you using standard IDOC type for creating Sales order from PO ?, if so check the Corresponding Function module which may have user exists
    check Function module : IDOC_OUTPUT_ORDRSP
    At first system, if the sales order is credit block you can restrict creation of PR-->PO in the first system itself, this is a standard Functionality
    This would be easier than looking for user and coding in IDOC function module
    try and revert
    thanks
    santosh

  • Need All Sales Order user exit

    Neeed all Sales Order user exits

    Hi,
    Check these Exits and their corresponding Programs
    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.
    Reward points if helpful.
    Regards
    Ravi

  • ABAP: Sales Orders user-exit

    Hi all,
    I have a functional requirement and I would like to know if a simple technical solution can be applied.
    My functional requirement :
    I create a Sales Order and according the Ship-to I've populated, some custom fields in Sales Order Header have to be automatically retrieved from a specific table and displayed in the screen.
    During this process, the user can often change the Ship-to and at each time, the system has to retrieve the corresponding data and displayed them into custom fields of the Sales Order.
    I wouls like to know:
    1- if the user-exit "MOVE_FIELD_TO_VBAK" can be used for retrieving the data according the Ship-to
    2- which user-exit I can use to display in custom screen of the Sales Order, the retrieved data related to the Ship-to
    Do not hesitate to propose all possible solutions, because I'm not aware about the techncial possibilities in Sales Orders.
    Thanks in advance.
    Have a nice day!

    Hi
    The first, take in account the recommendations in SAP Note 178328 - Problems due to incorrect user exits in SD.
    Read the comments for these subroutines.
    Go to SE38 for SAPMV45A and you can see all userexits
    Other source. Look for notes in the marketplace (service.sap.com/notes) related with these userexits.
    I hope this helps you
    Regards
    Eduardo
    PD: check in include MV45AFZB the subroutines USEREXIT_CHECK* for avoid changes.
    In include MV45AFZZ, read the comments for userexit_field_modification. You can avoid modifications for some fields.

Maybe you are looking for