Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Queries

Former Member

‎09-10-2007 1:07 PM

0 Kudos

Hi Experts,

Please clarify these queries.

1.How can we transport a Project that is created in CMOD from one server to another ?

2.How can we implement same user exit for multiple regions for same client?

3.When we have to go for User Exit and when we have to go for BADI?

4.How many Menu exits we can implement for single transaction?

5.What happend to a user exit that is implemented when version upgrade happens?

6.how many screen exits we can create for a single T-Code

7.What are the exits available in SAP R/2 system?How can we differentiate them with R/3 user-exits?

Regards

1 REPLY 1

Former Member

‎09-10-2007 1:16 PM

0 Kudos

Hi

1.How can we transport a Project that is created in CMOD from one server to another ?

2.How can we implement same user exit for multiple regions for same client?

3.When we have to go for User Exit and when we have to go for BADI?

<b>BADIS</b>

is an anticipated point of extension – these points act like sockets and exist in the original source code

based on ABAP Objects. BAdI defines an interface that can be implemented by BAdI-implementations that are transport objects of their own

Important! There are 2 roles: Enhancement Option-provider & Implementer.

In the above context, Enhancement Implementation can be done only if option (hook) is provided by the Option-provider. In simple words there are no implicit BAdIs.

<b>user exit</b>

EXIT s are nothing but the R/3 Enhancements which allows you to add your own functionality to SAP’s standard business applications without having to modify the original applications.

4.How many Menu exits we can implement for single transaction?

<b>Menu exits</b> add items to the pull down 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 item’s text when activating the item in an add-on project.

you can creat any number of if possible as per ur req

5.What happend to a user exit that is implemented when version upgrade happens?

6.how many screen exits we can create for a single T-Code

<b>Screen Exits</b> Screen exits add fields to screens in R/3 applications. SAP creates screen exits by placing special sub screen areas on a standard R/3 screen and calling a customer sub screen from the standard screen’s flow logic.

as per ur req u can creat any number of

7.What are the exits available in SAP R/2 system?How can we differentiate them with R/3 user-exits?