Week 1 Day 3 CRM Enhancement

7/27/2019 Week 1 Day 3 CRM Enhancement

1/31

Copyright IBM Corporation 2009

IBM Global Business Services

EasyEnhancement

Work Bench


2/31


Copyright IBM Corporation 2009|

Easy Enhancement Workbench (EEWB)

New fields and tables can be added

Easy and effiecient.

Wizard for user guidance

Retains results in case of SAP upgrades.


3/31



Enhancing Product Step I

Create an attribute using transaction COMM_ATTRSET


4/31



Enhancing Product Step II

Create a Settype using transaction COMM_ATTRSET and associate the

attribute created in step I


5/31



Enhancing Product Step III

Assign the Set Type created in Step II to the Product Hierarchy using

transaction COMM_HIERARCHY


6/31



Enhancing Product Step IV

Go to transaction COMMPR01 to see the outcome


7/31



Enhancing PPR Step I

CreateSet Type and Attributes


8/31



Enhancing PPR Step II

SPROconfig needs to be done


9/31



Enhancing PPR Step III

Detail of SPRO config


10/31



Enhancing PPR Step IV

Go to PPR Transaction CRMM_PPR to see the outcome


11/31

Copyright IBM Corporation 2009


Business

Transactions -

Enhancements


12/31



Business Transaction - Enhancements

One-Order concept Technical Architecture of Business Transactions

Interaction Layer Provides integration of the User Interface with Database

Screen Control Allows to customize the screens visible in Business

Transactions.


13/31



One-Order concept

In CRM all types of transactions are technically integrated into One-Order framework.

Order consists of Segments. Examples are

ORDERADM_H

ORDERADM_I

PARTNERS

SALES

Each segment is mapped to database table.

Guid is the key to the One-Order transaction.

Interaction layer provide interface to the database layer

Different types of transactions use segments that are relevant to it to captures the data.

Eg.


14/31



Segments in different business transactions - Example

Opportunity Activity

ORDERADM_H ORDERADM_H

PARTNERS PARTNERS

OPPORT_H ACTIVITY_H

Following example illustrates how different transactions shares various segments

relevant to it and also indicate that it could it own specific segments.

.

..

.

Shared Segments

Exclusive segments

For each type oftransaction


15/31



Segments relation to Database

Some of the segments and there

corresponding database tables are

listed below

Tip

Segment Name will part of the table

name and function modules used to

read data or update,

Segment

s

Database

TablesORDERADM_H CRMD_ORDERADM_H

ORDERADM_I CRMD_ORDERADM_I

PARTNER CRMD_PARTNER

CUSTOMER_H CRMD_CUSTOMER_H

CUSTOMER_I CRMD_CUSTOMER_I

OPPORT_H CRMD_OPPORT_H

* Not all the segments are listed


16/31



Architecture

User Interface

Interaction Layer

Database Layer

Advantages

Provides Isolation of User Interface & Business logic

GUI programmers need not handle any database operations


17/31



Mapping of UI structures in Interaction Layer

CRMC_MAP transaction allows mapping of UI fields to various segment fields


18/31



Mapping of UI structures in Interaction Layer-Contd.

Each UI field is mapped to segment fields


19/31



Screen Control SAP GUI Transaction layout

Screen Control determines how the screens are displayed in SAP GUI.

Controls screens in

Customer Interaction Center (CIC)

CRMD_ORDER transaction

Screen control can be customized using the transaction CRMV_SSC. Can be used toperform the following

Change the tab order displayed in transaction

Add new custom screen in transaction

Add new custom tabs

Note: Easy Enhancement Workbench can be used to add custom fields. However EEWBenhancements always appears as a separate tab in the transactions and is always thelast tab.


20/31



Screen Control - Concepts

Screen Profile Type

Screen profile type is to identify the category of screens for a the business transaction. (eg.SALS is the screen profile type for Sales transactions in CRMD_ORDER whereas TSAL is thescreen profile for Sales transaction in CIC)

Screen Profile Allows different screens to be assigned to same category of transaction based on the

transaction type.

Panels

Holds the subscreen areas

Subscreen Areas

Subscreen areas holds the screens.

Tabstrips Panel

Holds the various tabs that are displayed


21/31



Example adding a custom tab using screen control

A custom transaction Z_OP of Opportunity

type transaction is configured to show a

custom screen.

Steps 1 Define Custom program for the

screen profile type

Configure the Function Group that contains

the custom screen.

G S


22/31



Business Transaction enhancement using EEWB

Step 1: Create a new project

IBM Gl b l B i S i


23/31



Business Transaction enhancement using EEWB contd..

Step2: Create an Extension

IBM Gl b l B i S i


24/31




Step3: Wizard is started

IBM Gl b l B i S i


25/31




Step3: Define the Title of the extension

IBM Global B siness Ser ices


26/31




Step 4: select the transaction category



27/31




Step 5: Define fields to be added



28/31




Step 6: Specify if the fields needs to be added to Header and/or item



29/31




Step 7: Specify the relevance with other functionality like BI, Mobile or for search



30/31




Step 8: Complete the Wizard



31/31



Step 8: Complete the Wizard

Date post:	02-Apr-2018
Category:	Documents
Upload:	sangoothura-vayasulay-sangeetha
View:	216 times
Download:	1 times

Week 1 Day 3 CRM Enhancement

Documents