How Transaction Type Works

8/13/2019 How Transaction Type Works

1/36

HOW TRANSACTION

TYPE WORKS

Rohit Ranjan

Series How CRM Functionality Works

28-04-2011


2/36

Agenda

Definition

Purpose

Structure

Customizing Steps

Control Parameters & Basic Functions

Customizing Screenshots

Navigation Paths for Customizing

Q & A


3/36

Definition

A transaction typespecifies the characteristics and attributes ofa business transaction (for example, sales order, service request,

visit, etc,) and the control attributes (for example, partner

determination procedure, text determination procedure, status

profile, organizational data profile). A transaction type controls the

processing of a specific business transaction.

A business transaction type is assigned to one business

transaction category (for example, activity, opportunity, sales,

service). The business transaction category defines the business

context in which a business transaction type can be used.

Transaction type is similar to the document types in SAP SD.

SAP 2007 / Page 3


4/36


5/36

Purpose

A business transaction in SAP CRM portrays a business event.

You can enter items from different business contexts in one

transaction. For example, you can enter product sales, complaint

items and returns items in one transaction.

Transactions are a flexible means to control and manage

processes according to the company's requirements.

A business transaction provides business structures and functions

that can be used in the various processes of a company, for

example, in sales, marketing or service.

SAP 2007 / Page 5


6/36

Header

General data, such as:

Description, Priority

Status , Sales Cycle

Priority, Purchase order Number

Pricing Procedure..

Item

Material 2Quantity

Material 1

Quantity

Service 1

Quantity

Item specific Data, such as:

Pricing relevance

Billing relevance

ATP Relevance

Confirmation Relevance..

Business Partner

General Structure of Transactions


7/36

Structure of Sales Transaction

Transactions are divided into 3 levels :-

Header level, Item level & Schedule line level

The header data contains the general data which are applicable for the entire document

like Sold to party, Purchase order number etc

HEADER

ITEM

The Item level contains data which is applicable only for the items (e.g.) Product

number, Product Value, Item Quantity.

Schedule Line

The Schedule lines sub-divides an item according to the exact Delivery dates and

Delivery quantity according to ATP check


8/36

Define Transaction Types

Here we define the Business Transaction attributes & CharacteristicsLeading business Transaction category

Control parameters for the document

Assign Business Transaction Categories

Here depending upon the Leading Business Transaction category

we assign Additional Business Transaction categories.Sales, service, complaints.

Customizing at Header Level

Different settings according to Business Transaction Category

Assign Blocking Reasons

With respect to the Business Partner Status

Over all block, Free Goods Block.

Allowed Channels for Transaction Types

Restricting the usage of Transactions to specific channels

CRM Server, Interaction Center, Mobile sales.

Transaction: Customizing Header


9/36

Leading Transaction category

All Profiles are set here according

to the Business requirements

Business Transaction Customizing Header


10/36

Assignment of Business Transaction Category


11/36

Business Transaction: Customizing Header


12/36

Allowed Channels for Transaction Types


13/36

Transaction: Customizing Item

SAP 2007 / Page 13

Define Item Category

Here we define Item attributes & Characteristics

Controlling Attributes

Item Object type

Assign Business Transaction Categories

Here we assign Business Transaction categories.

Only certain combinations are possible

Customizing at Item Level

Different settings according to Business Transaction

Category


14/36


15/36

Assignment of Business Transaction

Categories


16/36

Business Transaction: Customizing Item


17/36 SAP 2007 / Page 17

TRANSACTION TYPE

+

Transaction ( TA )

ITEM CATEGORY GROUP Product Master (NORM)

ITEM CATEGORY USAGE Program

MAIN ITEM CATEGORY

ITEM CATEGORY( TAN )

Customizing Item Category Determination


18/36

Transaction Type

Item Category Group

( Product Master )

Item Category

Customizing: Item Category Determination


19/36

COPY CREATEFOLLOW-UP

Copies Current Transaction

document:

Same Transaction Type

Header data and Item data copied

Transaction history is not updated;

no relationship to predecessor

Copies data from a Business Transaction

We can choose the transaction

type for the follow up

Header Data is copied

You can select itemsTransaction history is Updated

Prerequisite:

We have to make the Customizing settings for

Copy control

Copying Business Transactions


20/36

Transaction history allows you to display the inter linkages

between Business Transactions at both Header & Item Level

The display of the transaction history is

context-specific and depends on each

transaction type

CRM_COPY_BADI to create own copy routines

Possible to navigate to linked transactions

from transaction history, even to connected

ECC system if ITS settings are maintained

Subsequent referencing possible using object

relationship profile

Transaction History/ Document Flow in

Transactions


21/36

Customizing: Copy Control

Transaction TypesSource Target

AG TA

Item Categories

Source Target

AGN TAN

Item Category

Determination

Source Target

AGN TANSource Target

AGN TAN

ZAG1 + TA ZTA1

Transaction Type Target Item

category

Source Item

Category

General Control

Detailed Data

General Control

Detailed Data


22/36

Define Copying Control for

Transaction Type

Define Copying Control for Item

Category

Copy Control: Customizing


23/36

Text Determination

Date Management

Status Management

Incompleteness Check

Organization Determination

Partner Processing

Action Processing

Credit Check

Availability Check

Product Substitution

Basic Functions & Control Parameters in

Business Transactions


24/36

These are the Basic Functions

which can be set for a Business

Transaction

Basic Functions in Transactions


25/36

Date management enables you to process the dates that are

relevant for you in one transaction

Examples of date types in business transactions:

Activity

Sales

Contract

Date type: Date rule:

Planned date:

Actual date: Current Date

Contract start: Current DateRuntime: One Year

Contract end: Contract start + validity period

Call customer: Contract end two weeks

Date Management


26/36

Transaction Type Item Category

Date Profile

Which date types can I use?

Which durations are included?

What attributes have been given to the dates and durations?

How are the dates determined (date rules)?

Date Management


27/36

User Status

(Customer status)

Set by User

Controlled by Status Profile

Can be set manually or triggered by a

process.

Examples:Customer Action

To Release

Released

Rejected

Triggered

System Status

(SAP standardstatus)

Its set Internally by the system

It informs the completion of certain

Business Transactions.

Examples:

OpenIn Processing

Error

Complete

Distribution Lock

Status Management


28/36

Transaction Type Item Category

StatusProfile

Definition of User Status

With or Without Status Number

Transactional Control.

Authorization Key

Status Profile


29/36

Status Profile


30/36


31/36

Incompleteness group

Transaction/item

Incompleteness Group Business

Partner

Incompleteness Procedure

Which fields are required entry fields?

Which message type is involved (error or warning)?How does the system react (for example, is

the status set to incomplete for delivery)?

You define which fields are mandatory for which transaction type and/or item

category:

Transaction Type/

Item category

Business Partner Master

data

Incompleteness Check Customizing


32/36

Incompleteness Check: Customizing

C


33/36

The system can update change documents for transactions

This allows you to display all changes made to a document,

including:

What was changed (field, old value, new value)

Who made the change

When (date and time) the change was made

You can decide for each transaction type whether changedocuments are updated.

Change History

T ti P i


34/36

Item Category Determination

SAP IMGCustomer Relationship Management Transactions Basic

SettingsDefine Item Category Determination

Copy Control

SAP IMGCustomer Relationship ManagementTransactions Basic Settings

Copying Control for Business TransactionsDefine Copying Control for Transaction

Types

Transaction Processing

T ti P i


35/36

Transaction Types

SAP IMGCustomer Relationship Management Transactions Basic Settings

Define Transaction Types

Item Category

SAP IMGCustomer Relationship Management Transactions Basic

SettingsDefine Item Category

Transaction Processing


36/36

Questions

How Transaction Type Works

Documents

Transcript of How Transaction Type Works