BAPI_PR_CHANGE within user-exit

Hi friends am using the BAPI_PR_CHANGE within a user-exit while doing transfer posting in MIGO.
since its within the user-exit i am not able to write commit work or transaction commit . Is ther any other way to commit the BAPI.
Even once the documents are posted the PR changes are not updated.
Please suggest a suitable solution for this issues.

Iam using the EXIT_SAPLMBMB_001. As per my requirement in the exit am doing changes to PR's and updating the same in R/3 and also it should be updated in APO server so am using the particular BAPI. But its not updating the PR changes in r/3 or APO.

Similar Messages

Updating custom field in table EKKO within user exit when PO is saved

I am trying to update a custom field in table EKKO when a PO is saved. I am using FM EXIT_SAPMM06E_013, within enhancement MM06E005. Since EKKO is not a table that can be updated with this user exit, I am using a technic that I read about on SDN where I assign a field symbol to the calling program variable and then am able to access data within EKKO table. But when I pass this data back into the field symbol, for some reason this field is not getting saved when the PO is saved. In debug mode, it looks like this field is getting updated, but when I look in the table after the PO is saved, it is not there. My code sample is below. What I am doing wrong?
data:
CHAR(50) VALUE '(SAPLMEPO)EKKO-ZHDRCSTCENTER',
g_zhdrcstcenter like ekko-zhdrcstcenter,
FIELD-SYMBOLS <F1> type any.
if i_ekko-ekorg = '5401'.
ASSIGN (char) to <F1>.
g_zhdrcstcenter = <F1>.
move '0000113322' to g_zhdrcstcenter.
<F1> = g_zhdrcstcenter.
endif.
Thanks!
Sarah Smyth.

Firstly, have you investigated using EXIT_SAPMM06E_008 to set any custom fields you have added in the EKKO_CI / CI_EKKODB structure?.. that might work more easily.
In terms of doing an assign back into a calling program's memory, it can work but it's probably worth setting a break point in your code then stepping through watching the values in EKKO - sometimes you can find subsequent code that re-writes an earlier copy of values back into the structure, thereby preventing you doing your change... SAP does warn this method is for "internal use". Also check in your debugger that it's SAPLMEPO and not SAPMM06E you need.

Updating EKKO within user exit ZXM06U22 (EXIT_SAPLEBND_002)

I am trying to update EKKO table (2 new fields that I added to CI_EKKODB) in user exit ZXM06U22 (EXIT_SAPLEBND_002). I am populating E_CEKKO (the 2 new fields) with this information, but for some reason, it is not saving to the database (EKKO table) after I save my ME21N or ME22N transaction. The very first thing i do in this user exit is:
move-corresponding I_CEKKO to e_cekko.
Does anyone have any ideas for other code that I need to add to this user exit to get these new field values in EKKO to save to database table?
Thanks!
Sarah.

You should use SMOD enhancement MM06E005 to do this
EXIT_SAPMM06E_006, EXIT_SAPMM06E_007, EXIT_SAPMM06E_008

Error in BDC within user exit

Hi All,
I am trying to generate a BDC recording within a function exit. I have declared the BDCRECX1 include within the TOP include of the function group. But the include BDCRECX1 which actually contains all the FORMs also contains a selection-screen defined in it. I am not able to activate it because it gives me the following error "SELECTION-SCREEN statements can only be used between SELECTION-SCREEN BEGIN and END OF SCREEN (program type is not "1")" Is it because we are not allowed to define a selection screen between Function-Endfunction which defines a function exit?
Please let me know why this error is generated and the step to rectify it.

Hi Nagaraj,
What Smitha is trying to accomplish here is reuse the subroutines that are available within the INCLUDE bdcrecx1.
Smitha - You cannot re-use the INCLUDE bdcrecx1 as it is, you will have to create a copy of it and take out all the code that relates to selection screen and reference to these selection parameters within the subroutines, as selection screen can be in programs type "1" - that is executable/report programs.
I guess you will need only the subroutines FORM BDC_DYNPRO USING PROGRAM DYNPRO. and FORM BDC_FIELD USING FNAM FVAL. just copy these routines into a new include. And you can use declare BDCDATA in the global data of the Function group.
If you ask me, i guess you could just write these 10-15 lines of code within the same include of the function exit and proceed rather than taking all this trouble.
Regards,
Chen

Is the Sales Order Item User Status available in user exit MV45AFZZ

Hello,
Does anyone know if a sales order line item user status is available within user exit MV45AFZZ (USEREXIT_SAVE_DOCUMENT)?
I need to send an email when the status changes from one specific value to another specific value but I don't seem to have access to what the latest value is in this user exit.
I have found a table XTVSTAT which cntains some user status' but it's not clear which status maps to which line item.
If anyone has any suggestion please let me know.
Thanks,
Ruby

Hi,
I do need to access the values as I need to check for a specific change to the user status from value A to value B.
I have already tried debugging the user exit and searching through the available variables but the status information doesn't seem to be available.
I guess I will have to try the output determination route. Can you explain this in a bit more detail please.
Thanks,
Ruby

Hr_infotype_operation errors when called within a user exit

Hi there.
I am doing an enhancement in userexit PBAS0001 for CE using the enhancement framework.Whenever I am trying to change the payroll area in IT0001 by PA30 it has to give a message saying that 'all the assignments will change to new payroll areas do you want to continue?'if i say yes then the payroll areas for all the assignments should be chnaged to the current payroll area which I am trying to change.So after the pop up I am looping at all the assignments and calling the function module hr_infotype_operation.It gives an error Complex Application error.I debugged and saw that when it calls the function module the user exit gets triggered again and goes to the starting within the function call and hits the function module again and keep going like this.I checked the structure and all the parameters.looks fine below is the code where I am using the function module.I am trying to update IT0001 when somebody tries to change the IT0001(is that an issue??) i tried by submitting a program by calling the function module in the program.Didnt work too.Is there any way we can do it by BDC??
Check if the payroll areas are equal
    IF ls_i0001-abkrs NE new_p0001-abkrs.
If the payroll areas are not equal then generate a message pop-up with 'YES' and 'NO' buttons
      CALL FUNCTION 'POPUP_TO_CONFIRM'
        EXPORTING
          titlebar       = 'Warning'
          text_question = 'Payroll Area specified is different with other assignments.Do you want to move all the other assignments to the same payroll area?'
          text_button_1 = 'Yes'
          icon_button_1 = ' '
          text_button_2 = 'No'
          icon_button_2 = ' '
          default_button = '1'
          start_column   = 25
          start_row      = 6
        IMPORTING
          answer         = lv_case
        EXCEPTIONS
          text_not_found = 1
          OTHERS         = 2.
      CASE lv_case.
        WHEN '2'.                                 "For 'NO' button
          LEAVE TO SCREEN '2010'.
        WHEN 'A'.                                 "For 'CANCEL' button
          LEAVE TO SCREEN '2010'.
        WHEN '1'.                                 "For 'YES' button
Second Pop-up confirm
          CALL FUNCTION 'POPUP_TO_CONFIRM'
            EXPORTING
              titlebar              = 'Warning'
              text_question         = 'System will update all other assignments to the new payroll area'
              text_button_1         = 'Yes'
              icon_button_1         = ' '
              text_button_2         = 'No'
              icon_button_2         = ' '
              default_button        = '1'
              display_cancel_button = 'X'
              start_column          = 25
              start_row             = 6
            IMPORTING
              answer                = lv_case1
            EXCEPTIONS
              text_not_found        = 1
              OTHERS                = 2.
          CASE lv_case1.
            WHEN '2'.                             "For 'NO' button
              LEAVE TO SCREEN '2010'.
            WHEN 'A'.                             "For 'CANCEL' button
              LEAVE TO SCREEN '2010'.
            WHEN '1'.                             "For 'YES' button
For all the assignments read the infotype 0001 and update the payroll area
              LOOP AT lt_pernr INTO ls_pernr.
                CLEAR:lt_i0001,ls_i0001.
                REFRESH lt_i0001.
                CALL FUNCTION 'HR_READ_INFOTYPE'
                  EXPORTING
                    tclas           = 'A'
                    pernr           = ls_pernr
                    infty           = '0001'
                    begda           = new_p0001-begda
                    endda           = new_p0001-endda
                    bypass_buffer   = 'X'
                  IMPORTING
                    subrc           = lv_subrc
                  TABLES
                    infty_tab       = lt_i0001
                  EXCEPTIONS
                    infty_not_found = 1
                    OTHERS          = 2.
                SORT lt_i0001 BY endda DESCENDING.
                READ TABLE lt_i0001 INTO ls_i0001 INDEX 1.
                ls_i0001-abkrs = new_p0001-abkrs.
               lv_record = ls_i0001.
Lock the employee
                  CALL FUNCTION 'BAPI_EMPLOYEE_ENQUEUE'
                    EXPORTING
                      number = ls_i0001-pernr
                    IMPORTING
                      return = lv_return.
                  CALL FUNCTION 'HR_INFOTYPE_OPERATION'
                    EXPORTING
                      infty         = '0001'
                      number        = ls_i0001-pernr
                      validityend   = '12302006'
                      validitybegin = '12012006'
                      record        = ls_i0001
                      operation     = 'INS'
                     IMPORTING
                      return        = return.
*unlock the employee
                  CALL FUNCTION 'BAPI_EMPLOYEE_DEQUEUE'
                    EXPORTING
                      number = ls_i0001-pernr
                    IMPORTING
                      return = lv_return.
               SUBMIT zhr_infotype_operation_py_area USING SELECTION-SCREEN '1000'
               WITH p_infty = '0001'
               WITH p_pernr = ls_i0001-pernr
               WITH p_endda = new_p0001-endda
               WITH p_begda = new_p0001-begda
               WITH p_record = lv_record
               WITH p_opera = 'INS'
               WITH p_tclas = 'A'
               AND RETURN.
              ENDLOOP.
          ENDCASE.
      ENDCASE.
ENDIF.

maybe a little late, but I had found this message today (searching for different problem) but maybe the date for HR_infotype_operation might do a little problem, cause you are filling it with: DDMMYYYY but it should be YYYYMMDD so it just translate it that this is really far in the past so that might be a problem. Try sy-datum instead and for the end of validity try '99991231' dont worry, when you will update the same infotype again, the FM will end the previous infotype to previous day and the new one will get validity from sy-datum till the end ....

COMMIT WORK within an user exit

Hi every one,
I got a lill question here, can i use COMMIT WORK (AND WAIT ) within a user
exit FM, if yes is do i need any thing extra. Please help.
Thanks in advance
Jahan.

Hi Jahan,
although your question has been answered, just a few words on COMMIT WORK.
During a LUW (logical unit of work, i.e. transaction) all changes of database records are done within a so-called rollback segment of the database. That means they are visible within the current LUW but invisible to other users.
This makes it easy to do all necessary changes to all tables step by step. And if any step fails, all changes can be thrown away. Thats what we call a rollback - A rollback will just dump the rollback segment.
The reason you should not COMMIT WORK in a user exit is simply you have no idea what other database changes have already been done and what other database changes may follow after the user exit. If in one of the following steps a severe error is detected, all prior changes cannot be rolled back. COMMIT WORK means that all changes still in the rollback segment of the database will be applied and finalized to the database. The rollback segment will also be dumped that there is no chance to find out details about the changes.
An Error message (Type E or A) will automatically finish the LUW without commiting the data in the rollback segment - implicit rollback.
The end of a report not caused by any error will commit the rollback segment to the database - implicit commit.
All function modules called IN UPDATE TASK will be executed in their own update process after COMMIT or DUMPED after rollback.
All form routines called as PERFORM ... ON COMMIT or PERFORM ... ON ROLLBACK will be executed only after explicit COMMIT WORK or ROLLBACK WORK.
The addition 'AND WAIT' just means that the next program statement is not executed before all update processes started with COMMIT WORK have finished.
The general rule derived from this can be:
Never do a commit or rollback in a process which is called by another process. The only place for COMMIT or ROLLBACK is at the end of reports and transactions using CALL ... IN UPDATE TASK or PERFORM ... ON COMMIT - if you call any functions you should be aware that function modules may initiate update calls and/or form calls ...ON COMMIT/ROLLBACK. An explicit COMMIT WORK at the end of a process (or ROLLBACK WORK in case of error) will be OK.
Regards,
Clemens

User exit - Default 'V' within field BSEG-REBZG - fb01 and more

Hi experts,
I need to get the user exit so i can fill in the field BSEG-REBZG as default 'V' (picture from [User Exit in fb01|http://imageshack.us/photo/my-images/442/userexitfb01.png/])
Can anyone help me out how to do this? I've read previous threads and i did the same but i still doesn't get the V in that field as you can see in the picture above.
[Default Setting for BSEG-REBZG field in all Sales Orders|Default Setting for BSEG-REBZG field in all Sales Orders]
Regards,
Michael
<< Moderator message - Please do not promise points >>
Edited by: Rob Burbank on Dec 14, 2011 9:33 AM

i tried substitution but it doesn't seem like you can substitute that field BSEG-REBZG.
So how can you resolve this?
I seem any topics about this but not really a good result....
anyone please help?

User exit ZXPADU02 - evaluating SY-UCOMM

Hello everyone,
I am trying to display an error message whenever someone tries to create a new work schedule rule (P0007-SCHKZ) in infotype 7. However, the error message should just come up when the user is trying to save his data.
I am using user exit ZXPADU02 for this purpose. My problem is that SY-UCOMM does not seem to hold reliable data in this user exit, and SSCRFIELDS does not seem to be supported at all.
My code looks like this (only the relevant code snippet in ZXPADU02):
CASE INNNN-INFTY.
        WHEN '0007'.
      CALL METHOD CL_HR_PNNNN_TYPE_CAST=>PRELP_TO_PNNNN
        EXPORTING PRELP = INNNN
        IMPORTING PNNNN = P0007.
      CALL METHOD CL_HR_PNNNN_TYPE_CAST=>PRELP_TO_PNNNN
        EXPORTING PRELP = PSAVE
        IMPORTING PNNNN = P0007_ALT.
      IF P0007_ALT-SCHKZ <> P0007-SCHKZ
      AND IPSYST-MASSN IS INITIAL " do not warn within an info group of a personnel action
      AND SY-UCOMM = 'UPD'. " only warn when saving the data -> problem here <-
        MESSAGE 'Do not change IT7 directly or else.' TYPE 'I' DISPLAY LIKE 'E'.
        SHOW_DATA_AGAIN = 'X'.
      ENDIF.
At first glance, the above works nicely. But this is what happens when I test more thoroughly:
I create a new period in IT 7, enter a P0007-SCHKZ other than the one that was previously valid, press F11. Some warnings appear (for different reasons), which I dismiss using the Enter key. Afterwards, the above code fires, the error message is being displayed, and I am thrown back into the data screen. So far, so good.
Now I simply alter the value in the field "Weekly hours" (P0007-WOSTD) and press Enter (!). Again a series of warnings appear, including one that a dataset is going to be deleted (seeing that an IT 7-period with just the same date range already exists). I confirm that with Enter, and the data is being saved. The above code does not fire because I have only pressed Enter - but the data is being saved anyway!
Looks like a pretty erroneous behavior on the side of the SAP system. The question is whether I have a chance to do something about it in the code.

Mihir Nagar wrote:
Dear Petersen,
Your IF condition seems ok. I doubt on the message statement. Can you replace your message statement with type E.
MESSAGE 'Do not change IT7 directly or else.' TYPE 'E'.
      ENDIF.
Hope this works.
Regards,
Mihir.
I did not expect this to work, because normally you use type 'E'-messages only in certain PAI-environments, but it does the job, thank you!
make use of field IOPER of the structure PSYST to check on the infotype actions INS, MOD, COP, DEL...
In this particular case I did not care, so I did not check that. IT 7 should only be maintained through personnel actions in our case.
Next you can check with sy-ucomm field the different between "enter" and "save". With "save" sy-ucomm will be 'UPD'.
That is what I did, but as I described, there was a situation when SY-UCOMM is SPACE, but the system saved anyway due to a prior save attempt.

A/R User Exit Spec and code

The spec -
1.     Canadian tax - currently based on Freight type:   Read the country(?) Ship-from (plant jurisdiction) to Ship-to(customer jurisdiction) and the inco term on the line item of the sales order and if it's not equal to 'DDP' the line item tax classification will be set to '0' exempt. (This is freight that comes into Canada from the US)
We will look at the shipto and shipfrom txjcd on the sales order document and billing document along with the inco term logic and we will tax freight when they are both Canada
Example Scenario:
For Freight charges where the Ship from is in Canada (Bedco, Artmedco, etc) and the Ship-to is in Canada the freight will always be taxable regardless of the inco term. This is freight that ships within Canada, no boarder crossing.
2.     Regular Freight - US & Canada: If separate line item on sales order, it may be exempt from tax based upon state. revisit
a.     D.1 Freight included on the line item
i.     The freight is passed to the external system by populating the field FREIGHT. The freight amount is always included in the base amount.
ii.     An example to fill the freight using the user-exit:
iii.     In the customer pricing procedure (for example ZUSA01) enter 4 in the subtotal field of the freight condition type (OTC must have this configuration in the pricing procedure for the freight pricing conditions).
iv.     In the customer structure CI_TAX_INPUT_USER, add the field KZWI4 as in KOMP-KZWI4.
v.     In the user-exit, add the code CH_USER_CHANGED_FIELDS-FREIGHT_AM = I_INPUT_USER-KZWI4.
3.     For PO Specific A/R Tax Exemptions using material tax class of 2, pass the TAXM1 field to the ACCOUNT_NO field in Taxware
oSolution:
For PO Specific Tax Exemptions CSR will go to the line item detail Billing Tab, Tax Classification field (TAXM1) and change that to 2 One-Time Exemption. Configuration complete.
CSR will go to the Text Tab, Internal Item Notice and CSR will provide a brief description as to why that line is tax exempt.
This the code----
TABLES: KNVV, KNA1, KOMK, MLAN, T001W, KNVI.
DATA: w_taxm1 LIKE mlan-taxm1,
      i_kna1 LIKE kna1,
      c_com_tax type com_tax,
      i_komk LIKE KOMK.
*--- if this freight comes into canada from US then set TAXM1 to 0
*----otherwise set TAXM1 to 2 and apply frieght charges. Set ACCNT_CLS
*----to 'Y' each time TAXM1 is passed to ACCNT_NO.
IF KNA1-LAND1 EQ 'CA'.
IF C_COM_TAX-TXJCD_SF EQ C_COM_TAX-TXJCD_ST.
    CH_USER_CHANGED_FIELDS-FREIGHT_AM = I_INPUT_USER-KZWI4.
    w_taxm1 = 2.
    CH_USER_CHANGED_FIELDS-ACCNT_NO = W_TAXM1.
    CH_USER_CHANGED_FIELDS-ACCNT_CLS = 'Y'.
ELSEIF C_COM_TAX-TXJCD_SF NE C_COM_TAX-TXJCD_ST.
    C_COM_TAX-TXJCD_SF = C_COM_TAX-TXJCD_ST.
    C_COM_TAX-TXJCD_POA = C_COM_TAX-TXJCD_ST.
    SELECT SINGLE * FROM KNVV
                    WHERE INCO1 = KOMK-INCO1
                    AND INCO1 NE 'DDP'.
    IF SY-SUBRC EQ 0.
      w_taxm1 = 0.
      CH_USER_CHANGED_FIELDS-ACCNT_NO = W_TAXM1.
      CH_USER_CHANGED_FIELDS-ACCNT_CLS = 'Y'.
    ENDIF.
ENDIF.
ENDIF.
SELECT SINGLE taxkd FROM knvi INTO knvi-taxkd
                    WHERE kunnr = i_komk-kunwe
                    AND aland = i_komk-land1.
IF SY-TCODE = 'VA01' OR SY-TCODE = 'VA02' OR SY-TCODE = 'VA03' OR
SY-TCODE = 'VF01' OR SY-TCODE = 'VF02' OR SY-TCODE = 'VF03' OR SY-TCODE
= 'VF04' OR SY-TCODE = 'VF05' OR SY-TCODE = 'VF05'.
   SELECT SINGLE * FROM kna1 INTO i_kna1
                   WHERE kunnr = i_komk-kunwe.
   IF i_KNA1-land1 EQ 'CA'.
      C_COM_TAX-TXJCD_SF = C_COM_TAX-TXJCD_ST.
      C_COM_TAX-TXJCD_POA = C_COM_TAX-TXJCD_ST.
   ENDIF.
ENDIF.
I am able to enter the user exit, but there is no value for KNA1-LAND1 or C_COM_TAX-TAXJCD_SF or C_COM_TAX-TAXJCD_ST. Does anyone what I am missing ? Please help.
Thanks in advance !!!!
N

Hi NP ,
which User exit ur using ? Are u talking abt MIRO or VF01.
Regards
Prabhu

Sales Order Pricing User Exit Problem

Hi,
I am facing a problem related to coding in Sales Order pricing user exits. Scenario is as mentioned below:
Based on Material Entered and Sold To in Sales Order, auto determination of a manual pricing condition happens. For doing this, coding has been done in USEREXIT_PRICING_PREPARE_TKOMP by changing XKOMV table. Auto determination of the manual price is happening properly.
From Sales Overview Screen when user goes to the Conditions tab, Net Value is not getting calculated. When we navigate away to Schedule line tab and then come back to COnditions tab, Net Value is automatically getting calculated.
AM i missing something in the coding part? As the data is getting populated automatically I guess some piece of code needs to be triggered. Can anyone shed some light into this.
Thanks in advance,
thunderans.

Prabhu: After filling in XKOMV structure, I am calling FM PRICING. On doing this, the Sales Pricing is getting calculated but even then net value of order at header i.e VBAK-NETWR is not getting populated when we are in Sales Overview screen. When, I am getting into Conditions tab and coming back to Sales Overview screen, Net value is getting populated correctly. This portion of everything not getting populated at the same time is bothering me. The pricing conditon that I am filling is a manual pricing condition.
I put a breakpoint after FM PRICING which correctly populates XKOMV structure. How do I properly update Order Net Value in Sales Overview screen wihtout having to navigate to any other tab?
Nicklas: I am looping at Order line within the user exit USEREXIT_PRICING_PREPARE_TKOMP and determining price. Once all line items are processed, I am using the FM PRICING for calculating Sales Prices.
J@Y: Request to send me a bit more details into your approach.

How to find out user exit

Hi All,
How to find out User Exit in particular program.
I mean if you have one profile, how to find is there any user exits in that program.
Appreciate if any body tel answer.
Thanks & Regards,
Subbu

You could try searching the main program for "userexit_"
This would give you a list of all the available user exits within the application.
For Customer exits, you could search SMOD with a short description ex: order in the F4 help. Another way is to search for CUSTOMER-FUNCTION in the main program. You can then navigate to the enhancement in the customer function and use the Z Program in the enhancement.
http://www.easymarketplace.de/userexit.php - has a complete list.
More specifically, in case you're looking for SD exits - http://help.sap.com/saphelp_46c/helpdata/en/1c/f62c7dd435d1118b3f0060b03ca329/content.htm.

How to find the user exits and BADIS from SPRO

Hi all,
please let us know how to find the User exits or BADIS for an application from SPRO.
Regards,
Madhavi

Hi Varisetty,
Finding user exits and BAdis from SPRO can be cumbsersome. In most instances you know the standard SAP program and want to check (find) an exit called in the flow of the transaction. You can do this as follows:
For User Exit:
Put "/h" in the command box (to start debugging)
Execute your transaction
When you enter debugging - put a breakpoint at statement
CALL CUSTOMER-FUNCTION
the control will stop at all calls to User Exits
For BAdi (it's simpler)
Go to class CL_EXITHANDLER in SE24
Enter method GET_INSTANCE
Put a breakpoint in this method
Run your standard transaction - control will stop at all BAdis called within the flow since this method is used to check BAdi implementations before invoking them
Also, if you want to find enhancements by package - go to SE80, enter the package and check function groups starting with X - those contain function exits (conventional user exits). For BAdis in a package, there is normally a separate tree node (under the package) for Enhancements hence clearly identifiable.
Cheers,
Adi

Difference b/w Customer exits and User Exits

Hi,
Can anybody explain diff b/w user exits and customer exits .
How to find out and Impement the coding ..
Thanks Advance
Rohan.A

Hi Rohan,
Check this matter , this may be helpful to you.
<b>CUSTOMER EXITS</b>
The enhancement concept allows you to add your own functionality to SAPs standard business applications without having to modify the original applications. SAP creates customer exits for specific programs, screens, and menus within standard applications. These exits do not contain any functionality. Instead, the customer exits act as hooks. You can hang your own add-on functionality onto these hooks.
If you want to enhance the functionality of your SAP System, you should take advantage of the exits available in standard applications. There are two main reasons why you should use exits rather than modifying SAP software yourself. Add-ons attached to exits have the advantage that:
        They do not affect standard SAP source code
When you add new functionality to your SAP System using SAPs exits, you do not alter the source code of standard SAP programs in any way. The code and screens you create are encapsulated as separate objects. These customer objects are linked to standard applications, but exist separately from SAPs standard software package.
        They do not affect software updates
When you add new functionality to your SAP System using SAPs exits, your objects (called customer objects) must adhere to strict naming conventions. When it comes time to upgrade a to a new software release, customer objects names ensure that they will not be affected by any changes or new additions to the standard software package.
Customer exits are not available for all programs and screens found in the SAP System. You can only use customer exits if they already exist in the SAP System.
<b>User exits :</b>
1. Introduction
2. How to find user exits
3. Using Project management of SAP Enhancements
1. Introduction:
User exits (Function module exits) are exits developed by SAP. The exit is implementerd as a call to a functionmodule. The code for the function module is writeen by the developer. You are not writing the code directly in the function module, but in the include that is implemented in the function module.
The naming standard of function modules for functionmodule exits is:
EXIT_<program name><3 digit suffix>
The call to a functionmodule exit is implemented as:
CALL CUSTOMER.-FUNCTION <3 digit suffix>
Example:
The program for transaction VA01 Create salesorder is SAPMV45A
If you search for CALL CUSTOMER-FUNCTION i program
SAPMV45A you will find ( Among other user exits):
CALL CUSTOMER-FUNCTION '003'
exporting
    xvbak   = vbak
    xvbuk   = vbuk
    xkomk   = tkomk
importing
    lvf_subrc = lvf_subrc
tables
    xvbfa = xvbfa
    xvbap = xvbap
    xvbup = xvbup.
The exit calls function module EXIT_SAPMV45A_003
Hope this is helpful.
Reward all the helpful answers.
Regards

User Exit Problem in Sales Order

Hello All,
This problem is related to Sales Order.I want the system to forcibly consider another line item and calculate its pricing while saving the sales order at the last moment.
For Example in the sales order I am giving 1st Line Item Material A of quantity 10 and Unit of Measurement BT (Bottle).Then when I am pressing the save button I want the User Exit of Material B as 2nd line item to be populated at that very moment which will be forcibly included and pricing will be calculated in that sales order.The user exit should work at this level.
Now considering the above scenario please suggest solutions in SD / ABAP regarding the successful running of User Exit in the Sales Order are required to attain my requirement.
Looking forward to some valuable suggestions.
Thanks & Regards
Priyanka

Hi priyanka,
though ur requirement is a bit complex i suggest userexits in this kind of scenarios wont help..rather an additonal program needs to be inserted in the standard sales order program..but for ur reference i am sending the list of all the user exits used in price determination. and the requirements fullfilled by them.... .hope it may help u....and cater to ur requirements....
User Exits For Price Determination
u2022     USEREXIT_PRICING_PREPARE_TKOMK (module pool SAPLV60A, program RV60AFZZ)
This user exit allows you to copy additional fields for pricing in the TKOMK communication structure (header fields), which have not been provided in the standard SAP system. These fields can also be used for pricing in the billing document.
This user exit is described in detail in the "New fields in pricing" section.
u2022     USEREXIT_PRICING_PREPARE_TKOMP (module pool SAPLV60A, program RV60AFZZ)
This user exit allows you to copy additional fields for pricing in the TKOMP communication structure (item fields), which have not been provided in the standard SAP system. These fields can also be used for pricing.
This user exit is described in detail in the "New fields in pricing" section.
u2022     USEREXIT_FIELD_MODIFICATION (module pool SAPMV61A, program MV61AFZA)
You can use this user exit to adjust the display of individual lines in the condition screen by changing the display attributes of the screen fields. This does not include the display of subtotals.
This user exit is also used in order processing.
u2022     USEREXIT_FIELD_MODIFIC_KZWI (module pool SAPMV61A, program MV61AFZB)
You can change the display of subtotals in the condition screen by changing the display attributes of the screen fields.
This user exit is also used in order processing.
u2022     USEREXIT_FIELD_MODIFIC_KOPF (module pool SAPMV61A, program MV61AFZB)
You can adjust the display of subtotals in the condition screen to your requirements by changing the display attributes of the screen fields.
This user exit is also used in order processing.
u2022     USEREXIT_FIELD_MODIFIC_LEER (module pool SAPMV61A, program MV61AFZB)
You can adjust the display of blank lines in the condition screen to your requirements by changing the display attributes of the screen fields.
This user exit is also used in order processing.
u2022     USEREXIT_PRICING_CHECK (module pool SAPMV61, program MV61AFZA)
You can install additional checks to the standard checks of condition lines (e.g. maximum/minimum value).
u2022     USEREXIT_PRICING_RULE (module pool SAPLV61A, program RV61AFZA)
In the standard SAP system, it is predefined which condition categories and classes can be copied or recalculated per pricing type. You can change the predefined standard procedure for each pricing type.
u2022     USEREXIT_CHANGE_PRICING_RULE (module pool SAPMV61A, program MV61AFZA)
You can use this user exit to change the pricing type that has been predefined in the copying control table in billing.
u2022     USEREXIT_XKOMV_BEWERTEN_INIT (module pool SAPLV61A, program RV61AFZB)
This field is used in the formulas and therefore initialized before the loop for the pricing procedure starts.
u2022     USEREXIT_XKOMV_BEWERTEN_END (module pool SAPLV61A, program RV61AFZB)
Within a loop for the price components during pricing, specific values can be transferred into the communication structures in pricing to be further processed.
u2022     USEREXIT_XKOMV_ERGAENZEN (module pool SAPLV61A, program RV61AFZB)
In change mode, you can change the dynamic part of the condition record (KONVD) that is always redetermined (i.e. it is not stored in database table KONV).
u2022     USEREXIT_XKOMV_ERGAENZEN_MANU (module pool SAPLV61A, program RV61AFZB)
You can use this user exit to change the ready-for-input fields of the manually entered condition record in add mode in the condition screen.
u2022     USEREXIT_XKOMV_FUELLEN (module pool SAPLV61A, program RV61AFZB)
This user exit is always called up during a redetermination of all or individual price components. You can change the work fields of the condition line. However, this only applies to conditions that have been determined via a condition record.
u2022     USEREXIT_XKOMV_FUELLEN_O_KONP (module pool SAPLV61A, program RV61AFZB)
This user exit is always called up during a redetermination of all or individual price components. You can change the work fields of the condition line. However, this only applies to conditions that have been determined via a condition record. This may include subtotals, manually entered conditions or conditions that have been calculated with a formula.
u2022     USEREXIT_PRICING_COPY (module pool SAPLV61A, program RV61AFZA)
You can change the KONV fields for copied price components.

BAPI_PR_CHANGE within user-exit

Similar Messages

Maybe you are looking for