Some Questions

[Former Member]

Hi Can anyone answer below questions ,

What is BTE ? Use of it ?

Which is best User Exit Or BADI ? Why ?

Which method is best Session / Transaction ?

What is use of maintenance table ?

How to find the Table if we get only structre from F1 -> Technical detail

Kindly do not give links , Answers in single word too will be rewrded than links

[Former Member]

Hi Can anyone answer below questions ,

What is BTE ? Use of it ?

Which is best User Exit Or BADI ? Why ?

Which method is best Session / Transaction ?

What is use of maintenance table ?

How to find the Table if we get only structre from F1 -> Technical detail

Kindly do not give links , Answers in single word too will be rewrded than links

[Former Member]

Hi Kumar,

Check this info.

<b>Business Add-Ins</b> 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<b> customer exits</b>, 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.

<b>Session Method</b> is best than Call Transaction Method as it offers even background processing and also large no. of records can be processed ata a time.

<b>Table maintenance</b> is used to maintain data in the tables created (ZTABLE)

Generally for inserting new records into custom table thru transaction SM30, we need to enter all the values manually and save the record.

Will give answers for other questions asap.

Hope this resolves your query.

Reward all the helpful answers.

Regards

[anversha_s]

hi,

Which method is best Session / Transaction ?

Session method.

1) synchronous processing.

2) can tranfer large amount of data.

3) processing is slower.

4) error log is created

5) data is not updated until session is processed.

Call transaction.

1) asynchronous processing

2) can transfer small amount of data

3) processing is faster.

4) errors need to be handled explicitly

5) data is updated automatically

Session method is to populate the data by filling BDC structure

and keep as session to process from SM37 to post in appropriate Transaction.

Call transaction method is to post the data directly into the Transaction from an Executable program.

Session method SAP defined Function modules.

What is use of maintenance table ?

Table Maintenance generator is required to do Manual entries in the Table.

If the requirement is to update the table only programmatically

and not manually then table maint generator is not required.

Manual entries in table can be maintained ( New record can be inserted / existing can be modified )

using transaction SM 30, if the table maintenance for the table is generated.

Rgds

Anversha

[Former Member]

Hi,

1) Which is best User Exit Or BADI ? Why ?

when we use user exit we can use only one user exit at a time i.e suppose if we r using 1 user exit in one project then we cant use it agian in some other project.

but with BADI we can use 1 user exit in more than one project so BADI is the best i think ... if i am wrong pls correct me

2)Which method is best Session / Transaction ?

this depends on the situauin if we need immediate update then we will go for Call Transaction its like online updating.But if there is larger number of record and we dont want to cause burden to our server we can go for Session method where we chsedule this upload at some later time when the server is free . In session method we can update more than one transaction

3) How to find the Table if we get only structre from F1 -> Technical detail

there is some transaction se15( i am not sure ) from there u can find just check it out or from se84

if this info is helpful reward me

ravi

[Former Member]

Hi,

I think this document may help you...

Business Transaction Events

This activity describes how you can connect additional components (such as in the form of function modules developed yourself or a product from an external software provider) to the standard R/3 System.

There are two types of interface available in the General Ledger

Accounting (FI-GL), Accounts Receivable and Accounts Payable

(FI-AR/FI-AP), and Sales and Distribution (SD) components for this:

1. Publish & Subscribe interfaces (also called "informing interfaces" in the following) These should inform you about particular events (such as a document being entered) in the SAP standard application and make the data generated as a result available to the external software. The external software does not return any data to the standard R/3 System.

(I'm confused. MIT is using two business transaction events for the SD to FI interface. Both of these events are Publish & Subscribe interfaces. They both return data to the SAP standard application! They both change the FI document before it is posted. What I've figured out is that if there is an export to memory and an import from memory before and after the function call, then we can't modify the data. We can check this in the calling function module - OUTBOUND_CALL_00503110_E or OPEN_FI_PERFORM_00001020_E, etc)

Examples of such events in the R/3 System are:

• Master record was created, changed, or blocked

• Document was entered, parked, changed, or reversed

• Items were cleared or reset

Additional processing can be caused in the additional component on the basis of these events and data:

• Starting a workflow

• Generating or changing additional data

• Requesting correspondence

FI Clearing (F-32) calls (gathered via SE30):

Function OPEN_FI_PERFORM_00001020_E (can't modify data)

00001020 POST DOCUMENT: Prior to final checks

EVENT

This Event is reached prior to completing the document. The checks that are carried out at this point include checking, prior to posting, that the document balances to zero, and calculations for tax offsetting. This Event is accessed once per standard posting process and is similar to validation at document level (Event 0003). A document number has not yet

been assigned when this Event is reached.

INTERFACE

All document line items created and the document header data are

transferred (both as tables).

Parameter

T_BSEG

T_BKPF

Function OPEN_FI_PERFORM_00001025_E (can't modify data)

00001025 POST DOCUMENT: Final checks completed

EVENT

This Event lies following all checks on the whole document, but prior to number assignment. Following this Event, no further error messages may be sent. The document is complete at this point, and no further changes can be made to it prior to posting.

INTERFACE

All current data, all document data relevant for the posting, and various control parameters are transferred to the additional component. At this point you can still implement your own checks on the current document data.

Parameter

I_BKDF

T_AUSZ1

T_AUSZ2

T_AUSZ3

T_BKP1

T_BKPF

T_BSEC

T_BSED

T_BSEG

T_BSET

T_BSEU

Function OPEN_FI_PERFORM_00001030_E (can't modify data)

Function OPEN_FI_PERFORM_00001140_E (can't modify data)

2. Process interfaces (also referred to as "process" in the following) Process interfaces are used to submit business processes to a different control which cannot be realized with the standard system, that is process interfaces replace standard processes. Here you can structure determination of individual field contents or of specific reactions to process flows individually. It is possible to connect different external developments to the standard R/3 System. The additional developments are generally carried out using the ABAP/4 Development Workbench. This way you can, for example, influence the control of payment transactions. Selection of payment method, house bank and partner bank can be made using the payment data (currency, amount, and payee) according to a selection logic which you have defined.

FI Clearing (F-32) calls:

Function OPEN_FI_PERFORM_00001120_P

Function OPEN_FI_PERFORM_00001130_P

Function OPEN_FI_PERFORM_00001150_P

Function OPEN_FI_PERFORM_00001170_P

Standard Settings

Sample modules are delivered in the standard R/3 System which you can

copy into your name range and fill them with statements there.

Activities

1. Enter a product using "Settings -> Customer's products". Actually, in 4.6C, from transaction FIBF (IMG -> Financial Accounting -> Financial Accounting Global

Settings -> Business Transaction Events):

Settings -> Products -> ...of a customer

There are generally a large number of function modules belonging to a product which can be called by different program events from within the standard R/3 System. A product can also be an external software component. If the product is in an external system, enter an RFC destination here. If the product is in the same system, you do not have to enter anything. Important: Do not forget to activate the product after making the following settings.

2. Establish the interfaces with which the R/3 System provides you. To do this, choose

Environment -> Info system (P/S)

or

Environment -> Info system (Processes).

Execute the program. You should enter "A" as the

attribute type. You see the respective interfaces with which the R/3 System provides you. Note the key of the interface which you require.

You can also select:

• By particular SAP application components

• By particular events by entering intervals

• Which interfaces are used in activated products

• Which interfaces are used within a particular country version or within a particular industry

• Which interfaces are used within a particular customer product

3. Enter the function module which you have developed yourself. To do this, choose either Goto -> Edit modules within the info system or Settings -> P/S modules or Process modules -> Customer's in the "SAP Business Framework" menu. Make the following entries:

• Key for the interface

• The product that you want to use

• Function module which belongs to this product.

You can also enter several function modules for a product. Caution:

The function module must be within your name range, that is must begin with the letter Z. You leave the Ctr and Appl. fields blank unless you want a particular country version or a particular SAP industry-specific component to be enhanced or replaced instead of the standard process flow.

4. Fill the source text of your function module

and activate it. To do this, go again via Environment -> Info system (P/S) or Environment -> Info system (Processes) into the information system and execute the program. Then proceed as follows:

• Click twice on the interface you have chosen. If you want, you can look at the interface at this point by choosing Goto -> Interface. Then choose the Back function again afterwards.

• Place the cursor on the relevant line and choose Goto -> Function library. You see the sample function module delivered by SAP.

• Copy the sample module delivered by SAP and call it the same as the function module entered in step 3.

• Fill the source text of the empty function module.

• Activate the function module.

• Activate the product as described in step 1.

5. Run the R/3 program affected and test whether calling your function module works.

Further Notes

The other menu paths are only used for information about additional components delivered by SAP or about software already installed by external software providers.

http://fuller.mit.edu/user_exits/business_transaction_event.htm

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

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.

3.In this method, the ABAP/4 program uses the call transaction <T-code > using <bdc_tab> mode <mode> update <update > method.

In ‘ Call Transaction ’ , the transactions are triggered at the time of processing itself and so the.

ABAP program must do the error handling.

Synchronous Processing

We can update the database both synchronously and asynchronously. We can specify the mode in the program.

No batch input processing log

While execution it starts from the first.

Faster than session method.

Session Method:

In this method, ABAP/4 program read the external data that is to be entered to the SAP system and stores the data in the batch input session. When the prgm has finished creating the session, we can run the session thro the TC SM35. This method involves FM like BDC_OPEN,BDC_INSERT,BDC_CLOSE

Whereas in Batch Input Sessions, the ABAP program creates a session with all the transactional data, and this session can beviewed, scheduled and processed (using Transaction SM35) at a later time. The latter technique has a built-in error processing mechanism too.

Asynchronous Processing

Synchronous Database update. During processing, no transaction is started until the previous transaction has been written to the database.

Detailed Log will be generated for all the sessions

While executing it wont start from the first. It will start from the place where it ends with error.

Not as fast as call transaction method.

Rgds,

P.Naganjana Reddy

[Former Member]

1.

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/207835fb-0a01-0010-34b4-fef...

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

3.

http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm

4.

table maintainence generator

http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ed2d446011d189700000e8322d00/content.htm

http://help.sap.com/saphelp_46c/helpdata/en/a7/5133ac407a11d1893b0000e8323c4f/frameset.htm

Regards,

Santosh

[Former Member]

<b>Seems like u r hunting answers for a set of interview questions. Please dont keep opening new thread for this. Else ur account will be deactivated and ur threads deleted on complaints filed by any users.</b>

[Former Member]

Hi ,

Thanks for that info .Now thread closed .