What is a transaction?: A transaction, or business transaction, is a document used to, partly or completely, record business processes. Examples of business transactions are Sales orders, quotations, contracts, etc.

What is a transaction type?: Transaction types define the characteristics and attributes of a business transaction (e.g. whether it is a sales order, service request, or sales call), and determine how the transaction is processed (for e.g profiles and procedures used to determine texts, business partners, statuses, and organizational data). Transaction types are configured in spro>img>crm>Transactions>Basic Settings You create a new transaction type by selecting the standard transaction type of the same category, e.g. Sales Order (TA) and making a copy. All custom transaction type id’s have to be created as Z or Y (as for 99% of customizing in CRM). Do not make any changes to standard delivered transaction types, even if it is only one profile that is different, you need to make a copy. This also counts for the rest of the CRM customizing, if you cannot use the standard delivered configuration, create a new Z or Y entry.

What is a transaction header?: : A transaction always consist of a header, containing data like main business partner, creation date, description. Depending on the type of transaction the data will defer. The different aspects per transaction type will be covered in the functional parts of Sales, Marketing and Service.

What are transaction items?: : Depending on the transaction type, a transaction will or will not have line items. Line items are used to register products (or services) that are related to the transaction. E.g. a sales order cannot exist without items, a business activity doesn’t necessarily have to have any. Also this will be covered in the functional chapters