Change VBEP in Va02 in user exit prepare_save_document

Hi,
I want to change the field ezeit in table vbep in all lines of the order when i'm modifing a sales order, I'm trying to change it in the userexit prepare_save_document but nothing changes. How can i change that? Here is the code that i'm using:
          LOOP AT xvbep.
            xvbep-ezeit = fl-value.
            MODIFY xvbep.
            vbep-ezeit = fl-value.
          ENDLOOP.

Changing XVBEP in save_document_prepare can be tricky. You have to call some SAP routines for this and thoroughly TEST. Be careful not to resort XVBEP. here is some sample code that we used to set delivery block.
i_vbap[] = xvbap[]. "copy to custom table to avoid re-sort
loop at xvbep where lifsp eq c_zz.
    check xvbep-updkz ne updkz_delete.
    read table i_vbap with key posnr = xvbep-posnr.
    check ( sy-subrc eq 0
            and not i_vbap-grkor is initial )
           or l_abgru eq 'X'.
    read table ivbap with key posnr = xvbep-posnr.
    if sy-subrc eq 0.
      ivbap-selkz = c_x.   "select vbap line
      modify ivbap index sy-tabix.
    endif.
    read table ivbep with key posnr = xvbep-posnr
                              etenr = xvbep-etenr.
    if sy-subrc eq 0.
      ivbep-selkz = c_x.               "select vbep line
      modify ivbep index sy-tabix.
    endif.
    rv45a-s_lifsp = ''.
    perform rv45a-s_lifsp_pruefen(sapfv45p).
    loop at xvbap where posnr = xvbep-posnr
                    and updkz ne updkz_delete. "set correct VBAP line
    endloop.
    perform xvbap_lesen_allgemein(sapfv45p) using xvbap-posnr
                                                  space
                                         changing svbap-tabix.
    perform vbap_bearbeiten_vorbereiten(sapfv45p).
    perform vbap_fuellen(sapfv45p).
    perform vbap_bearbeiten(sapfv45p).
    read table ivbep1
         with key posnr = xvbep-posnr
                  etenr = xvbep-etenr.
    svbep-tabix = ivbep1-tabix.
    perform vbep_fuellen(sapfv45e).
    perform vbep_bearbeiten_vorbereiten(sapfv45e).
    vbep-lifsp = ''.
    perform xvbep_aendern(sapfv45e).
    perform vbep_bearbeiten(sapfv45e).
    perform vbap_bearbeiten_ende(sapfv45p).
endloop.

Similar Messages

Event triggering before needed in transaction VA02 as user exit is involve

Hi All,
My requirement was to put authorisation check using ABAP coding in VA02 transaction so that a particular user can delete change or modify a particular order . For this i had maintained a ztable in which authorisation was given to each user. For this i used User exit to write my code. Initially tha code was running fine.
But now whenever i run the Transaction VA02 and enter the order number and hit the enter button , a message is displayed . which shuold have been displayed while the user made changes in line item. This message was written by me , whenever the user who is not authorised to change the Line Item . But it is comming when when order is entered i.e on initial screen.
So pls Help.
Thanks & regards
Vijju.

Vijju,
You have done your code in MV45AFZB which also gets triggered on ENTER if data is changed on screen, so behavior is OK.
i run the Transaction VA02 and enter the order number and hit the enter button , a message is displayed
This should be NOT the case, it is NOT the same for me, When I open an order in VA02, CHANGE any field and then press ENTER, then only Exit gets triggered and msg should appear.
If it is appearing for you without changing any field itself, then just DEBUG and check what is the data in XVBAP/YVBAP. Check with some other data as well, I think shouldn't be the case.
Also, I feel, if you change anything and error comes on ENTER itself before SAVE , it should be actually Fine with the user and is normal with many other std transactions as well.
1 more point, your condition " IF YVBAP NE XVBAP." should be the first condition and not later, because why you want to do a SELECT if nothing gets changed.
Regards,
Diwakar

Vbep-ezeit modification using user exits

Hello experts,
I have been using userexit_save_document_prepare to modify xvbep-ezeit, but it is throwing once in a while message number v1 322.
Incorerect index structure for table IVBEP1.
This error occurs very rarely.
In my code i am modifying XVBEP and for changed items YVBEP.
Please suggest how to rectify this error ? Do i need to modify IVBEP1 table also ?
PS: Is there any other user exit/enhancement available to achieve the same result ?
also i found this note and explanation in scn forums searching for solutions.
Note 985130 - SAPSQL_ARRAY_INSERT_DUPREC in VBEP_BEARBEITEN
In your user exits and modifications, particularly user exit USEREXIT_MOVE_FIELD_TO_VBEP in include MV45AFZZ, check whether the values of one or more of the following fields are changed:
VBEP-POSNR Sales document item
VBEP-EDATU Schedule line date
VBEP-EZEIT Arrival time
VBEP-PRGRS Date type (day, week, month, interval)
VBEP-ABART Contract release type
VBEP-ABRUF Forecast delivery schedule number
If this is the case, deactivate the relevant statements or the entire modification, or exit and check whether the symptoms you observed are now gone.
Please suggest any solution. I will really appreciate it.
Regards
Ravi

Is your ERP connected to CRM system? If so, check whether the document is not archieved in CRM system in which case, system would pop up this error message.
Alternatively, if ERP is not connected to CRM but still you have this issue, then there would be some issue with regard to updation schedule lines for a particular sale order or data inconsistency in table VBEP. So as recommended in note 1932377, you may have to correct the user exit USEREXIT_MOVE_FIELD_TO_VBEP. Go through the note for more details.
G. Lakshmipathi

Schedule Line Date Changed By Standard Code After User Exit

We've implemented USEREXIT_MOVE_FIELD_TO_VBEP to conditionally change the schedule line date (it changes VBEP-EDATU) when sales orders are being created. This functions correctly when VA01 or EDI is used. However, when the order is created using BAPI_SALESORDER_CREATEFROMDAT2, standard code executing after the user exit changes the schedule line date to an incorrect value.
The user exit correctly changes the schedule line date; then later on in the execution subroutine VBEP_FUELLEN_VBEPKOM in include FV45EFEP_VBEP_FUELLEN_VBEPKOM is executed which changes the date on line 37 using the value in US_VBEPKOM-EDATU. US_VBEPKOM-EDATU is in scope in the user exit, but earlier in subroutine VBEP_FUELLEN_VBEPKOM (line 12 to be exact) this variable is updated with the value in US_VBEPKOM1-EDATU, which is not in scope during the user exit. So, USEREXIT_MOVE_FIELD_TO_VBEP doesn't have access to US_VBEPKOM1-EDATU and can not ensure that the correct value is used later on in subroutine VBEP_FUELLEN_VBEPKOM.
I noticed at the end of subroutine VBEP_FUELLEN_VBEPKOM it calls USEREXIT_MOVE_FIELD_TO_VBEPKOM. I could update VBEP-EDATU here to correct the error whenever the order is created using the BAPI, but it would be nice to have a solution that could be implemented only in USEREXIT_MOVE_FIELD_TO_VBEP without also having to implement USEREXIT_MOVE_FIELD_TO_VBEPKOM.
So my question: is there a way to update the schedule line date in USEREXIT_MOVE_FIELD_TO_VBEP where it won't be changed later in subroutine VBEP_FUELLEN_VBEPKOM when the order is created using the BAPI?

Hi Caetano,
thanks for your suggestion
Yes, we use firm zone for few of the vendors. there the system don't change the schedule lines.
Also for the stock transfer PR's there is no firm zone and the lead time is one day. in this case it changes everyday after the MRP run.
the stock transfer PR's leads to the creation of Schedule lines from the source plant. Since this PR gets changed everyday. the alerts coming out of MD07 gets changed and we really did not know if this order is delayed or not. In the source plant we use the firm zone to avoid moving the schedule line. But then the alerts are always not correct.
is there any setting which helps in not moving the PR everyday without using " start in the past"
thanks
Nagendra Kumar

Change Schedule Line category through user exit - Issue with transfer of requirements

Dear All,
There is a user exit in Sales Order program MV45AZZ - PREPARE_TO_SAVE . It is currently being used to implement code to change schedule line category based on the status of the sales order.
When Blocked , category is set to ZP, and when Released then it is set to CP.
Now, when we change ZP to CP manually through VA02, I am able to see the requirements transferred in tcode MD50.
The problem is, when user changes status of sales order from blocked to released, the userexit changes categories from ZP to CP, but the requirements are not transferred ( cannot see it in MD50 ).
I tried searching the SCN, tried googling it, its been a week now and I havent found any clear solution.
So, far what I understood is Availability Check needs to be carried out again. But I am not clear how to trigger it again.
Are there any indicators that need to be set or any internal tables to be updated or any FM to call or any other user exit to place the code in.

?? Any suggestion friends ?

Add a new line item in VA01/VA02 using user exits.

Hi Experts,
I have a problem regarding adding of line items in VA01/VA02. I was able to add a line item but my problem is, there is no validation for the added line. I want SAP to validate it before posting it to database. I'm using USEREXIT_SAVE_DOCUMENT_PREPARE for this one.
I also found out from other threads, that adding line items in XVBAP is not advisable since no checking will be done after USEREXIT_SAVE_DOCUMENT_PREPARE.
I'm thinking if I can use FM DYNP_VALUES_UPDATE on one of the user exits to add a line item in VA01/VA02 and let SAP do the checking and validation. This way, I'm sure that the added line is correct and data integrity will be maintained.
Do you have any comments/suggestions about this?
Thanks a lot,
Arman.

Hi,
I am trying to do this as well but I don't get it working...
I am able to add records to XVBAP, but those never show up in my sales order.
I have found that I should also add records to XVBEP, XKOMV and XKOMP before it will be working, but when I add something to XVBEP I do get a dump on SAVE.
I would like to ask people that managed to get this working to post the code as an example here.
Thanks and best regards,
Marnix

KE52 - Change profit centre - user exit

Hello,
I've searched high and low in transaction KE52 (change profit centre) for a user exit/badi/bte etc. and have found nothing. I need to validate that the 'Person Responsible' field is a valid SAP user. Please let me know if any of you have found a way of doing this - I'm not interested in z programs that find user exits etc.
Thanks
Richard

Hi Richard,
you could, instead of using a user-exit or BADI, use the field-exit of the domain VERAK (link to the data element) VERAPC.
I have not found any user-exit or BADI too.
Rgd
Frédéric

Trigger User-Exit userexit_pricing_prepare_tkomk while changing Billing doc

Hi Experts,
Could any one of you let me know how to identify user exit "userexit_pricing_prepare_tkomk" is getting triggered while creating Billing document or while changing Billing document.
This user exit is being triggered in both the above cases.
I looked into xvbrk-updkz. No value is getting populated in change mode of Billing document for this field.
Is there any other field which will be helpful in differentiating these 2 cases.
Thanks in advance,
Vinoth

Hi Vinoth,
refer to the following link:
Re: USEREXIT_PRICING_PREPARE_TKOMK in prog. RV60AFZZ
Hope this will help you...

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

How to implement user-exit based changes for incompletion status?

Hi,
I have to implement changes to incompletion procedure using user exit. I have found the following user exit for controlling header status.
User exit in Program RV45PFZA
In this user exit 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)
Please help, how to implement changes to incompletion procedure using user exit?
Regards,
Chamandeep

Dear,
Go to CMOD and enter the enhacement number there. U can find the enhancement number through table MODSAP. here u can enter the enhancement object which is in ur case is Program name. Then you can use the enchacement number in CMOD and create a project and export it.
RG,
VM

User exit in VA01 not triggering on change of custom field

Hello Guys,
We have custom field in SO item (VBAP) for which screen 8459 of SAPMV45A has been enhanced. Now, on the change of the custom field, user exit USEREXIT_MOVE_FIELD_TO_ME_REQ is not getting triggered.
Requirement is to change Purchase Requistion item (setting value of a EBAN field to custom field from 8459 screen) when a SO is created/changed.
Can someone please help!
Regards,
Ashish
Edited by: Ashish Kshatriya on Nov 4, 2009 8:00 PM

Hi
U can also to try to insert a new MODULE in the PAI of screen-exit where u call the user-exit USEREXIT_MOVE_FIELD_TO_ME_REQ or where u fill the header line of table EBAN just as what that exit does.
U should remember the screen-exit is "yours", so u can insert all module u need, just only save them in the following include:
- MV45AOZZ (PBO module)
- MV45AIZZ (PAI module)
Max

User-Exit to change ECR number before Save

Hi all,
I have a requirement to assign an ECR number (if it is left blank) whenever we create the ECR.
So the scenario is we go to TCode CC01 / CC31 and enter without giving the Change Number.
Now after entering all the mandatory fields, when we save, based on some conditions, i have to generate a Change number.
I have check some user-exits / BADIs which are triggered on Save. But none of them provides an option to Change the Change Number. meaning all the user-exits / BADIs have AENNR as IMPORT parameter.
Could any one please tell whether there is any user-exits or BADI that will solve my requirement.
Many thanks in advance,
Anoop R.S
Edited by: R.S.Anoop on Dec 8, 2009 4:29 PM

Hello Anoop,
Could you please let me know if you where able to resolve this issue? If yes, how?
I have a similar requirement and still working on solution for this.
Thanks in advance.
Regards,
Senthil G.

Sales Orders - Add/Delete the Partner should Trigger User Exits

Hi,
I have a business requirement to add a new partner or delete or change an existing partner so as to re-determine the route and hence re-direct the goods to appropriate shipping point. This partner is a service agent and not maintained in the Customer Master. These are freely added partners (agents) at the sales order level.
Once there is a change in the partner functional the sales order level in VA01 or VA02, the user exit logics to be called again so that the route is re-determined based on the newly added or changed partners at the sales order level.
I am just trying to provide a pop-up screen for user interaction when the sales order partners are modified with buttons 'OK' or 'Cancel'. For OK, the sales order user exits to be called again. For Cancel, the newly added partners need to be deleted.
Please suggest me a suitable solution. I hope I have made the question correct. Appreciate your help in advance.
Thanks,
Kannan.

I could Figure it out.
Thanks,
Kannan

PO outbound message control - Condition record / PO IDOC outbound user exit

Guys,
I have a system with PO outbound message control sending PO idocs to a unique plant that is set up as a customer in the partner profile. I am using a custom message type and RSEOUT00 to send my idocs with custom message type to this plant. This interface works fine. Now my requirement has changed. I need to send PO's to varying plants (depending on the plant in PO item- all items on my POs belong to same plant).
I noticed that i cannot create condition tables with PO type and Plant combination. (SAP Note 457497 .Q-34).
So I have decided to populate all my PO idocs with a generic receiving partner number '9999' and planning to change this somewhere in a user exit. I found an user exit which looks helpful.
EXIT_SAPLEINM_001 . FM
MM06E001 - Enhancement.
But somehow this exit is not triggered in during PO creation ME21N or change Me22N/Me22.
Is this because I am using a custom message type instead of standard message type ? (I still use the process codes Me10/Me11). Would this matter ? When should this user exit trigger (during creation of idocs in status 30 or when i run RSEOUT00 to sweep these idocs in status 30 to status 03) ? Any tips will be useful.
THanks.
Edited by: Shareen Hegde on Jul 21, 2008 10:13 PM

I found a OSS note -Note 457497 (Q&A # 34), which talks about the same . This was my assumption too. I was just confused because I saw plant(WERKS) in the field catalag of the access sequence.
I don't know what header field I can use to map the plant (I agree its a good idea to do this). But I have decided to do it another way. I will change the receiving partner on the control record depending on the plant in an user exit
- EXIT_SAPLEINM_001.
Thanks for your answer , Mahesh.

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

Change VBEP in Va02 in user exit prepare_save_document

Similar Messages

Maybe you are looking for