Is User Exit's support ABAP Objects?
Hi Experts,
Is User Exits supports ABAP Objects. I am planning to implement the ABAP classes in User exits to fill Query Variables.
Is it possible?
Thanks & Regards
Hi,
Yes user Exit's support ABAP Object.
But according to me if you want to use class then use the class into some generic function module, then that function module use in Exit. Its just for Cleanness and Simplicity of user Exit.
Regards,
Similar Messages
-
Hi to all,
Can any body help me in User-Exit in Hr-Abap. send me ur mail id i wil send u functional specs.
Thanks
hiddu.The most common enhancements for HR can be found in PBAS0001.
Here you will find the user exits for infotypes PBO & PAI.
http://sap.ittoolbox.com/groups/technical-functional/sap-hr/implementing-user-exit-for-it0041-452836
This link should help -
User Exits tied to Authorization Objects
Hello all,
Are there any User Exits available that are tied to authorization objects? We are talking about creating a custom authorization object for use in MM01 & MM02, and we are looking for somewhere to call the custom authorization object.
Thanks,
ChuckWe were not able to find a User Exit that met our requirements. We needed to Block the Basic Data view for certain Material Types from MM01 and MM02 for certain users.
We ended up doing it by modifying the screen sequence for those screens and blocking it for users who who had been given a certain role in SAP. -
User exit/BAdI whenever an object is saved to a transport request
Hi all,
We have a requirement to compare the object's version every time an object is attached to a TR. I found the BADI CTS_REQUEST_CHECK~CHECK_BEFORE_CREATION. But, this has the TR attributes only. Also, this is triggered only when the transport is created, not when the repository objects are attached to an existing TR.
Can you please help us with a BADI/user exit to gain control before an object is attached to new/existing TR?
Thanks in advance.
Regards,
Hema.Hi Hema,
Have you checked the BADI given in below thread
CTS Badi or User Exit
Thanks,
Pawan -
Hi all,
Please can you give me the any small example on USER EXITS in HRmodule...
thanks
poojaDear,
Tell me your requirements then i will tell you the User-Exits for thatt reuirement. Or you can the user exits in the SPRO itself under the functional Module for which you r looking for user exits.
Well some of ur requirments can be fulfilled with PM01.
RG
VM -
Populate user exit Variable with User Authorizations using ABAP?
Hi, Does anyone know of a way to populate a user exit variable (with ABAP) with the Authorization Values for a user running a report? I am turning off authorizations for our InfoProvider using RSSM and want to populate a variable instead and use the variable as a filter.
Hi Kenneth ,
You need dynamic authorization in your report .This can be done at query runtime by using exit variable and writing cmod code for the same .
This code will read authorization maintained at runtime of query in i_step = 1 and will pass input var values accordingly .
For step by step information you can access this document .
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f0f9f33c-0f17-2d10-d3a2-ae52ccd00780?quicklink=index&overridelayout=true
Hope this will be helpful .
Regards,
Jaya Tiwari -
Hi SAP gurus can u explain me on user exits?
Hi Chandrakanth,
Userexits are system modifications. The requirements of the client which can be met with Standard SAP are done with help of routines or userexits.
Userexits are nothing but a provision given by sap to write your own code/logic in the standard program.
Say for example while processing a sales order you want to check certain criteria weather they are met or not then you can use userxit_save_document_prepare.Here depending on the code you write system checks the if the criteria is fulfilling if not you can set an error or warning message in the code. This userexit is being executed just before saving of document.
one more commonly used exit is adding field in field catalog
In spro check this path Sales and Distribution-System modifications-Userexits.
Read the document provided,you will find all the exits in different processing for SD with program name and their purpose.
User exits are the enhancements provided by SAP
you can use them in transactions. Each transaction will have user exits.
If you want to use your own requirements by making your coding while the transaction is run you can use user exits.
For example if you want to run the MRP in MD02 specific to MRP controller you can user exit.
Please also refer the document below.
USEREXIT
Userxits allow us to add our own functionality to SAP standard program
without modifying it. These are implemented in the form of subroutines and hence are also known as FORM EXITs. The userexits are generally collected in includes and attached to the standard program by the SAP.
All Userexits start with the word USEREXIT_...
FORM USEREXIT_..
z..
ENDFORM.
The problem lies in finding the correct userexit and how to find it if one exists for the purpose. Once the correct userexit is found the necessary customer code is inserted in the customer include starting with the z. in the form routine.
e.g. USEREXIT_SAVE_DOCUMENT_PREPARE
Certain application like SD still provide this form of enhancement using userexit but this practice is no longer being followed for newer extensions instead they are using EXITs which come bundled in enhancement packages . Nevertheless existing USEREXITS will be supported by SAP an all the newer versions of SAP.
HOW TO FIND USEREXITS
Userexits can be found in number of ways:
1) To find userexits in SD module , goto object navigator(SE80) and select
development class from the list and enter VMOD in it. All of the userexits in SD are contained in the development class VMOD. Press enter and you will find all the includes which contain userexits in SD for different functions like PRICING, ORDER PROCESSING etc. Select the userexit according to the requirement and read the comment inserted in it and start coding.
Some examples of userexits in SD (SALES & DISTRIBUTION) are:
1)ADDING OF NEW FIELDS IN PRICING
In Pricing in SD the fields on the basis of which pricing is done are derived from the FIELD CATALOG which is a structure KOMG .This structure is used to transfer transaction data to the pricing procedure in SD and is also known as communication structure. This structure KOMG consists of two tables KOMK for Header related fields and KOMP for item related fields. The fields which are not in either of the two tables KOMK and KOMP cannot be used in pricing .Sometimes a need arises when the pricing is to be based on some other criteria which is not present in the form of fields in either of the two tables. This problem can be solved by using USEREXITS which are provided for pricing in SD. Pricing takes place both when the SALES ORDER ( Transaction VA01) is created as well as when INVOICING ( Transaction VF01) is done. Hence SAP provides 2 userexits ,one for sales order processing which is
USEREXIT_PRICING_PREPARE_TKOMP or
USEREXIT_PRICING_PREPARE_TKOMK
Depending upon which table (KOMK or KOMP) the new fields were inserted we use either of the above two userexits.These userexits are found in include MV45AFZZ of the standard SAP sales order creation program SAPMV45A.
In the case of userexit which will be called when invoicing is done ,these
are provided in the include RY60AFZZ which is in the standard SAP program SAPMV45A. The name of the userexits are same. i.e.
USEREXIT_PRICING_PREPARE_TKOMP or
USEREXIT_PRICING_PREPARE_TKOMK
These userexits are used for passing the data from the communication structure to the pricing procedure, for this we have to fill the newly created field in the communication structure KOMG for this we fill the code in the above userexit using the MOVE statement after the data that has to be passed is taken from the database table by using the SELECT statement. The actual structure which is visible in these userexits and which is to be filled for that particular field is TKOMP or TKOMK.
Before the coding for these userexits is done ,it is necessary to create a new field in either of the two tables KOMK or KOMP .For this purpose includes are provided in each of them .
To create the field in header data (KOMK) the include provided is KOMKAZ
and to create the field in item data (KOMP) the include provided is KOMPAZ.
One possible example for the need of creating new fields can be e.g. Freight to be based upon transportation zone, for this no field is available in field catalog and hence it can be created in KOMK and then above userexits can be used to fill the transportation data to it.
2) The other method of finding userexit is to find the word USEREXIT in the
associated program of the transaction for which we want to determine userexit using SE38.
3) The other method of finding userexits is to find the include in case of SD/MM applications where the userexits are located, this can be found in the SAP reference IMG generally in the subfolder under SYSTEM MODIFICATION.
Some other examples of userexits in SD are:
USEREXIT_NUMBER_RANGE
This userexit is used to assign a different internal document number to the
sales order(VA01) when it is created depending on some criteria like a different SALES ORGANIZAION(VKORG) .
USEREXIT_SAVE_DOCUMENT_PREPARE
This userexit is used to insert the ABAP code which will be called when
the document (sales order VA01) is just about to be saved. This userexit is used generally for custom checks on different fields , to display some information before the order will be saved or for making changes to certain fields before the sales order will be saved.
Exits & Enhancements
There are mainly six types of EXITs in sap which have been collected in the form of enhancement packages and attached to standard code in SAP.
These are different from USEREXIT in the way that they are implemented
in the form of FUNCTIONs while in USEREXITS we use form routines for their implementation. These are also sometimes known as function exits.
These start from the word EXIT_ followed by the program name and then followed by a three digit number.
e.g. EXIT_SAPMV45A_002
This exit is found in SD in enhancement V45A0002.
TYPES OF EXITS
1) MENU EXITS
2) FUNCTION EXITS
3) TABLE EXITS
4) SCREEN EXITS
5) KEYWORD EXITS
6) FIELD EXITS
We use SAP transactions CMOD and SMOD to manage exits. Before implementing an exit, it is required to create the project by using CMOD
selecting the enhancement e.g. V45A0002 and selecting the component
(one which fulfills our need) i.e. the exit which will be implemented in SMOD and after coding has been done the project has to be activated.
An exit can be coded only once.
FUNCTION EXITS
These are used to add functionality through ABAP code. These start from the word EXIT_programname_NNN ending in a 3 digit number. No access code is required to implement any type of exit including function exits.
The function exits are called from the standard SAP program in the form
of ABAP statement
CALL CUSTOMER-FUNCTION 'NNN'
This is in contrast to USEREXITs where PERFORM statement is used to call
the required userexit.
To implement the FUNCTION EXITs first of all the project is created and a suitable enhancement package is selected and from its components the function exit to be implemented is selected and on double clicking it the exit code will appear in ABAP EDITOR(se38) where a Z include will be found and the customer code should be entered in this include.
e.g.
ADDING A DEFAULT SOLD-TO-PARTY in Sales Order Creation
To show a default sold-to-party in this field when the user creates a sales order (VA01) we can use a function exit .This function exit is located in enhancement no V45A0002 . Before we can choose the exit we have to create a project in CMOD after that enter V45A0002 in the enhancement field and click on the components. In the components you will see the exit EXIT_SAPMV45A_002. This exit is used for our purpose.
Double clicking on this exit will takes us to function builder (SE37) . This
function exit has one exporting parameters and two importing parameters, we are interested in exporting parameter which is E_KUNNR of type KNA1-KUNNR i.e. if we move the desired customer name to this structure(E_KUNNR) it will be shown in the field as the default value when we create the sales order. This function also contains a customer include ZXVVA04. This include will be used to write our custom code.
Double clicking on this include and it will prompt us that this include does not exists do you want to create this object, select yes and the include will be created .In this include we can write our own code that will fill the field E_KUNNR.
e.g. E_KUNNR = 301.
Activate the include and Activate the project. Now when ever the SALES ORDER will be created, sold-to-party field will come up with a predefined customer.
FIELD EXITS
The field exits are managed, created, activated through program RSMODPRF. The field exit is associated with a data element existing in ABAP dictionary and hence to the screen field using that data element.
The format of field exit is:
FIELD_EXIT_dataelement_A-Z or 0-9
If a particular screen and program name is not specified than the field exit will effect all the screens containing that data element.
The function module associated with field exit shows two parameters
INPUT and OUTPUT. Input parameter contains the data passed to the field exit when the field exit was invoked by the R/3, we can write our own code to change the output parameter depending upon our requirements.
Before the field exit can have any effect the system profile parameter
ABAP/FIELDEXIT in all the application servers should be set to YES
ABAP/FIELDEXIT = YES.
User exits in the SD orders. These are program names (SE38):
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 User exits in the SD orders. These are program names (SE38):
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. e 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.
SMOD is the transaction to view user exits assigned to an object.
CMOD is the transaction to change the user exits according to your requirement.
You can find user exits by looking into the phrase USER_EXIT.
Check this program to find out user exits for a transaction
TABLES: tftit,
e071,
e070.
TYPES: BEGIN OF x_tstc,
tcode TYPE tcode,
pgmna TYPE program_id,
END OF x_tstc.
TYPES: BEGIN OF x_tadir,
obj_name TYPE sobj_name,
devclass TYPE devclass,
END OF x_tadir.
TYPES: BEGIN OF x_slog,
obj_name TYPE sobj_name,
END OF x_slog.
TYPES: BEGIN OF x_final,
name TYPE smodname,
member TYPE modmember,
include(15), "Include name
END OF x_final.
DATA: it_tstc TYPE STANDARD TABLE OF x_tstc WITH HEADER LINE.
DATA: it_tadir TYPE STANDARD TABLE OF x_tadir WITH HEADER LINE.
DATA: it_jtab TYPE STANDARD TABLE OF x_slog WITH HEADER LINE.
DATA: it_final TYPE STANDARD TABLE OF x_final WITH HEADER LINE.
SELECTION-SCREEN: BEGIN OF BLOCK blk01 WITH FRAME TITLE text-t01.
PARAMETERS: p_tcode LIKE tstc-tcode OBLIGATORY.
SELECTION-SCREEN END OF BLOCK blk01.
START-OF-SELECTION.
PERFORM get_tcodes. "Get Tcodes
PERFORM get_objects. "Get Objects
END-OF-SELECTION.
PERFORM display_results. "Display Results
FORM get_tcodes.
SELECT tcode
pgmna
INTO TABLE it_tstc
FROM tstc
WHERE tcode = p_tcode.
IF sy-subrc = 0.
SORT it_tstc BY tcode.
ENDIF.
ENDFORM. " get_tcodes
FORM get_objects.
DATA: l_fname LIKE rs38l-name,
l_group LIKE rs38l-area,
l_include LIKE rs38l-include,
l_namespace LIKE rs38l-namespace,
l_str_area LIKE rs38l-str_area.
DATA: v_include LIKE rodiobj-iobjnm.
DATA: e_t_include TYPE STANDARD TABLE OF abapsource WITH HEADER LINE.
DATA: l_line TYPE string,
l_tabix LIKE sy-tabix.
IF NOT it_tstc[] IS INITIAL.
SELECT obj_name
devclass
INTO TABLE it_tadir
FROM tadir FOR ALL ENTRIES IN it_tstc
WHERE pgmid = 'R3TR' AND
object = 'PROG' AND
obj_name = it_tstc-pgmna.
IF sy-subrc = 0.
SORT it_tadir BY obj_name devclass.
SELECT obj_name
INTO TABLE it_jtab
FROM tadir FOR ALL ENTRIES IN it_tadir
WHERE pgmid = 'R3TR' AND
object = 'SMOD' AND
devclass = it_tadir-devclass.
IF sy-subrc = 0.
SORT it_jtab BY obj_name.
ENDIF.
ENDIF.
ENDIF.
*- Get UserExit names
LOOP AT it_jtab.
SELECT name
member
INTO (it_final-name, it_final-member)
FROM modsap
WHERE name = it_jtab-obj_name AND
typ = 'E'.
APPEND it_final.
CLEAR it_final.
ENDSELECT.
ENDLOOP.
*- Process it_final contents.
LOOP AT it_final.
l_tabix = sy-tabix.
CLEAR: l_fname,
l_group,
l_include,
l_namespace,
l_str_area.
l_fname = it_final-member.
CALL FUNCTION 'FUNCTION_EXISTS'
EXPORTING
funcname = l_fname
IMPORTING
group = l_group
include = l_include
namespace = l_namespace
str_area = l_str_area
EXCEPTIONS
function_not_exist = 1
OTHERS = 2.
IF sy-subrc = 0.
IF NOT l_include IS INITIAL.
*- Get Source code of include.
CLEAR: v_include, e_t_include, e_t_include[].
v_include = l_include.
CALL FUNCTION 'MU_INCLUDE_GET'
EXPORTING
i_include = v_include
TABLES
e_t_include = e_t_include.
IF sy-subrc = 0.
LOOP AT e_t_include.
IF e_t_include-line CS 'INCLUDE'.
CLEAR l_line.
l_line = e_t_include-line.
CONDENSE l_line NO-GAPS.
TRANSLATE l_line USING '. '.
l_line = l_line+7(9).
it_final-include = l_line.
MODIFY it_final INDEX l_tabix TRANSPORTING include.
ENDIF.
ENDLOOP.
ENDIF.
ENDIF.
ENDIF.
ENDLOOP.
ENDFORM. " get_objects
FORM display_results.
FORMAT COLOR COL_HEADING.
WRITE:/1(150) sy-uline.
WRITE:/ sy-vline,
2(23) 'Extension Name',
24 sy-vline,
25(39) 'Exit Name',
64 sy-vline,
65(74) 'Description',
140 sy-vline,
141(9) 'Include',
150 sy-vline.
WRITE:/1(150) sy-uline.
FORMAT RESET.
SORT it_final BY name member.
LOOP AT it_final.
CLEAR tftit.
SELECT SINGLE stext
INTO tftit-stext
FROM tftit
WHERE spras = 'EN' AND
funcname = it_final-member.
WRITE:/ sy-vline,
it_final-name COLOR COL_KEY, 24 sy-vline,
25 it_final-member, 64 sy-vline,
65 tftit-stext, 140 sy-vline,
141 it_final-include, 150 sy-vline.
WRITE:/1(150) sy-uline.
ENDLOOP.
ENDFORM. " display_results
Hope this Clarifies your Doubts and Please Reward If Really Helpful,
Thanks and Regards,
Sateesh.Kandula -
Enhancement /User Exit for logic setting call date / Horizon
Due toe planning in IP10 we have a horizon set by the system for (eks.) 80%. This is working OK for small planning intervals (i.e. up to 24 mth intervals).
However when intarval exceeds this limit we will set the call date to be maximum 30 days (for instance) ahead of the sceduled start date of the order.
Thus we need a user-defined way to manipulate / set the call date by a user exit (logic in ABAP - or by IMG settings if possible) that differs from the standard SAP setting for this date.
The question is then how we - in best practice - can do so.
Please advice if you need mor information on this issue.Hi
Find the available exits with the following program:::
*& Report ZFINDUSEREXIT
report zfinduserexit.
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).
If there are no available user exits you could go for badi's.
To search for a badi, go to se 24 display class cl_exithandler. double click on method get_instance, get a break point on case statement. execute and start the required transaction in new session. look for variable exit_name. It would show the available badi's.
Please reward if useful....
regards
Dinesh -
User exit for Previous and current system status for 5 transactions
Hi Experts
My Objective to capture the Previous and current status of system status for 5 transactions in their user exits .
Description Business Object Transaction
Production Order operations BUS2005 CO02 to edit Production Order
Maintenance Orders BUS2007A IW32 to edit Plant Maintenance Order
INTernal ORDER BUS2075 KO02 to edit Internal Order
WorkBreakdownStruct BUS2054 CJ02 To edit the WBS element
Project System Network BUS2002 CN22 to edit Network
Activities Network
For Both Production order and Project System Network Activities Network ,
i got User exit " EXIT_SAPLCOBT_001 "
But i am not sure whether we can use this or not for our purpose . When i am changing status and then saving , my break point comes to EXIT_SAPLCOBT_001 .
But can we capture JEST or JCDS related data in that user exit or How can we capture both Previous status and Current ( Means New changed status ) . For eg From Released to Technically complete etc.
I want Status changed and its immedtiate previous status.
Do i need to check Exit or BADI before and after Saving .
Thanks
Regards
Gaurav
Edited by: TheGaurav on Sep 8, 2011 10:28 AMHi Himanshu
Many Thanks for the reply .
I also had some other processing needs to be done on the basis of those status. .
So do you have any idea or how to find what all exits or BADIs i can use for all of these 5 transactions , where
i can get data for JCDS ( or JEST ) .
CO02 to edit Production Order
IW32 to edit Plant Maintenance Order
KO02 to edit Internal Order
CJ02 To edit the WBS element
CN22 to edit Network
can we use EXIT_SAPLCOBT_001 for CO02 and CN22 .
Edited by: TheGaurav on Sep 8, 2011 1:21 PM -
How to put bin information to table T_QMAT thru user exit for stock remove?
Hi,
I have already use stock removal strategy 'F' and checked the flag 'User exit active', but the value in table T_QMAT filled by the standard system not include all vendors. So I need to use stock removal strategy " " and set up the table T_QMAT by the user exit.
Do you know what is the user exit and the ABAP coding to put bin information to table T_QMAT for stock removal?
Best Regards,
Chris.Hi Chris,
You can use the exit: EXIT_SAPLL03A_005 to populate t_qmat table based on your requirements. As you have already mentioned, it is important to check the flag: User exit active in SPRO, but bear in mind the stock removal strategy has to be BLANK. If you use F, then standard SAP auto-populates the T_QMAT table.
Regards,
Narendra. -
Dear All,
Could you please tell me the general impacts of user exists in FICO with an example?. How can we use this concept in FICO module?
I request you all, please reply your values.
Thanks with regards,
RanHi,
I will give you my actual example of this aplication.
I would like configure a payment condition with 15 days out of week, but the OBB8 transaction doesn't have any field to define days of week. Only sequencial days numbers.
I have created a substituition Rule in GGB4 with a user exit. This User Exit is a ABAP logics codes in a especific SAP program. This allowed especific changes in my data field recognizing days in week.
I hope I help you.
Please, assign points for my contribution.
Rgds -
Hi all,
I have an interface program that integrates with external program that via RFC it will create Delivery document by calling standard SAP tcode "VL01N" through function module and when Delivery number is successfully created, it will update the information from the Delivery document to a Z-table accordingly.
This Z-table also collectively update information passed from the external progam to SAP.
Which then, the Z-table is used by a customised report to retrieve information and tabulate in ALV.
Kindly advise if assuming a Delivery document is reversed or deleted via standard tcode (i.e. VL02N or VL09), is there any exit I can apply to update the deletion or reversal of this document to the customised table??
Kindly advise.
Thanks.Dear PKW,
This is possible to achieve through a User Exit, where the ABAPer writes a code which will update the z table when ever data is edited for a delivery document. Presently i am not aware of any User Exit numbers, which an ABAPer or another Guru form this forum can suggest.
Happy SAPing
Venkat - Hyd -
HI
I have case which user want to limit material received of quantity.
i addon one table which structure
WERKS --plant id
MATNR ---material
ALLOW_SIZE -
allow max limit
RECEIVE_SIZE --- have received quantity
ervery time when execute MIGO_GR program, i will add this time received quanitity to table and check RECEIVE_SIZE < ALLOW_SIZE .
otherwise will give a message to user what this action be reject.
so i find a user exit:MB_CF001
and ABAP CODE as follow:
tables:ZMRP_LOT_SIZE,ZMRP_PARAMETER.
data:wa_mseg type mseg.
data:l_subrc type c.
DATA:IT_PARA TYPE ZMRP_PARAMETER OCCURS 0 WITH HEADER LINE.
DATA:IT_ZMRP_LOT_SIZE TYPE ZMRP_LOT_SIZE OCCURS 0 WITH HEADER LINE.
data:wa_zmrp_lot_size type ZMRP_LOT_SIZE.
RANGES:R_WERKS FOR ZMRP_LOT_SIZE-WERKS,
R_MATNR FOR MARA-MATNR,
R_MATKL FOR MARA-MATKL.
data:wa_mara type mara.
data:l_msg(30) type c,
g_msg(100) type c.
break john.
break fms04873.
clear l_subrc .
read table XMSEG INTO wa_mseg with key bwart = '101'.
if sy-subrc <> 0.
read table XMSEG INTO wa_mseg with key bwart = '103'.
if sy-subrc = 0.
l_subrc = '0'.
endif.
else.
l_subrc = '0'.
endif.
check l_subrc = '0'.
***lock mrp prameters table.
CALL FUNCTION 'ENQUEUE_EZ_MRP_PARAMETER'
EXPORTING
MODE_ZMRP_PARAMETER = 'S'
MANDT = SY-MANDT
MRP01 =
MRP02 =
X_MRP01 = ' '
X_MRP02 = ' '
_SCOPE = '2'
_WAIT = ' '
_COLLECT = ' '
EXCEPTIONS
FOREIGN_LOCK = 1
SYSTEM_FAILURE = 2
OTHERS = 3
IF SY-SUBRC <> 0.
MESSAGE 'parameter table is lock' TYPE 'E'.
ENDIF.
SELECT * INTO TABLE IT_PARA FROM ZMRP_PARAMETER.
loop at IT_PARA.
IF IT_PARA-MRP01 = '1'.
R_WERKS-SIGN = 'I'.
R_WERKS-OPTION = 'EQ'.
R_WERKS-LOW = IT_PARA-MRP03.
COLLECT R_WERKS.
ENDIF.
IF IT_PARA-MRP01 = '3'.
R_MATNR-SIGN = 'I'.
R_MATNR-OPTION = 'CP'.
R_MATNR-LOW = IT_PARA-MRP03.
COLLECT R_MATNR.
ENDIF.
IF IT_PARA-MRP01 = '4'.
R_MATKL-SIGN = 'I'.
R_MATKL-OPTION = 'CP'.
R_MATKL-LOW = IT_PARA-MRP03.
COLLECT R_MATKL.
ENDIF.
ENDLOOP.
LOOP AT XMSEG INTO WA_MSEG.
IF WA_MSEG-BWART = '101' OR WA_MSEG-BWART = '103'.
IF WA_MSEG-WERKS IN R_WERKS.
IF NOT WA_MSEG-MATNR IN R_MATNR.
SELECT SINGLE * INTO WA_MARA FROM MARA
WHERE MATNR = WA_MSEG-MATNR.
IF NOT WA_MARA-MATKL IN R_MATKL.
read table IT_ZMRP_LOT_SIZE with key werks = wa_mseg-werks
matnr = wa_mseg-matnr.
if sy-subrc = 0.
it_zmrp_lot_size-RECEIVE_SIZE =
it_zmrp_lot_size-RECEIVE_SIZE + wa_mseg-MENGE.
if it_zmrp_lot_size-ALLOW_SIZE <
it_zmrp_lot_size-RECEIVE_SIZE.
perform unlock_data.
perform display_info.
loop at it_zmrp_lot_size into wa_zmrp_lot_size.
CALL FUNCTION 'DEQUEUE_EZ_ZMRP_LOT_SIZE'
EXPORTING
MODE_ZMRP_LOT_SIZE = 'E'
MANDT = SY-MANDT
WERKS = wa_zmrp_lot_size-werks
MATNR = wa_zmrp_lot_size-matnr.
endloop.
CALL FUNCTION 'DEQUEUE_EZ_MRP_PARAMETER'
EXPORTING
MODE_ZMRP_PARAMETER = 'S'
MANDT = SY-MANDT.
l_msg = wa_mseg-ebeln.
condense l_msg.
concatenate 'num:' l_msg into g_msg.
l_msg = wa_mseg-ebelp.
condense l_msg.
concatenate g_msg 'item' l_msg into g_msg.
concatenate g_msg 'exceed max number'
into g_msg.
MESSAGE g_msg type 'E'.
else.
modify it_zmrp_lot_size.
endif.
else.
select single * into IT_ZMRP_LOT_SIZE from ZMRP_LOT_SIZE
where werks = wa_mseg-werks
and matnr = wa_mseg-matnr.
if sy-subrc <> 0.
perform unlock_data.
perform display_info.
loop at it_zmrp_lot_size into wa_zmrp_lot_size.
CALL FUNCTION 'DEQUEUE_EZ_ZMRP_LOT_SIZE'
EXPORTING
MODE_ZMRP_LOT_SIZE = 'E'
MANDT = SY-MANDT
WERKS = wa_zmrp_lot_size-werks
MATNR = wa_zmrp_lot_size-matnr.
endloop.
CALL FUNCTION 'DEQUEUE_EZ_MRP_PARAMETER'
EXPORTING
MODE_ZMRP_PARAMETER = 'S'
MANDT = SY-MANDT.
l_msg = wa_mseg-ebeln.
condense l_msg.
concatenate 'num:' l_msg into g_msg.
l_msg = wa_mseg-ebelp.
condense l_msg.
concatenate g_msg 'item' l_msg into g_msg.
concatenate g_msg 'exceed max number'
into g_msg.
MESSAGE g_msg type 'E'.
else.
if it_zmrp_lot_size-ALLOW_SIZE <
it_zmrp_lot_size-RECEIVE_SIZE.
perform unlock_data.
perform display_info.
loop at it_zmrp_lot_size into wa_zmrp_lot_size.
CALL FUNCTION 'DEQUEUE_EZ_ZMRP_LOT_SIZE'
EXPORTING
MODE_ZMRP_LOT_SIZE = 'E'
MANDT = SY-MANDT
WERKS = wa_zmrp_lot_size-werks
MATNR = wa_zmrp_lot_size-matnr
endloop.
CALL FUNCTION 'DEQUEUE_EZ_MRP_PARAMETER'
EXPORTING
MODE_ZMRP_PARAMETER = 'S'
MANDT = SY-MANDT.
l_msg = wa_mseg-ebeln.
condense l_msg.
concatenate 'num:' l_msg into g_msg.
l_msg = wa_mseg-ebelp.
condense l_msg.
concatenate g_msg 'item' l_msg into g_msg.
concatenate g_msg 'exceed max number'
into g_msg.
MESSAGE g_msg type 'E'.
else.
perform lock_data.
CALL FUNCTION 'ENQUEUE_EZ_ZMRP_LOT_SIZE'
EXPORTING
MODE_ZMRP_LOT_SIZE = 'E'
MANDT = SY-MANDT
WERKS = it_zmrp_lot_size-werks
MATNR = it_zmrp_lot_size-matnr.
IF SY-SUBRC <> 0.
perform unlock_data.
loop at it_zmrp_lot_size into wa_zmrp_lot_size.
CALL FUNCTION 'DEQUEUE_EZ_ZMRP_LOT_SIZE'
EXPORTING
MODE_ZMRP_LOT_SIZE = 'E'
MANDT = SY-MANDT
WERKS = wa_zmrp_lot_size-werks
MATNR = wa_zmrp_lot_size-matnr
endloop.
CALL FUNCTION 'DEQUEUE_EZ_MRP_PARAMETER'
EXPORTING
MODE_ZMRP_PARAMETER = 'S'
MANDT = SY-MANDT.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
append it_zmrp_lot_size.
endif.
endif.
endif.
ENDIF.
ENDIF.
ENDIF.
ENDIF.
ENDLOOP.
*****modify
IF it_zmrp_lot_size[] is not initial.
modify zmrp_lot_size from table it_zmrp_lot_size.
endif.
perform unlock_data.
loop at it_zmrp_lot_size into wa_zmrp_lot_size.
CALL FUNCTION 'DEQUEUE_EZ_ZMRP_LOT_SIZE'
EXPORTING
MODE_ZMRP_LOT_SIZE = 'E'
MANDT = SY-MANDT
WERKS = wa_zmrp_lot_size-werks
MATNR = wa_zmrp_lot_size-matnr.
endloop.
CALL FUNCTION 'DEQUEUE_EZ_MRP_PARAMETER'
EXPORTING
MODE_ZMRP_PARAMETER = 'S'
MANDT = SY-MANDT.
***************end
first question:
this segment code can't be debug even have set break point.
how to debug this segment.
second question:
use the same condition to execute MIGO_GR,but one usING BDC method with CALL TRANSCTION 'MIGO_GR' will go to this segment code and display message which set in USER EXIT code.
but other use TCODE MIGO_GR to receive goods and will create document successfully.
three question:
have other method will be resolve my issue.
thank you advance!close!
-
Hi ,
In Badi there can be 'n' number of implementations but in User Exit it is only one implementation,can we do the user exit as 'n' number of implementation ?
For E.g: can we write Badi under User Exit? if so how is it possible can any one plz explain detaily?
Regards,
ChalapathiHi Chalapathi,
There are two types of BADIs
1. single used BADI : we can have one implementation for single requirement. If we want to use the same implemetation for another requirement also, we can write our code in already existing implemetation, BUt we can't create seperate implementation for that requirement.
2. multiple used BADI: we can have N number of implemetations. We can implement the BADI per requirement seperately.I found it usefull when we are creating subscreen (Custom tabs) in standard screens.
USER EXITS: User exits are like ABAP Perform in standard SAP programs. We can write code directly in between FORM & ENFORM and activate it. We can use the same exit for N number of requirements by adding our code to already existing one!
If we create a new BADI (single or multiple) we can use the USER exit to write code to call our new BADI. BUT it rarely happens.
Note: As suggested by Keshav, please dont post Interview Qs in FORUM.
Reddy -
ABAP Objects available in a USER-EXIT
Dear Sir,
I am very new to ABAP / User-Exit . To learn about User-Exit , I was refereing one tutorial related to USER-EXIT implementation in VL01 (form userexit_save_document_prepare) .
Sir , in this sample User-Exit , author is referring ABAP Objects like : xlips-lgort / xlips-matnr etc .
Sir , my query is that how can we know that which objects are available which can be used in a User-EXIT . How a new user like me will come to know that object xlips-lgort can be used in this User-Exit .
Pl help me .
Regards
B MittalHi,
A user exit is similar to an function module. The difference is you can write your own piece of code in a user exit to fulfill your requirements. If you look into the IMPORT parameters of the User Exit all these variable in the IMPORT are inputs to your exit. All the variables in the EXPORT parameters are the ones that can be sent out of the exit. You can change all the variables that are present in bothe IMPORT and EXPORT parameters. Ex: If i have V_data in IMPORT as well as EXPORT then i can change the value of V_DATA from 1 to 2 and pass it to next step in the standard program.
Also you have TABLES in user exit. These can be inputs and output parameters. For example i can enter a few records in the tables parameter IT_TAB in one of the exits and change these records inside the USer Exit include and export the same to the next step in the standard transaction.
Hope this is helpful.... reward if useful.
Thanks,
Anil
Edited by: Anil Japa on Mar 20, 2008 9:27 AM
Maybe you are looking for
-
Error in redeploy to 9iAS 9.0.2 from jDev 9.0.3.1
I've been trying to follow the howto on using jDev to deploy portal applications. ( http://portalstudio.oracle.com/pls/ops/docs/FOLDER/COMMUNITY/PDK/ARTICLES/BUILD.JAVA.PORTLETS.USING.JDEVELOPER.V2.HTML ) I made it through the first part OK and deplo
-
IPhone no longer compatible with Sony ICF-C1iP Dock/Speakers
I'm a litte annoyed today. I purchased the Sony ICF-C1iP so I could use it with my first generation iPhone without the static I was getting with the iHome. However, after updating to the newest update yesterday, (August 5), the Sony ICF-C1iP no longe
-
How do i print on my hp officejet 6500 wireless from my ipad?
When i try to print with my ipad via airprinter I get a message "No AirPrinter Printers Found" I have a HP officejet 6500 Wireless, what do I need to do? This question was solved. View Solution.
-
Mac book pro will not sleep after i installed mavericks
mac book pro will not sleep after i installed mavericks the sleep indicator light stays solid and fans still run but the display turns off
-
Help with WRT54G and CenturyTel DSL
I'm hoping someone can help me out. I'm trying to set up a WRT54G with DSL service from Century Telephone. I'm running Windows XP and have been using this DSL service for several years without a router, so I know I can connect reliably. I've connec