Difference between dynamic actions and user exit

Hi,
Please help me in when to use table T588z and user exit to write code for dynamic actions.
Thanks,
Venkat

Hi Prasad,
Find the difference between Dynamic action and user exits.
Dynamic Action                                              User Exits
1. Here only initialization of an infotype                    1. Along with initialization of an infotype,                  depending upon other infotype                                    validation also can be done like in
    can be done.                                                        IT 16 the contract end date can not be
                                                                                entered more than 6 months.
2. Less time consuming to write.                             2. Require programming approch so more
                                                                                time consuming.
3. Table T588Z                                                       3. PBAS0001
Br/Manas

Similar Messages

Difference between BADI's and User Exits.

Hi Experts,
I want to know the difference between BADI's and User Exits....
What i know is BADI's are Object oriented But User exits are normal Programs.....i think in User exits also we can write Object oriented program.....
AND one more is BADI's are multiple use but user exits are not,,,,
IF BADI's are multiple use like all BADI's are multiple use or some....is there any performance issues,,,i need to know gurus .......and please provide to me more than this.........
Thanks
Venkat

User exits are some provisional space in the standard program for you to write your own business functionality.
BADI's are soem of the business add-in's that comes along with the standard SAP product but are disabled as most of the customers do not need it. So for those customers who need this will have to activate it and that functionality will be avilable in the transaction.
- guru
Reward points for helpful answers

Difference between Adhoc package and user created package

what is the difference between Adhoc package and user created package.
Thanks,

Hello Asha,
Here are some links which would be helpful for you to get started with BPS
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/biw/s-u/sap bw business planning and simulation - how to guides list.htm
https://media.sdn.sap.com/public/eclasses/teched04/BW253_files/Default.htm#nopreload=1
https://www.sdn.sap.com/irj/sdn?rid=/webcontent/uuid/3040dd5d-0501-0010-baa8-fc0aafa88c40 [original link is broken]
http://help.sap.com/bp_biv235/BI_EN/html/BW/CostCtrPlan.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/biw/d-f/enhancements bw-bps formerly sem-bps in sapnetweaver 04.ppt
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5d90209f-0501-0010-59a2-9243ac94a4d7
http://help.sap.com/saphelp_nw04/helpdata/en/05/242537cedf2056e10000009b38f936/frameset.htm
Also sent you some useful documents. Please check your mail.
Regards,
Praveen

Difference Between Service Account and User Account

What is the Difference Between Service Account and User Account

Hello Mohit,
Basically there are two types of approches which you should understand.
In many environments, administrators prefer to simply create a domain user account and assign appropriate privileges to it. Then this user account is used in order to start a specific service on a computer.
In that case there is really no difference between a user account and the so called service accounts. Since this service account is simply a domain user, all the task related to managing the domain users apply to it. For example you
should keep the password up to date manually. Some environment move step forward and assign
Deny Logon Locally of this type of service account in order to enhance the security.
The second concept is Managed Service Accounts. There are plenty of differences between a Managed Service Account and a User Account.
The Display Icon is different from a view perspective.
The type of object is different.
Managed service accounts password management is automatic.
You can not create Managed Service Accounts using GUI. They are only created using Powershell.
You can refer to link below for more inormation:
Service Accounts Step-by-Step Guide
Regards.
Mahdi Tehrani |
|
www.mahditehrani.ir
Please click on Propose As Answer or to mark this post as
and helpful for other people.
This posting is provided AS-IS with no warranties, and confers no rights.
How to query members of 'Local Administrators' group in all computers?

Difference between system status and user status.

Can someone explain to me the difference between system status and user status in details

Hi,
As you mentioned there are 2 status can be maintained for documents like Equipment Master, Notification, Maintenance Order & other important business documents.
In case, client feels that system status is not enough to capture the details of the object, then user status can be used.
System statuses will be updated automatically based on business transactions which will be done on SAP.
For example, once the equipment is created, System status would CRTD (Created). If you install the same to some superior equipment or FL, then status would be INST (Installed).
If you keeping that equipment in Spare, then for that, you have to maintain separate User Status like AVLB (Available in Stock / Spare) so that through IH08, by using User status, you can the report which is available as spare.
These user status as per the name, should be updated by the user manually.
Regards,
Maheswaran.

Any difference between Master data and User master data ?

Any difference between Master data and User master data ?

hi
A user master record defines the authorizations assigned to a user. Based on these authorizations one can access the master data.
Master data - it is the data which is used long term in SAP r/3 system such as vendor master , material master, customer master,
there is no such thing like user master data to the best of my knowledge
hope this helps
regds
Manan

Difference between implementation guide and user guide.

Hi All,
I am a recent graduate, just wanted to know what is teh Difference between implementation guide and user guide.
Sorry the question may sound to simple but I am not aware of the aswer.
Regards,

Hi,
The implementation guide is the reference that you need to use to do the functional setup while the user guide covers how the navigation of the module/application and tells you how to use it.
Thanks,
Hussein

Difference between dynamic report and template

I think the subject line covers it, I am trying to find out, that when I save the report, I can save it as static or dynamic report or as a template. but what is the diff between dynamic report and template?
Thanks.

Hi Zack,
SAP provides some standard templates as report templates. The users are provided with the option to save their own versions of reports as 'Report Templates' for future use. As a super user one could create a custom template and save to the template library which the other users could access from the template library.
For example if you have 'ACCOUNT' drilldown as a standard report template, you could define a new template as for example, 'Entity' drilldown template.
Hope it is clear now.
Thanks,
Sreeni

Difference between Business partner and user

Hi,
When you Define a position under a Organization Unit & under the position, do we assign a User or a Business partner, what is the difference them.
Please give me some idea?
Rgds
Eliz

Hi Eliz,
the most common approach is to create a businesspartner from type employee (ROLE = BUP003). Within this businesspartner please assign the User-ID (transaction BP - tab "Identification").
Afterwards assign this businesspartner to your position in transaction PPOMA_CRM.
If you do it like this the user is also assigned to the position.
The businesspartner itself is needed if you create transactions in CRM, for example "responsible Employee" of an opportunity.
If you have more questions please ask.
Kind regards
Manfred

Diff between BADI and USER EXITs

Hi,
What is the difference between the BADI and USER EXITs?
Thanks,
Satish

HI
GOOD
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.
What is difference between badi and user-exists?
What is difference between enhancements and user-exists? and what is the full form of BADI?
I have another doubt in BDC IN BDC WE HAVE MSEGCALL (i did not remember the > correct name) where the error logs are stored, MSEGCALL is a table or structure.
What is the system landscape?
1) Difference between BADI and USER-EXIT.
    i) BADI's can be used any number of times, where as USER-EXITS can be used only one time.
       Ex:- if your assigning a USER-EXIT to a project in (CMOD), then you can not assign the same to other project.
    ii) BADI's are oops based.
2) About 'BDCMSGCOLL' it is a structure. Used for finding error records.
3) Full form of BADI 'Business addins'.
3) System land scape will be depends on your project
    Ex:- 'Development server'>'Quality server'-> 'Production server'......
THANKS
MRUTYUN

What is the difference between customer exits and user exits?

hello friends,
what is the difference between customer exits and user exits?

Hi
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.
Types of Exits
There are several different types of user exits. Each of these exits acts as hooks where you can attach or "hang" your own add-ons.
Menu Exits
Menu exits add items to the pulldown menus in standard SAP applications. You can use these menu items to call up your own screens or to trigger entire add-on applications.
SAP creates menu exits by defining special menu items in the Menu Painter. These special entries have function codes that begin with "+" (a plus sign). You specify the menu items text when activating the item in an add-on project.
Screen Exits
Screen exits add fields to screens in R/3 applications. SAP creates screen exits by placing special subscreen areas on a standard R/3 screen and calling a customer subscreen from the standard screens flow logic.
Function Module Exits
Function module exits add functions to R/3 applications. Function module exits play a role in both menu and screen exits.
When you add a new menu item to a standard pull down menu, you use a function module exit to define the actions that should take place once your menu is activated.
Function module exits also control the data flow between standard programs and screen exit fields. SAP application developers create function module exits by writing calls to customer functions into the source code of standard R/3 programs.
These calls have the following syntax:
CALL CUSTOMER-FUNCTION 001.
Field Exits
Field exits allow you to create your own programming logic for any data element in the Dictionary. You can use this logic to carry out checks, conversions, or business-related processing for any screen field. Example: The data element BBBNR identifies a companys international location number. You might want to set up your R/3 System so that all international location numbers are larger than 100.
The field exit concept lets you create a special function module that contains this logic.
You assign the special function module to the data element BBBNR. You then assign the module to any programs and screens in which users can add new international location numbers. When you activate your field exit, the system automatically triggers your special routine whenever a user enters a company location number.
In 4.6c, you can use "RSMODPRF" program to create field exits.
An example of a user exits :-
MODULE user_exit_0001 INPUT
    CASE okcode.
        WHEN 'BACK OR EXIT'.
            CASE sy-dynnr.
                    WHEN '100'.
                         SET SCREEN 0.
                         LEAVE SCREEN.
                    WHEN '200'.
                         SET SCREEN 100.
                         LEAVE SCREEN.
             ENDCASE.
      ENDCASE.

Differences between BADIS and User-exits

Hi everybody,
I am new to ABAP and wonder what are the differences between BADIS and User-Exits. I read paper but did not find a SAP documentation yet.
Does anybody know where to find a sap document which explains both technologies?
Greetings, AD

Hi,
User-Exit is a specific place in a transaction-process where SAP offers
third parties to include there own business functionality. Actually
User-Exit is the namespace used for Exits programmed by SAP specifically
for SD. For the other modules it's called Customer-Exit.=20
>Business Add-Ins (BADI) =20
The use of object orientated code within SAP has lead to new method of
enhancing standard SAP code called Business Add-Ins or BADI's for short.
Although the implementation concept is based on classes, methods and
inheritance you do not really have to understand this fully to implement
a BADI.
For better understanding visit.
http://sap.ittoolbox.com/groups/technical-functional/sap-r3-dev/779183#
Hope it was useful.
Thansk,
Sandeep.

Difference between customer exit and user exit?

hi experts
difference between customer exit and user exit?

These r the main differences between user exits and customer exits
1) user exits r subroutines where as customer exits r function modules
2) user exits r not upgraded where as customer exits r will upgrade
3) customer exits r used for creating and additional fields or menu items to stadard tcode where as user exits r used for enabling or disabling the fields on the standrd screen or concatenating the key fields,it is not used adding an additional componenats to stadard tcode
4) customer exits r reusable where as user exits r not reusable.
Also:
1. Customer exits: Implemented as Function Modules within z includes. Anybody can change it and no access key is required.
2. User Exit: Implemented as subroutines within includes (any include except y or z includes). You need access for the specific include and then you can any subroutine (user exit) within that Include.
BADIs are the enhanced version of user exits where the same logic is implemented via classes and object (OOP)
Enchancement point is the latest once introduces with ECC6.0 . Not very sure about that but you can change it without any access key.
Please go through the following link which will help you understand the exits in a much better way:
http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec07a25db911d295ae0000e82de14a/content.htm
http://www.sap-img.com/abap/what-is-the-difference-between-smod-and-cmod.htm
http://sap.niraj.tripod.com/id21.html
http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/frameset.htm
http://www.sap-img.com/ab038.htm
User Exits.
http://www.erpgenie.com/sap/abap/code/abap26.htm
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
customer exits
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f1a7e790-0201-0010-0a8d-f08a4662562d
Menu Exit.
http://www.sappoint.com/abap/spmp.pdf
http://www.sappoint.com/abap/userexit.pdf
http://www.sapdevelopment.co.uk/enhance/mod_sapmenu.htm
http://www.sapdevelopment.co.uk/enhance/enhancehome.htm
1. Previously there were only user-exits.
2. Then came the concept of customer-exits.
3. user exits were nothing but subroutines
FORM/PERFORM
called from standard programs.
4. The FORM defintion was placed inside
an empty include file.
5. So It was called EVERYTIME.
and we need to MODIFY/REPAIR the
standard include .
6. Then it came with concept of customer-exit
7. It consists of calling a FUNCTION MODULE,
which is called only if
the user-exit is ACTIVATED (other wise not called)
In this case, the code in put inside
a pre-defined Z include.
8. Functionality of both is same, howerver
we can note the following important differences
a) Customer exit is called only if activated.
(hence, it does not waste resources)
b) in customer exit, REPAIR does not happen
to the standard include.
Exits are basically the hooks whcih SAP has provided to add your own code.
User Exits: These are provided only SD module .
They are Empty subroutines with naming like USEREXIT_.
We need to have Access key to implement them.
Customer Exits: These are enhancement techniques.
There are defined in SMOD and implemented in CMOD.
Types of Customer exits: Function exit, Screen Exit, Menu exit.
User Exit and Customer Exit are same ,but SAP Exit and Customer exit are different...
Customer Exit,
Enables you to determine values for variables by means of Functional Module exit.The function module used is EXIT_SAPLRRSO_001.
Create a project in CMOD by selecting the SAP Enhancement RSR00001 and assign this to the enhanced proj and activate it.
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 find find more information about locating applications with pre-defined exits in Locating Applications that have Exits
http://help.sap.com/saphelp_nw04/helpdata/en/1d/ca10d858c2e949ba4a152c44f8128a/frameset.htm
SAP EXIT:this processing type contained in variables that are delivered with SAP BW business content.
http://help.sap.com/saphelp_nw04/helpdata/en/1d/ca10d858c2e949ba4a152c44f8128a/frameset.htm
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 USEREXIT. 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
reward points if found useful
regards
palak

Difference Between BADI and User Exits

Hi..
generally BADIs & User Exis are used exensively in SAP SD...
Can anybody throw some light waht is difference between them ...
Kindly please reply......
Regards
Nisha

Hi
ifference Between BADI and User Exits
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.
What is difference between badi and user-exists?
What is difference between enhancements and user-exists? and what is the full form of BADI?
I have another doubt in BDC IN BDC WE HAVE MSEGCALL (i did not remember the > correct name) where the error logs are stored, MSEGCALL is a table or structure.
What is the system landscape?
1) Difference between BADI and USER-EXIT.
    i) BADI's can be used any number of times, where as USER-EXITS can be used only one time.
       Ex:- if your assigning a USER-EXIT to a project in (CMOD), then you can not assign the same to other project.
    ii) BADI's are oops based.
2) About 'BDCMSGCOLL' it is a structure. Used for finding error records.
3) Full form of BADI 'Business addins'.
3) System land scape will be depends on your project
    Ex:- 'Development server'>'Quality server'-> 'Production server'......

Differences between OA 11i and R12 on User Management

Hi All,
Please give some details about differences between OA 11i and R12 on User Management (Role Responsibilities and Role Based Access Control,etc).
Please advise me on this regard.
Moreover,I don't have any Metalink username and Password.
Thanks

New features introduced for User Management (UMX) in R12
The following are the new features introduced in R12 for User Management (UMX):
1)Proxy User:
This new functionality:
· Provides the delegator the ability to grant/revoke the proxy privilege to individuals
· Provide a mechanism throughout the application’s framework where the user can access the proxy switcher feature
· Provide a mechanism throughout the application’s framework which indicates to the user that they are acting as a proxy
· Provide the ability to track the delegate’s actions within the system, while the delegate is acting on behalf of the delegator (Audit)
Benefits of Proxy User:
Ability to delegate proxy authority provides great security controls and Granular control of proxy authority is provided i.e delegate authority can be specified for date ranges
2) ICM (Separation of Duties – SoD) Integration
Oracle User Management is integrated with Oracle Internal Controls Manager (ICM) for the prevention, detection, enforcement, and resolution of separation-of-duties constraints during the assignment of roles by administrators to users.
For example, a constraint (created using a set of ICM UIs) can be defined such that no user is allowed to have "Role A" and "Role B" at the same time. In such a case, anadministrator attempting to assign Role B to a user who already has Role A will be presented with a dialog page displaying the constraint violation information.
At this point, the administrator can take one of two actions:
• Go back to the role assignment page and remove the assignment that is causing the
violation.
• Override the constraint violation, if he has the "AMW: Allow SOD Violation
Override" permission granted to him.
With this permission, the administrator will see Apply and Cancel buttons on the constraint violation dialog page. Clicking Apply will override the constraint, and assign Role B to the user despite the warning. Clicking Cancel will cancel the save operation without granting Role B to the user.
UMX integration with ICM is enabled according to the setting of site-level profile option "UMX: Enable ICM Validation". The default value is "Yes".
3) Enhanced Forget Username/Password Functionality
Forgot Username Functionality is Introduced in R12 along with Forgot Password. So now Users can query on either lost “username” or lost “password” Users should enter email address if lost username and enter username if lost password
Users can now aslo reset username as part of email address verification instead of a two step process.
4)New Registration Process Type for Administrator Role Assignment
New Registration Process Type is introduced for type “Administrator Assisted Additional Access”
Different policies (registration processes) can be used as administrative actions vs. self service requests for
· Approval Routing
· UI
· Notifications
· Business Logic
Simpler registration processes can be created for self-service and administrator flavors
Support for alternative approvals for administrator role assignment is also introduced.
5) Security Wizard Infrastructure
a)Security Wizard Infrastructure
· Infrastructure for product teams to create their own security wizards in context of a role.
· Product teams can create their wizards and seed relevant information
· These wizards appear in list of security wizards available to the administrator when creating/updating role information
b)New User Interface for Delegated Administration
· Existing functionality(11.5.10) of delegated administration setup implemented using wizard infrastructure
· Wizard guides the user through what options they can set for a delegated administration
6) Search Enhancement for List of Value’s (LOV)
Search Enhancements has been made in LOV’s in User management.
a) All LOVs in User Management (UMX) are now searchable by
· Role
· Responsibility
· Both
· Internal Code
b)A type included in the results – to differentiate roles and responsibilities

Difference between dynamic actions and user exit

Similar Messages

Maybe you are looking for