User Exit at the time of activity saving
Dear all,
I want to update activity constarints & date based on some logic & want to ensure that at the time of activity saving logic should triggered. I want to use user exit for this.Validation/ substitution is also one option but does not seem feasible. if you know any user exit at the time of activity saving, please share with me.
Regards,
Ashok Sangal
You requirement is to check the constrain based on scheduling . THere is not user exist I believe that may exaclty address your requirement. THan also check below two user exit.
CNEX0028 Check activity release
CNEX0029 Check network release
Ideally yhou should chekc for hte some BAPI for hte network save will help you .
Regards
Nitin P.
Similar Messages
-
User Exit at the time of saving Prod Order.
Hi All,
I need to know whether there is any exit which gets called when I save the Production Order.
In our project Serial No as well as Production Order gets created when we save the Production Order.
I have to pass "Basic Start Date" to a FM which generates Serial No.I can hit some DB table if i know
Planned Order no at the time of saving of Production Order.So i want the user exit at the time of saving Prod Order
I have also tried one program which gives all the User exits for a certain Transaction.But the user exit mentioned in that is not getting called.
Thanks in Advance,
Saket.hi,
check this exit for production order by placing a break point in it.it will work .
PPCO0007 Exit when saving production order
exit name : EXIT_SAPLCOZV_001 -
User Exit at the time of MB1A mvt type 262
Hi
I want to introduce exit at the time Process Order reversal through MB1A with mvt. type 262.
At this I require check reversal is not more than consumption qunatity.
Please suggest any one.
Regards
ARKDear ,
Tell your ABAPer to implement user exit 'CONFPI02'.Table used is 'RESB' .Or Goto SMOD and Enter MBCF* and execute , which will display you all the User exit .Search the User eixt which will be applicable in your case .
Refer this : Enhancement in MIGO for Goods Movement
Regards
JH -
User exit at the time of saving purchase order
Hi experts
There are some plants for which we need to auto GR. Is there any user exit available which will check these plants in PO at the time of saving PO document and do auto GR.
RegardsEnhancement
MEVME001 WE default quantity calc. and over/ underdelivery tolerance
MM06E001 User exits for EDI inbound and outbound purchasing documents
MM06E003 Number range and document number
MM06E004 Control import data screens in purchase order
MM06E005 Customer fields in purchasing document
MM06E007 Change document for requisitions upon conversion into PO
MM06E008 Monitoring of contr. target value in case of release orders
MM06E009 Relevant texts for "Texts exist" indicator
MM06E010 Field selection for vendor address
MM06E011 Activate PReq Block
MMAL0001 ALE source list distribution: Outbound processing
MMAL0002 ALE source list distribution: Inbound processing
MMAL0003 ALE purcasing info record distribution: Outbound processing
MMAL0004 ALE purchasing info record distribution: Inbound processing
MMDA0001 Default delivery addresses
MMFAB001 User exit for generation of release order
MRFLB001 Control Items for Contract Release Order
AMPL0001 User subscreen for additional data on AMPL
LMEDR001 Enhancements to print program
LMELA002 Adopt batch no. from shipping notification when posting a GR
LMELA010 Inbound shipping notification: Transfer item data from IDOC
LMEQR001 User exit for source determination
LMEXF001 Conditions in Purchasing Documents Without Invoice Receipt
LWSUS001 Customer-Specific Source Determination in Retail
M06B0001 Role determination for purchase requisition release
M06B0002 Changes to comm. structure for purchase requisition release
M06B0003 Number range and document number
MEQUERY1 Enhancement to Document Overview ME21N/ME51N
MELAB001 Gen. forecast delivery schedules: Transfer schedule implem.
MEFLD004 Determine earliest delivery date f. check w. GR (only PO)
MEETA001 Define schedule line type (backlog, immed. req., preview)
ME590001 Grouping of requsitions for PO split in ME59
M06E0005 Role determination for release of purchasing documents
M06E0004 Changes to communication structure for release purch. doc.
M06B0005 Changes to comm. structure for overall release of requisn.
M06B0004 Number range and document number
User exit for me21n -
User Exit at the time of saving Invoice.
Dear All,
We have a requirement in which we have to validate the Functional location type of an FL at the time of saving the invoice.
We require an user exit for Tcode FV60, FB60, ME21 and MIRO that gets triggered at the rime of saving the invoice.
Request all of you to kindly help as this is an urgent requirement.
Regards
Ajay.Hi,
Go to SE93. give the transaction code for which you want the user exit and click display.
click on the object browser.
Open the node 'Function Groups'.
search for function groups starting with 'X'.
These are the user exits.
Try each andd find which suits your requirement.
Regards,
Shashank -
BADI OR USER EXIT AT THE TIME OF SAVING THE TCODE MIGO TO UPDAT FIELD LSMNG
Hello Guru,
I am using BAPI BAPI_GOODSMVT_CREATE for GRN creation it is working fine. But i want to update DELIVERY NOTE QUANTITY (LSMNG) at the time of GRN Creation . This field is not provided in the BAPI .
What i had done i had applied BADI MB_MIGO_BADI to update this field but this badi does not call at the time of saving ( THIS BADI ONLY CALL WHEN WE ARE USING MIGO TCODE AND ON THE SCREEN WE ARE PRESSING ENTER) . so i am not able to update the field (LSMNG).
So i need a badi of user exit which can updates this field at the time of saving.
there are exit which are updating other fields at the time of saving but not this one .
Why i need the badi or userexit which will update the field at the time of saving because when we are using bapi only those badi or user exit are called which are
used at the time of Saving.
Kindly suggest any solution.
Thankyou
With Regards
Shantanu ModiHi
<b>Here is the sample code...</b>
method if_ex_mb_migo_badi~post_document .
data: ls_migo_badi_example type migo_badi_exampl,
lt_migo_badi_example type table of migo_badi_exampl,
ls_extdata type migo_badi_example_screen_field,
ls_xmseg type mseg.
field-symbols: <gt_extdata> type migo_badi_example_screen_field.
* Transaction MIGO will now post a material document.
* Any errors here MUST be issued as A-message (better: X-message)
* Copy data from material document into internal table
loop at gt_extdata into ls_extdata.
if g_cancel is initial.
read table it_mseg into ls_xmseg
with key line_id = ls_extdata-line_id.
else.
read table it_mseg into ls_xmseg
with key smbln = ls_extdata-mblnr
smblp = ls_extdata-zeile
sjahr = ls_extdata-mjahr.
endif.
if sy-subrc is initial.
move-corresponding ls_extdata to ls_migo_badi_example.
move-corresponding ls_xmseg to ls_migo_badi_example.
append ls_migo_badi_example to lt_migo_badi_example.
endif.
endloop.
* The data from external detail screen can be saved now:
check gt_extdata is not initial.
call function 'MIGO_BADI_EXAMPLE_UPATE_DATA' in update task
tables
it_migo_badi_example = lt_migo_badi_example.
* The data from external header screen can be saved now:
move-corresponding is_mkpf to gs_exdata_header.
call function 'MIGO_BADI_EXAMPLE_UPDATE_HEAD' in update task
exporting
is_migo_badi_header_fields = gs_exdata_header.
endmethod. "IF_EX_MB_MIGO_BADI~POST_DOCUMENT
Hope this will help.
Please reward suitable points.
Regards
- Atul -
User Exit at the time of Saving in Vendor Master
Hi,
I am trying to put a check through Enhancement "SAPMF02K" in Vendor Master to make Tax No fields as Mandatory for to some particular Company Code and Account Group.
But the problem is enhancement triggers at the time of saving, so what ever error message check i have implement will trigger at the time of saving the data. Now my requirement is it should trigger to the screen where i need to maintain the fields, instead of the error showing in the last screen ( As user need to check in which screen he/she need to maintain these fileds in the list of screens by going back).
Please reply with the appropriate solution.
Regards,
NSKHi Shashi,
Did you check with your functional side. It is possible with configuration.
Regards,
Madhu. -
Need User Exit before the Purchase Order saved!!!
Hai All,
I am in search for User Exit before the Purchase Order gets saved.This User Exit should capture this generated Purchase Order and post it to the Destination System for further processing.
Can anyone help me to find this User Exit.
Thanks,
Ugandhar.<b></b><b></b>
Message was edited by: Ugandhar DomathotiCheck out this enchancement in smod <b>MM06E001</b>
in that EXIT_SAPLEINM_001
EXIT_SAPLEINM_002
may help you ....
regards
vijay -
BADI / User exit for Purchase order(ME21N) after saving the document
Hi expert,
I need the BADI / User exit for Purchase order(ME21N) after saving the document
This is for email sending after create the purchase order so PO document number will be the import parameter
pls help me
point will be reward
Regards,
GaneshHi Ganesh,
Could you please share your solution?
Thanks.
Hoops
Edited by: Hoops on Jun 13, 2011 10:51 PM -
User Exit in the Sales order create BAPI
Hi,
Can some one help me in telling if there exists a user exit for the BAPI '/AFS/BAPI_SALESORDER_CREATE'.
This is urgent. So, pls. throw some light on this.
Thanks in advance.Hi
User Exits In Sales Document Processing
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. -
SAP ISU - User exits at the end of move-in process
Hi,
We have a requirement to send some outbound messages on completion of Move-in process in SAP ISU system. And send some outbound message on completion of Reverse Move-in process.
I tried to find the customer/user exit in transaction EC50E and EC53E, all i could find is user exits during the process. I need something at the end of process.
At the moment all I can do is use the events raised when these process are completed (Ex: MOVEINDOC.Created) and start a workflow to send outbound messages. But i would want to know if there are any exits available at the end of the processess as I dont want to create a workflow just for one activity.
Any inputs will be appreciated.
Many Thanks,
Anandvery old item - closed
-
FB70: User exit when the save button (for posting) has been click
Hi ABAP Gurus,
With regard to FB70, can anyone provide me the name of the user exit that will be triggered when the save button (for posting) has been clicked?
Thanks!
<b>
Best Regards.
Brando</b>Hello Brando,
With FB70 I recommend you implement the user-exit via the Business Add-In (BADI) way and avoid SMOD exits if possible.
The list below are the BADIs that are called by the <b>ECC6.0</b> system after you click the <b>Save</b> button to post a document. <u>They are listed in the order which they are called before the actual post</u>. You'll have to find the right one as per your requirement - you can view their definition via transaction SE18 then after you find the right one you need to use that definition to create an implementation via SE19. Here again, you'll have to choose the right method that suits your requirement. You'll find the method and class documentation in some cases with examples on how to implement, you need to write the code between the Method..EndMethod statement using the parameters provided by the Method.
1. PPA_CUST_BADI
2. FI_RES_ITEM_CURRENCY
3. AC_QUANTITY_GET
4. BADI_PRKNG_NO_UPDATE
5. FM_POP_CORE
6. FMRI
7. FMRE_BUS_PROCESS
8. FAGL_SET_SEGMENT
9. EXIT_XFMPR1_001
10. BUAVC_CHECK_RESTRICT
11. UKM_R3_ACTIVATE
12. CO_DOCUMENT_INFO
I spent a bit of time debugging FB70 to find this info for you, please appreciate by rewarding points (or else
Good luck.
Cheers,
Sougata. -
User exit before the call of FM CCARD_AUTH_SIMULATION
HI Gurus
I wanna know if there is any user-exit before the call of FM CCARD_AUTH_SIMULATION, for the structure XVBAK.
I want to manipulate with the document category for that particular order before the order is saved.
If anyone can provide me the user exit for the structure XVBAK then it will be helpful to me.
Thanks
Swarngo for implicit enhancement option.
Reddy -
User exit for the release of Purchase Order
Hi Friends,
I am searching for a user exit which should trigger at the time of Purchase Order release in ME29n transaction.
If anyone can help me for the same....!!!
I need the exact exit which triggers at the release of PO....
Points will be rewarded for the needful replies.
Regards,
Mandeep.HI,
Finding the user-exits of a SAP transaction code
Enter the transaction code in which you are looking for the user-exit
and it will list you the list of user-exits in the transaction code.
Also a drill down is possible which will help you to branch to SMOD.
report zuserexit no standard page heading.
tables : tstc, tadir, modsapt, modact, trdir, tfdir, enlfdir.
tables : tstct.
data : jtab like tadir occurs 0 with header line.
data : field1(30).
data : v_devclass like tadir-devclass.
parameters : p_tcode like tstc-tcode obligatory.
select single * from tstc where tcode eq p_tcode.
if sy-subrc eq 0.
select single * from tadir where pgmid = 'R3TR'
and object = 'PROG'
and obj_name = tstc-pgmna.
move : tadir-devclass to v_devclass.
if sy-subrc ne 0.
select single * from trdir where name = tstc-pgmna.
if trdir-subc eq 'F'.
select single * from tfdir where pname = tstc-pgmna.
select single * from enlfdir where funcname =
tfdir-funcname.
select single * from tadir where pgmid = 'R3TR'
and object = 'FUGR'
and obj_name eq enlfdir-area.
move : tadir-devclass to v_devclass.
endif.
endif.
select * from tadir into table jtab
where pgmid = 'R3TR'
and object = 'SMOD'
and devclass = v_devclass.
select single * from tstct where sprsl eq sy-langu and
tcode eq p_tcode.
format color col_positive intensified off.
write:/(19) 'Transaction Code - ',
20(20) p_tcode,
45(50) tstct-ttext.
skip.
if not jtab[] is initial.
write:/(95) sy-uline.
format color col_heading intensified on.
write:/1 sy-vline,
2 'Exit Name',
21 sy-vline ,
22 'Description',
95 sy-vline.
write:/(95) sy-uline.
loop at jtab.
select single * from modsapt
where sprsl = sy-langu and
name = jtab-obj_name.
format color col_normal intensified off.
write:/1 sy-vline,
2 jtab-obj_name hotspot on,
21 sy-vline ,
22 modsapt-modtext,
95 sy-vline.
endloop.
write:/(95) sy-uline.
describe table jtab.
skip.
format color col_total intensified on.
write:/ 'No of Exits:' , sy-tfill.
else.
format color col_negative intensified on.
write:/(95) 'No User Exit exists'.
endif.
else.
format color col_negative intensified on.
write:/(95) 'Transaction Code Does Not Exist'.
endif.
at line-selection.
get cursor field field1.
check field1(4) eq 'JTAB'.
set parameter id 'MON' field sy-lisel+1(10).
call transaction 'SMOD' and skip first screen.
*---End of Program
USE THIS PROGRAM TO GET ANY USER EXIT BY GIVING THE TCODE.
MMFAB001 User exit for generation of release order
MRFLB001 Control Items for Contract Release Order
REGARDS,
PRIYA.
Edited by: Priyadharshini Veluswamy on Mar 13, 2008 9:21 AM
Edited by: Priyadharshini Veluswamy on Mar 13, 2008 9:40 AM -
Dear SAP GURUS
When the sales order is created and saved , the business wants a pop up to show asking whether you want to save the order or cancel.
Please suggest how this has to be achieved using a user exit and the coding
regards
SIMHi,
The requirement is fairly simple and need to be just triggered into the program SAPMV45A.
The code is to put into a subroutine called. PERFORM USEREXIT_SAVE_DOCUMENT_PREPARE.
Write the code in the form of the same subroutine and get the job done. Am sure that it'll be a smooth sail.
Reward points if useful.
Thanks,
Tej..
Maybe you are looking for
-
Mis match in attributes of item category B-limit and PO item details
Hi I could not able to create a Blanket PO with document type FO and item category B (limit). Normally for a blanket PO, GR is not allowed and IR is mandatory. So, I could able to see these checkboxes for GR (not set and grayed) and IR (set and graye
-
I cant update my ipod touch 3rd generation
when I try to update the IOS version on my ipod touch 3rd gen. it goes through the whole process then says "unkown error occurred (-1.) unable to restore ipod" it only has IOS 2.2 so I cant download any games or apps, it wont even let me download ibo
-
Firefox won't open. No error messages, no processes in task manager.
Thought it might be an update issue as I was running FF 3.x when this issue started. I updated to 4.0 last night and it hasn't changed anything. FF opened and ran once, now not at all. No error message, no running process in task manager. Double clic
-
Do I need NI card to use DAQmx in my c# ?
Do I need NI card to use NI-DAQmx to get measuring from Foundation Fieldbus device in my c# application? Connection to FF device is via USB Fieldbus Interface.
-
Should I wait to buy my iMac when apple upgrades it to support 802.11ac Wi-Fi ?
Since apple released the Macbook air that supports 802.11ac wi fi, is it going to do the same with all the others products? Being so, I understand that if I by an imac today, it will not support 802.11ac. And this imac will not make the most out of t