Business Transaction 
Business object that depicts the following possibilities:
A business interaction with a business partner at a given time
The result of an interaction, for example, a contract
The initiation of or request for an interaction, for example, an opportunity
The collection of information in preparation for a possible business interaction, for example, an activity
The object of a (potential) interaction, for example, a sales or service transaction
Each business transaction is stored as a separate database record.
The business transaction provides business structures and functions that can be used in the various processes of a company, for example, in sales, marketing, and service.
In SAP CRM, business transactions are used in the following areas:
Sales
For example, quotation, sales order, opportunity, sales contract, sales agreement
Marketing
Lead
Service
For example, service contract, service order, service request, complaint, return, service confirmation
Activity management
For example, interaction logs, tasks
Business transactions are typically structured as follows:
Header
The header of a business transaction contains information that is relevant for the entire transaction, for example, the business partner, status of the transaction, and certain dates.
Items
Items contain the details of individual products to which the business transaction relates, and information such as the item status. Items can have subitems.
Some business transactions, for example, activities and leads, do not contain items.
You can combine items from different business contexts in one transaction. For example, in one transaction you can sell products and also enter complaint or return items.
A single business transaction can be created, displayed, and processed in various interfaces (for example, E-commerce, mobile applications, and the WebClient UI). Some business transactions can also be replicated to an integrated SAP ERP system for further processing, for example, accounting.