Symptoms

A customer requested a special transaction splitting, for example, transaction MM (Materials Management). In snapshots, they could see the URL field with some details about the transaction like: MIRO, MIR4, etc.
The customer added URL fields to the transaction name, consequently they changed a configuration of GUI automatic transaction detection to get a subcomponent name. This changed the behavior and resulted in: MM (Materials Management) changed to MM-IV (Invoice Verification), but MIRO and MIR4 did not appear on the transaction.

Reason and prerequisites

The customer had a group of TCODEs that he wanted to split with: MIRO, ME33K, and ME33N.

They were interested in:

1. Automatic transaction to split on default behavior - Priority 10

2. Manual detection to detect a list of specific TCODEs and split these transactions by them - Priority 15

The customer manually split the transactions:

Transaction ME23N was configured to be collected, a newly created transaction was not working and the ME23N transaction was grouped under "all other transactions". 

Solution

If the newly created transaction ends in "all other transactions", it means the customer exceeded the default BT limit of 50 BTs per tier or 200 BTs per whole application. This is not SAP specific issue but a limitation set by AppDynamics to limit agent-generated traffic. Solution is to increase the limits via settings in the controller or delete unused BTs to free up some space for new BTs.