Generally if you are a developer you know all about BADI’s, if you are a functional person you possibly only know that they exist. This is what every functional person, at least needs to know about them:

A BADI is similar to a user exit.

It stands for Business Add In.

BADIs  are object orientated.

You do not need to register the code change in SAP SSCR. (SAP Software change registration).

In ECC the transaction code to display/change/create a BADI definition is SE18.

In SE18 you can also see detailed descriptions of the use and examples of standard SAP BADI’s for example use: ME_DEFINE_CALCTYPE - To reset the calculation type in a purchase order.

In ECC you can see the business implementation that calls the BADI in transaction SE19.

• In the definition, SE18 you create an enhancement that is called from the application code

• In the implementation, SE19  you save the code for the functions for the enhancement

How do you find a BADI:

Go to the transaction code you wish to check, for example MM02. Click on a field, select help, select technical details. (F1-F9), then double click on the program name.

1. Search in the program for the string CL_EXITHANDLER you should find the string “CALL METHOD CL_EXITHANDLER=>GET_INSTANCE” where you will find the relevant BADI.
2. Alternatively you can find out the BADI name by following this post: http://saptricks.com/2438/find-a-badi

Do you wish to remove the “Copy From” prefix of a document title in Solman?

When copying a document in Solution Manager, the original title gets “Copy From” as a prefix for the new title. When the length of a document title approaches the limit of 64 characters, relevant parts at the end can get truncated by putting this prefix at the beginning.

To solve this you can simply remove the prefix by using a simple SAP note - 1605780. This correction avoids the prefix and thus keeps the original title for the copied document.

Quite often, program variants are protected to avoid any unauthorised users from changing them.

For example, if this variant is for a program which is part of a batch plan, you don’t want to this variant to be modified as it will disturb your automatic processes. So you protect your variants. But a protected variant can only been changed by the user who has protected this variant.

The issue could arise when the original user has left the company or the variant is required to be changed for an urgent issue?

The solution – Go to transaction SE38, execute program RSVARENT, “Cancel Variant Protection” enter the program and the variant you want to unprotect and execute. The program variant is now available for any changes.

Submitted by Robin Ferali – Thank you for contributing to the webs largest database of SAP tricks!

There are some cases where we need to add some functionality when a transaction is called or an action is done in SAP.

In some cases we are not able to know which BADI to change in order to have our customized behaviour for a determined action.

Well, following the following steps we will be able to identify the BADI that we will need to change:

Step 1: SE37 display Function Module – SXV_GET_CLIF_BY_NAME.

Step 2: Set a BREAKPOINT on call function SXV_ADD_PREFIX .

Step 3: In another SESSION run the desired transaction, parameter ‘name‘ gives the BADI; (parameter ‘clif ‘ gives implementation, e.g. for TCode MIGO name = MB_MIGO_BADI, clif = CL_EX_MB_MIGO_BADI.)

Submitted by an anonymous SAPtricks User – Thank you for contributing to the webs largest database of SAP tricks!

When you want to activate/deactivate MS Word as the text editor for SAPscript/Smartforms.

- Call transaction se38, enter program RSCPSETEDITOR and press Execute (F8). On the next screen, select the checkbox SAPScript/Smartforms and press ‘Activate’.

- This is a fantastically fast method to produce multiple texts in multiple languages provided they are supported by your code page. Check out the OSS note below for comprehensive instructions on MS Word setup and available options.

OSS Note: 742662.

Submitted by an anonymous SAPtricks User – Thank you for contributing to the webs largest database of SAP tricks!

Requirement: You wish to investigate the contents of an IDoc. Or you need to locate a specific IDoc based upon a specific IDoc segment value.

Solution: The best solution is not to use tables, but instead to use the standard SAP transaction WE09. (The IDoc search for business content.) Here you can locate for example, all Sales Order IDocs that were for a specific product. (You search for a value (material) in a field (IDTNR) within a segment for example (E1EDP19) for a Basic Type for example (ORDERS05).

In some instances you may wish to use the tables in which case there are 3 main reference tables:

• Control Record Table = EDIDC
• Data Record Table = EDID4
• Status Record Table = EDIDS

Requirement: Storing the soft copies or scanned copies related Sales Document.

Steps:

1. Go to SU3, in parameter tab maintain SD_SWU_ACTIVE in parameter ID, maintain X in parameter value and save.
2. Now you will find services object on top left side corner of Sales Document.
3. You may now create/view attachments and notes to the Sales Document.

Submitted by an anonymous SAPtricks User – Thank you for contributing to the webs largest database of SAP tricks!

So picture the scenario: You see an article which is configured has been changed in the IMG, but you do not know which transport was responsible. You could search with SE10 via table names , but did you know there is an easier method?

If you are trying to locate a transport/s of a specific IMG activity or object it is very easy to do, without even using the table names, simply use transaction SE 10 with the following steps:

1) Select Transport and organizer tools (Shift +F6).

2) Select “Search for Objects in Requests/Tasks”.

3) Select 1/2 down the page for “IMG Activity” then select F4.

4) Now select the place in the IMG, the lowest drill down level possible, for which you wish to search for transports, which include those changed objects.

5) Then select the date range and Status “modifiable” or “Released” and execute.

Picture the scenario: Due to Sarbanes-Oxly or some other reason the FI part of the customer master is created by the Finance team. After which the SD part of the customer master is created by the Sales team. It is possible that the two teams have failed to communicate to eath other and customer master records can be sitting in your system as incomplete.

To report on these you can use the transaction OV50. This will show you the sales area created customer master records for which there are missing company code views, or visa versa. (A great little utility.)

You are now able to submit your own SAP tips and tricks. Find more of what you need! Engage and share content with other SAP professionals. Simply submit a Tip or Trick on the right hand side of every page. Help establish the largest resource of SAP Tips and Tricks on the web.