For checking which gl account does generic material number is posting to.

Go to mm03 -> sales org 2( tab)-> acct assignment grp

And then go to table C001 ( Cust.Grp/MaterialGrp/AcctKey )

Find GL account for account assignment grp & sales org.

Vofa tcode controls billing type

v/08 pricing procedure tcode

Find out what are the output communication structures involved in that output condition table. To find
that, go to field catalog, and enter a new field called "test". Then it will give you a message "The field test
is not a part of the communication structures KOMB, KOMPBV* KOMKBV*where * equals 1, 2 or 3 based on
whether the output is for order, delivery or billing documents. For delivery document it is KOMPBV2,
KOMKBV2 and KOMB.

Communication structures for output determination .

KOMB, KOMPBV* AND KOMKBV*
* = 1 = sales
* = 2 = delivery
* = 3 = billing

VF31 ( works just like rsnast00 but provide more selection criteria but low in performance )

Include in which we do changes for user exits in output determination procedure.

RVCOMFZZ

Find badi :
In SE80 in a client that you can run the transaction in, set a break-point in the class
"CL_BADI_FLT_DATA_TRANS_AND_DB" in the method "ACT_IMPS_PER_FLT_VAL" just after the "SELECT"
headed by the comment "read BADI attributes".

Run the transaction.

At each break-point in the debugger, examine the fields "exit_name" and "internal".

The name of the BADI is in "exit_name" and the BADI is reserved for SAP use if "internal" has a value of
"X".

There is an even quicker way to finding a BADI and BADI implementations for a transaction:

1. SE37 display Function Module - SXV_GET_CLIF_BY_NAME.

2. Set a BREAKPOINT on call function SXV_ADD_PREFIX .
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
.

1. Go to the TCode SE24 and enter CL_EXITHANDLER as object type.

2. In 'Display' mode, go to 'Methods' tab.
3. Double click the method 'Get Instance' to display it source code.
4. Set a breakpoint on 'CALL METHOD
cl_exithandler=>get_class_name_by_interface'.
5. Then run your transaction.
6. The screen will stop at this method.
 7. Check the value of parameter 'EXIT_NAME'. It will show you the BADI for
that transaction.
debug the sap process

Sometimes, an SAP process will stop working with an error message, or an abend. Unlike with a
dump, it can be difficult to find exactly where the problem occured. What you should do, is get
the technical name and number of the message - e.g. RS 100. Set a breakpoint at the start of the
process (or run the process with the debugger switched on). As soon as the debugger is in some
abap code, set a watchpoint for sy-msgno. In this example, you should set a watch point for sy-
msgno = 100. Then hit F8.

The process will continue to run until sy-msgno has the value 100.

Check that the message ID is correct, according to the message - RS in this example. If it is, then
you are at the place where the error occurs. You can usually back trace a few steps to find out
precisely what was causing that error to be triggered.

Closing a hung session :

If you have multiple SAP sessions open from one system and one of them gets hung up
on a transaction or program and you would like to stop that one session without closing
them all, you can use this transaction to end the one session.

Let's say you want to end session three. You can go to either session one or two and enter
this command in the transaction box: /i3
This will immediately close the hung up session (session three in this case).

Or you can do this the long way by going to SM04 and double-click your userid, select a
session and hit 'end session'.