Regarding Exit of validation in SPRO

Hi All,
Normally for user exits the system should not ask for the Access key. But the exits of validations in tcode 'SPRO' it is asking for the acess key. It is creating some sort of confusion.plz clarify.
Regards
Prashanth

Hi prashanth,
1. customer exits (using CMOD, SMOD)
won't ask for access key.
2. But user-exits, (especially in SD Module)
   have some Z INCLUDE,
   which needs to be modified,
   for writing our code.
So, only for the first time, it will ask for access key.
regards,
amit m.

Similar Messages

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

BADI/User Exit for validation in WAK1

Hi,
I need to put validations in transaction WAK1.
for the Site Groups under the site groups TAB.
Please suggest if any BADI or User Exit is available to do this.
I checked there are BADI's "WAKT_BADI_001" to "WAKT_BADI_008" but they are for SAP Internal Use only.
Regards
Ankur

Hi
Below are some of BADIs available for WAK1. Please check.
Exit
WCOUP001 User exit for coupon processing in POS inbound
BADIs
RDM_BAPI_PROMO_CREATE - Enhancement Spot (RDM_OPT_PROMO_IN)
RDM_PROMO_POST - Enhancement Spot
RDM_PROMOTION_WAK1 - Enhancement Spot
WAKT_BADI_001 -
~~~Ganesh Kumar K.

FBCJ BADI/User Exit or Validation Rule Implementation

Inspite of my maintaining validation as under, i am not able to achieve what i desire, i.e., System is still posting Cash transactions thru FBCJ t code for amount exceeding INR 50,000
1. Created a validation name
2. Assigned it to Application Area - FI
3. Callup Point - 2 Line item
4. In validation step 0001, created pre-requisite as
Transaction code = 'FBCJ' AND Account Type = 'D' AND
Posting key = '15'
5. Under check, Amount <= '50000.00'
6. Entered E in message type with corresponding message class ZKM_MSG_CLASS for message number 018
7. Assigned the above validation in OB28 t code for activation level 1 (i.e., Active)
System display a message; but also post it as well, despite of 'E' error message type.
How to tackle with the above problem.
Is there any other badi/user exit for FBCJ. I have only find CJ_DOCUMENT, but it's not working for me.
Thanks and Regards,
Sohail

Hi
Below are some of BADIs available for WAK1. Please check.
Exit
WCOUP001 User exit for coupon processing in POS inbound
BADIs
RDM_BAPI_PROMO_CREATE - Enhancement Spot (RDM_OPT_PROMO_IN)
RDM_PROMO_POST - Enhancement Spot
RDM_PROMOTION_WAK1 - Enhancement Spot
WAKT_BADI_001 -
~~~Ganesh Kumar K.

Use of field exit for validation of KNTTP in ME51N

Hi All,
I've a client who is still running on SAP 4.6C. There is a requirement to validate the Account Assignment Field KNTTP based on the document type, and if the validation fails, to raise an error message. As there is no standard user exit that I've been able to find for this field, and we don't want to modify standard screens, I've created a field exit against the KNTTP field and generated the FM FIELD_EXIT_KNTTP, and activated it, but it doesn't work.
As this is the first Field Exit I've coded could someone please assist me with understanding the following: in the parameters list is the value of INPUT the value of, in this instance, the KNTTP field and also is it possible to read other screen data within this FM, for example, if the KNTTP value eq 9, can I read the BSART field of the current transaction, and if so, how do I reference it (BSART, EKKO-BSART, MEREQ_TOPLINE-BSART, parameter id BSA, etc)?
Any suggestions on how to debug the process would be greatly appreciated as well.
Any help would be greatly appreciated.
Regards,
Steve

Due to lack of assistance, we were unable to pursue this requirement - the users were not happy, but what can you do, huh!

User Exit CATS0002 Validation

Hi Gurus,
I need to validate a field in cat2 transaction for a field . if the user enters a value other 1 then i need to validate that field providing an warning message "Number of days should not exceed 1 for a given date".
and then user should input the proper value (i.e, 1).
I incorporated this validation in User Exit CATS0002 CATS: Supplement recorded data.
in which i need did the validation for enrich_table-catsquantity as mentioned below.
IF enrich_table-catsquantity > 1.
      MESSAGE w667(lr) WITH 'No.of days'
                            'should not'
                            'exceed 1 for'
                            'a given date'.
       ENDIF.
1. If this condition becomes true the message will be triggred. then after executing this message staement will it alow the user to enter proper value ?
2. any other method of validating ?
Please help regarding this.
Thanks
ramu

Hi Kiran,
This sounds very interesting to me and I would like to learn more about the use case.
But first I need more information about your system landscape.
Do you run the use case on NW 70 EhP 1 or 2?
I strongly recommend NW 7.0 EhP 2 and I am convinced you get it done easily with BRFplus.
Calling BRFplus rules can be achieved by RFC or WebService call or locally in ABAP. Maybe take a look at a package called SFDT_DEMO_OBJECTS.
BR,
Carsten

USER EXIT for Validation

Dear All,
We have two user group for creating the Sales Order.They are
1. Sales order creation (Real ) and 2. Sales Order creation (Virtual ).
Our requirement is that a user(s) belonging to Real must be able to create Virtual SALES ORDER   and vice versa.
We have identified the table and the field as mentioned below.
Table is VBAK ( Transaction Code : VA01 & VA02), & Field is ZZSO_SORT.
As we are planning to write a Validation in FI as per the below logic.
Validation 1.
IF T.CODE ; VA01 or VA02 and User id isXXXXX ( REAL group),then check ZZSO_SORT = REAL (hard code value)
Validation 2.
IF T.CODE ; VA01 or VA02 and User id isXXXXX ( VIRTUAL group),then check ZZSO_SORT = VIRTUAL (hard code value)
But we don't have the table VBAK( and also the feild ZZSO_SORT) in FI validation (OB28),so we have to write an user exit.
As we have fever knowledge about writing a code for user exit( as per above logic) and assigning the same to the respective Validation,it will great,if some one can assist us to achieve our target.
Thanks for your time and patience.
Regards,

Hi
I don't know where the information for that field is from
Validation 1.
IF T.CODE ; VA01 or VA02 and User id isXXXXX ( REAL group),then check ZZSO_SORT = REAL (hard code value)
Validation 2.
IF T.CODE ; VA01 or VA02 and User id isXXXXX ( VIRTUAL group),then check ZZSO_SORT = VIRTUAL (hard code value)
The field VBAK-ZZSO_SORT can be filled programatically by the user-exit USEREXIT_MOVE_FIELD_TO_VBAK (include MV45AFZZ):
FORM USEREXIT_MOVE_FIELD_TO_VBAK.
IF T180-AKTYP = 'H' OR                                    "---->VA01
     T180-AKTYP = 'V'.                                      "---->VA02
    IF SY-UNAME = <......>.
      VBAK-ZZSO_SORT = 'REAL'.
    ENDIF.
    IF SY-UNAME = <......>.
      VBAK-ZZSO_SORT = 'VIRTUAL'.
    ENDIF.
ENDIF.
ENDFORM.                    "USEREXIT_MOVE_FIELD_TO_VBAK
Otherwise it needs to know who/what inserts the value of VBAK-ZZSO_SORT in order to decide where the control has to be placed.
Max

User exit or validation to check plant in FI entry

Dear Experts,
I have one business requirement that at the time of vendor invoice verification throgh FB60 or credit memo system should check that the vendor is existing for the particular plant or not from LFM2 table.
So please help me if there is any validation or user exit is there which we can use for the same.
Thanks & Regards,
Hansa Chechani

Dear expert
please go through below link it may help you
Copy Credit Memo request from Invoice
Regards
Ajeesh

How does the user exit of validation rules get triggered?

SPRO
FinancialAccounting> GL Accounting > Business Transaction > GL posting > Carry out doc settings > Validation in accounting docs
Here you can specify rules and call user exits also.
To add code into the user exit, we have to copy the standard program that contains this user exit and then create a z version?
If so, where do you tell to branch into the custom z program and not the standard program?

Go to transation GGB0(Change Validation), Go to Application Area/Time -> Financial Accounting -> Line Item. Create a validation what ever you want and add the steps/rules for that. You have a provision to give Rules/Exits(User Exit).

User Exit for Validity Date for VA41 Tcode

Hi,
I am giving order type in VA41 Tcode and then Clicking on 'Create with Reference' .Then a Pop Up is getting generated. In this i am giving Contract created with validity date lessthan today's date(in Contract Tab).For Example i created a Contract xxxxxx with 'valid to' 9.12.2008. When I am giving this contract and clicking on 'Copy' button a Warning message is getting generated 'The sales document is only valid until 09.12.2008'. Now i have to change this into Error message instead of Warning Message.
i used User Exits mv45afzz,MV45AFZA,MV45AFZB. But the debugger is getting started only after Warning message got generated.Is there any User Exit for which debugger gets started when i give the Contract and then Click on 'Copy' button. Please Suggest.
Thanks and Regards
K Srinivas

Hi,
One idea. Go to VTAA (copy between sales docs) and create a new VOFM where you manage the copy control. Set a warning/error message in the new VOFM (in your range number), and try it.
Regards,
Eduardo
Edited by: Eduardo Hinojosa on Dec 10, 2008 3:58 PM

My exit in validation exit dont execute for fb02

Hi guys,
Validation in field BSEG-ZLPRS for FB02 transaction.
1.- i add new form in se38 -> ZGGBR000
FORM u105 CHANGING b_result.
BREAK-POINT.
DATA: znolib LIKE zliber-znolib.
SELECT SINGLE znolib
    INTO znolib
    FROM zliber
    WHERE bukrs = bseg-bukrs AND
          username = sy-uname.
IF sy-subrc <> 0.
    b_result = b_false.
    MESSAGE i031(z001) WITH sy-uname.
ELSE.
    IF znolib = 'N'.
      b_result = b_false.
      MESSAGE i031(z001) WITH sy-uname.
    ELSE.
      b_result = b_true.
    ENDIF.
ENDIF.
ENDFORM.
2.- After activated i use RGUGBR00 for rebuilding validation structures
3.- The condition is SYST-TCODE = 'FB02', cause there is no specific condition, we need to check thhis field for all circunstances
I have all ok in ggb0
Best regards
Jua

Not solved yet...
in table GB01 i have:
BOOLCLASS = 9
CLASSTYPE = B
BLCTAB = BSEG
BCLFIELD = *
BEXCLUDE = ' '
Since i am not sustituying the field only validating its not necessary to change....
But my exit still not working
Best regards
Juan

User exit for validation of field NEWKO in f-48 tcode in finance

hi,
Previously we validated the Field XBLNR (Reference) in the document header from the table EKKO, for the PO Number. now we want to validate the vendor number(LIFNR) in the field NEWKO from the table EKKO with reference to the PO number entered in the field XBLNR.
we want to find out the correct user exits or any enhancement for the above validation.
pls help me in this regard ,matter most urgent.
Thanks & regards
veera

hi,
for f-48 you could use FI-validation with tcode OB28
use an exit (UK...) for your check in Program ZGGBR000
A.

Help Regarding Exits

Hi, Please explain me the uses of User Exits?
and where we have to create them?
What are types of Exits?
Thanks
Please explain me
thanks and regards
Dinakar

MODIFICATIONS : Change to the standard functionality by changing the SAP object itself using the 'ACCESS KEY ' from SAP .
These objects needs to be observed during version upgrades as the upgrade patches might overwrite the code written by you .
Except for certain incode user exits provided by SAP like MV45AFZZ .
ENHANCEMENTS : Change to the standard functionality by using the exits / badis provided by SAP.
These objects do not need any access key from SAP.
These changes will not get over written during SAP version upgrades.
MODIFICATIONS : Change to the standard functionality by changing the SAP object itself using the 'ACCESS KEY ' from SAP .
These objects needs to be observed during version upgrades as the upgrade patches might overwrite the code written by you .
Except for certain incode user exits provided by SAP like MV45AFZZ .
ENHANCEMENTS : Change to the standard functionality by using the exits / badis provided by SAP.
These objects do not need any access key from SAP. These changes will not get over written during SAP version upgrades.
USER EXITS->
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>
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
CUSTOMER EXITS-> t-code CMOD.
As of Release 4.6A SAP provides a new enhancement technique, the Business Add-Ins.
Among others, this enhancement technique has the advantage of
being based on a multi-level system landscape (SAP, country versions, IS solutions, partner,
customer, and so on)
instead of a two-level landscape (SAP, customer) as with the customer exits.
You can create definitions and implementations of business add-ins at any level of the system landscape.
To unify enhancements of the SAP Standard you can migrate customer exits to business add-ins.
http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/content.htm
In order to find out the user exits for any tcode,
1. get the developement class of the tcode from SE93.
2. Now goto transaction SMOD and press F4,
3. give in the Deve class in the dev class and Press ENTER
this will show u the exits for any tcode.
or execute this report
http://www.erpgenie.com/sap/abap/code/abap26.htm
which gives the list of exits for a tcode
http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec079f5db911d295ae0000e82de14a/frameset.htm
For information on Exits, check these links
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sapgenie.com/abap/code/abap26.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
http://www.easymarketplace.de/userexit.php
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sappoint.com/abap/userexit.pdfUser-Exit
Difference between user exits & customer exits:
User exit - A user exit is a three character code that instructs the system to access a program during system processing.
SXX: S is for standard exits that are delivered by SAP. XX represents the 2-digit exit number.
UXX: U is for user exits that are defined by the user. XX represents the 2-digit exit number
Customer exit - The R/3 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 R/3 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.
"The R/3 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 R/3 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."
Customer exits are implemented in Z-includes and are ENHANCEMENTS to the system.
User-exits were firstly intended to be developed for the SD module. You make your coding in includes in SAP namespace
(e.g MV*). That's why, user exits are MODIFICATIONS to the system. In includes for user exits there are empty subroutines
( generally with the name convention "userexit_...") and you code using global variables of the main program.
But, generally developers use these terms without this distinction. So, someone may mean a "customer exit" when (s)he says
"user exit" or vice-versa.
And as a last thing, let me introduce you the SDN forums pointing system: You can assign points to posts you find helpful
while solving your question. You can reward points by clicking the yellow star icon at header of each reply post.
You can reward;
Business Add-Ins are a new SAP enhancement technique based on ABAP Objects. They can be inserted into the SAP System to
accommodate user requirements too specific to be included in the standard delivery. Since specific industries often require special functions, SAP allows you to predefine these points in your software.
As with customer exits two different views are available:
In the definition view, an application programmer predefines exit points in a source that allow specific industry sectors,
partners, and customers to attach additional software to standard SAP source code without having to modify the original
object.
In the implementation view, the users of Business Add-Ins can customize the logic they need or use a standard logic if one
is available.
In contrast to customer exits, Business Add-Ins no longer assume a two-level infrastructure (SAP and customer solutions),
but instead allow for a multi-level system landscape (SAP, partner, and customer solutions, as well as country versions,
industry solutions, and the like). Definitions and implementations of Business Add-Ins can be created at each level within
such a system infrastructure.
SAP guarantees the upward compatibility of all Business Add-In interfaces. Release upgrades do not affect enhancement calls
from within the standard software nor do they affect the validity of call interfaces. You do not have to register
Business Add-Ins in SSCR.
The Business Add-In enhancement technique differentiates between enhancements that can only be implemented once and
enhancements that can be used actively by any number of customers at the same time. In addition, Business Add-Ins can
be defined according to filter values. This allows you to control add-in implementation and make it dependent on specific
criteria (on a specific Country value, for example).
All ABAP sources, screens, GUIs, and table interfaces created using this enhancement technique are defined in a manner
that allows customers to include their own enhancements in the standard. A single Business Add-In contains all of the
interfaces necessary to implement a specific task.
The actual program code is enhanced using ABAP Objects. In order to better understand the programming techniques behind
the Business Add-In enhancement concept, SAP recommends reading the section on ABAP Objects.
Difference between user exits & customer exits:
User exit - A user exit is a three character code that instructs the system to access a program during system processing.
SXX: S is for standard exits that are delivered by SAP. XX represents the 2-digit exit number.
UXX: U is for user exits that are defined by the user. XX represents the 2-digit exit number
Customer exit - The R/3 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 R/3 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. *-- Mani
The following document is about exits in SAP :-
The R/3 enhancement concept allows you to add your own functionality to SAPs standard business applications without having
to modify the original applications.
SAP creates user exits for specific programs, screens, and menus within standard R/3 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.
Customer Exit is a hook and also we have to add our own functionality so we have to write the code in include file and
activate that project in CMOD.
Whereas in User Exit ,we are writing the code in SAP namespace. So am thinking that its no need to create project and
activating that project for user exit. Is it right? For User Exit also we have to create project please clarify me
User Exits:
User exits allow you to add additional functions to the SAP standard.
Programs with user exits contain subroutine calls at certain points in their syntax that are identified by the prefix
USEREXI
T. The actual user exits are located in an include that has been assigned to a module pool. This is where customers can
include any changes (enhancements) that they want to make to the system. These includes are always processed during program
flow.
Advantage: In principle, customers can modify anything they want that is found in the include (tables, structures, and so
forth).
Disadvantage: SAP cannot check the individual enhancements themselves which often leads to errors in the enhancement process.
User exits (Function module exits) are exits developed by SAP. The exit is implemented as a call to a function module.
The code for the function module is written 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.
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.
Customer Exit
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. You can find more information about locating applications with pre-defined exits in
Locating Applications that have Exits
1. Learn user exits :
http://www.sapgenie.com/links/abap.htm
2. finding user exits :
http://www.sapgenie.com/abap/code/abap26.htm
3. A short tutorial on user exits :
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
4. Introduction to user exits with examples :
http://www.sap-img.com/abap/what-is-user-exits.htm
Regards,
Balaji.

Put validation through SPRO

Hi,
There are not any userexists for down payment ( F-47 ) which are suitable to my requirment .So now i have only way to chane in spro for validation so can any one tell me how validation done through spro step by step.
Regards,
Gurprit Bhatia

Hi,
There are not any userexists for down payment ( F-47 ) which are suitable to my requirment .So now i have only way to chane in spro for validation so can any one tell me how validation done through spro step by step.
Regards,
Gurprit Bhatia

User Exit for validating overall limit field and expected limit field-ME2xN

Dear Gurus,
Can you please suggest me any user exit or BAdi to validate the overall limit field and expected limit field in transaction ME2xN.
Or any other way to to achieve this functionality in ME2xN.
Our Requirement is while raising a service PO in the Limits tab the 'Overall limit' should be same as 'Expected Value', at present the user can enter overall limit greater than 'Expected Value'.
Regards,
Priyank Joshi

this will not work. you cannot add another structure (AUFK) on top of CEBAN. all characteristics have to be of one structure and since you want to release a PR it has to be CEBAN. before attempting to program something around that why do you not go to tx. OLME -> PR -> Release Strategy -> With Classfication -> Release Strategie and run it in a simulation mode. you will then see how it reacts.
there's a white-paper on service.sap.com explaning in detail release-strategies. it's a good one and a good read too!

Regarding Exit of validation in SPRO

Similar Messages

Maybe you are looking for