Solved: LUW

Former Member · ‎2007 Nov 20

Hi,

1. What is LUW and what purpose we use in sap.

2. what is system land scape.

3. if u get a error in quality server how do u rectify this problem.

4 . In my report there is coding only report name is there if i execute the program

which event will be active.

5.what is VPN.

6. what is main diff between badi and user-exit.

Thanks.

Srinivas

Former Member · ‎2007 Nov 20

HI

1. What is LUW and what purpose we use in sap.

Transactions and Logical Units of Work

In everyday language, a transaction is a sequence of actions that logically belong together in a business sense and which either procure or process data. It covers a self-contained procedure, for example, generating a list of customers, creating a flight booking, or sending reminders to customers. From the point of view of the user, it forms a logical unit.

The completeness and correctness of data must be assured within this unit. In the middle of a transaction, the data will usually be inconsistent. For example, when you transfer an amount in financial accounting, this must first be deducted from one account before being credited to another. In between the two postings, the data is inconsistent, since the amount that you are posting does not exist in either account. It is essential for application programmers to know that their data is consistent at the end of the transaction. If an error occurs, it must be possible to

undo the changes made within a logical process.

In the R/3 System, there are three terms frequently used in this connection:

Database Logical Unit of Work (LUW)

A database LUW is the mechanism used by the database to ensure that its data is always consistent.

SAP LUW

An SAP LUW is a logical unit consisting of dialog steps, whose changes are written to the database in a single database LUW.

SAP Transaction

An SAP transaction is an application program that you start using a transaction code. It may contain one or more SAP LUWs.

The following sections of this documentation explain these three terms in more detail.

Database Logical Unit of Work (LUW)

Check the following link:

http://help.sap.com/saphelp_nw04/helpdata/en/41/7af4bca79e11d1950f0000e82de14a/frameset.htm

SAP LUW

http://help.sap.com/saphelp_nw04/helpdata/en/41/7af4bfa79e11d1950f0000e82de14a/content.htm

SAP Transactions

An SAP LUW is a logical unit consisting of dialog steps, whose changes are written to the database in a single database LUW. In an application program, you end an SAP LUW with either the COMMIT WORK or ROLLBACK WORK statement. An SAP transaction is an application program that you start using a transaction code. It may contain one or more SAP LUWs. Whenever the system reaches a COMMIT WORK or ROLLBACK WORK statement that is not at the end of the last dialog step of the SAP transaction, it opens a new SAP LUW.

If a particular application requires you to write a complex transaction, it can often be useful to arrange logical processes within the SAP transaction into a sequence of individual SAP LUWs. You can structure SAP transactions as follows:

With one or more SAP LUWs.

Transactions in this form consist entirely of processing blocks (dialog modules, event blocks, function module calls, and subroutines). You should be careful to ensure that external subroutines or function modules do not lead to COMMIT WORK or ROLLBACK WORK statements accidentally being executed.

By inserting an SAP LUW

The ABAP statements CALL TRANSACTION (start a new transaction), SUBMIT (start an executable program), and CALL FUNCTION... DESTINATION (call a function module using RFC) open a new SAP LUW. When you call a program, it always opens its own SAP LUW. However, it does not end the LUW of the SAP transaction that called it. This means that a COMMIT WORK or ROLLBACK WORK statement only applies to the SAP LUW of the called program. When the new LUW is complete, the system carries on processing the first SAP LUW.

By running two SAP LUWs in parallel

The CALL FUNCTION... STARTING NEW TASK statement calls a function module

asynchronously in a new session. Unlike normal function module calls, the calling

transaction carries on with its own processing as soon as the function module has

started, and does not wait for it to finish processing. The function call is synchronous. The called function module can now call its own screens and interact with the user.

2. what is system land scape.

every client follows one landscape for his PROJECT

for SAP normally we have 3 servers

DEVELOPMENT SERVER -> QUALITY SERVER -> PRODUCTION SERVER

the flow of object also in this way

there may be any number of servers for each level

example:- for my client they had 3 development servers , 2 quality severs and 2 production servers

3. if u get a error in quality server how do u rectify this problem

if you don't get any error in DEVELOPEMENT SERVER and getting error in QUALITY THEN it won't reflect in your system because you need to transport that object from DEVELOPMENT SEVER to QUALITY SERVER

after transporting it there won't be any refecltion of that object in ur system

but it wil come back for you again to change that error message

4 . In my report there is coding only report name is there if i execute the program

which event will be active

it won't trigger any thing

it will look for some events but there won't be any event triger , result the execution button does't work

5.what is VPN.

for every client there is on VPN connection it is for security perpous

after login into that VPN you don't have access to copy or paste your code etc.. securties wil be there

6. what is main diff between badi and user-exit

Difference 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.

These are two different ways of implmenting similar functionality.

1. BADI's - Use Classes / Methods to implement the custom functionality

2. User Exits - Use functions to implement the same.

Badi is a OO concept.

You can do multiple implementation of BADI but user exit only once.

For badi use se18 and se19 t-code

for user exit use smod and cmod t-code

BADI is just an object-oriented version of user-exit. Instead of entering program code into some function module (as in customer-exit), you define some class which has to implement predefined methods and those methods are fired at predefined points just like an old user-exit. Some BADI can have multiple independent implementations which is much better for software deployment as several developers can implement the same BADI independently.

Difference 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

BADI

Business Add-Ins are a new SAP enhancement technique based on ABAP Objects.

Badi’s allow for a multi-level system landscape (SAP, partner, and customer solutions, as well as country versions, industry solutions, and the like). Business Add-Ins can be created at each level within such a system infrastructure

Some BADI can have multiple independent implementations which is much better for software deployment as several developers can implement the same BADI independently.

Customer-exit

CUSTOMER EXITS(enhancements) are FUNCTIONS so they are called using CALL FUNCTION (or more exactly CALL CUSTOMER FUNCTION

customer exits assumes a two-level infrastructure (SAP and customer solutions)

Customer-exit implemented in one project cannot be implemented in other.

User-exits(modifications)

USER EXITS are FORMS and are called by SAP standard programs using PERFORM.

Inside the form (user exit) you can read and change almost any global data from host program.

User exits are more flexible because you have more information to use in your code but on the other hand , it is very easy to manipulate erroneously global data and lead the standard program to a dump or even to make database inconsistent.

User-exit doesn’t have any classification.

Basically designed For SD module

User-exits can be written only using access-key

With user-exits the code , the developer has written will not be there for next version unless modification assistance tool is used

http://www.sap-img.com/abap/difference-between-badi-and-user-exits.htm

http://sap.ittoolbox.com/groups/technical-functional/sap-r3-dev/badi-vs-user-exit-405324

http://www.sapfans.com/forums/viewtopic.php?t=172792

http://sap.ittoolbox.com/groups/technical-functional/sap-r3-dev/badi-vs-user-exit-405324

http://www.sapfans.com/forums/viewtopic.php?t=172792

http://www.sap-img.com/abap/difference-between-badi-and-user-exits.htm

diff between badi n customer exits........

http://www.sap-img.com/abap/difference-between-badi-and-user-exits.htm

https://forums.sdn.sap.com/click.jspa?searchID=519283&messageID=2515351

https://forums.sdn.sap.com/click.jspa?searchID=519283&messageID=2627911

https://forums.sdn.sap.com/click.jspa?searchID=519283&messageID=2847358

https://forums.sdn.sap.com/click.jspa?searchID=519283&messageID=2584155

https://forums.sdn.sap.com/click.jspa?searchID=519283&messageID=2826338

https://forums.sdn.sap.com/click.jspa?searchID=519283&messageID=2859102

Reward points If it is useful.

Former Member · ‎2007 Nov 20

Hi,

Please refer these links for answers to ur queries :

Do reward points if helpful.

1)http://help.sap.com/saphelp_nw04/helpdata/en/41/7af4bfa79e11d1950f0000e82de14a/content.htm

2) http://help.sap.com/saphelp_nw04/helpdata/en/31/f0ff69551e4f259fdad799a229363e/content.htm

5)http://www.sap.com/community/pub/showdetail.epx?itemID=7459

6)http://www.sap-img.com/abap/difference-between-badi-and-user-exits.htm

Former Member · ‎2007 Nov 20