crm design registration for high tech
DESCRIPTION
crmTRANSCRIPT
CRM Design Registration for High Tech
Contents
CRM Design Registration for High Tech: Configuration Guide ....................................................... 3
1 Purpose .................................................................................................................................... 3
2 Prerequisites............................................................................................................................. 3
3 Notes ........................................................................................................................................ 3
4 Configuration ............................................................................................................................ 4
4.1 Settings for Basic Functions........................................................................................... 4
4.1.1 Defining Partner Processing ...................................................................................... 4
4.1.1.1 Defining Partner Functions................................................................................ 4
4.2 Settings for Scenario Activity Management ................................................................... 6
4.2.1 Settings for Basic Functions ...................................................................................... 6
4.2.1.1 Defining Partner Processing ............................................................................. 6
4.2.1.1.1 Defining Access Sequences........................................................................ 6 4.2.1.1.1.1 Defining Access Sequence Y003......................................................... 6 4.2.1.1.1.2 Defining Access Sequence Y008......................................................... 7 4.2.1.1.1.3 Defining Access Sequence YRES........................................................ 7
4.2.1.1.2 Defining Partner Determination Procedures................................................ 8 4.2.1.1.2.1 Defining Partner Determination Procedure YAPP0003 ....................... 8 4.2.1.1.2.2 Defining Partner Determination Procedure YSRQ0001....................... 9 4.2.1.1.2.3 Defining Partner Determination Procedure YOEM0001 .................... 12
4.2.2 Settings for Transactions ......................................................................................... 12
4.2.2.1 Defining Transaction Types ............................................................................ 13
4.2.2.1.1 Transaction Type Sample Request YSRQ................................................ 13
4.2.2.1.2 Transaction Type Approve YAPP.............................................................. 14
4.2.2.1.3 Transaction Type OEM Activity YOEM...................................................... 14
4.2.2.2 Defining Item Category Determination............................................................ 15
4.2.3 Activity Journal......................................................................................................... 16
4.2.3.1 Creation of Standard Activity Journal Template Type..................................... 17
4.2.3.2 Maintaining Activity Journal Template Type (Optional) .................................. 17
4.3 Settings for Design Registration Process .................................................................... 18
4.3.1 Settings for Basic Functions .................................................................................... 18
4.3.1.1 Defining Partner Processing ........................................................................... 18
4.3.1.1.1 Defining Access Sequence YSAM ............................................................ 18 4.3.1.1.1.1 Defining New Function Module .......................................................... 18 4.3.1.1.1.2 Maintain Determination Rule .............................................................. 19 4.3.1.1.1.3 Define Access Sequences ................................................................. 19
4.3.1.1.2 Defining Partner Determination Procedures.............................................. 20 4.3.1.1.2.1 Defining Partner Determination Procedure YDRP0001 ..................... 20 4.3.1.1.2.2 Defining Partner Determination Procedure YDRA0001 ..................... 21 4.3.1.1.2.3 Defining Partner Determination Procedure YDRO0001..................... 22 4.3.1.1.2.4 Defining Partner Determination Procedure YDRO0002..................... 23
4.3.1.2 Actions............................................................................................................. 23
4.3.1.2.1 Creating Actions with Wizard..................................................................... 24
4.3.1.2.2 Defining Action Profiles and Actions.......................................................... 25
4.3.1.2.3 Defining Conditions.................................................................................... 26
4.3.2 Settings for Design Registration Projects/Opportunities.......................................... 26
4.3.2.1 Defining Authorization Code for Status........................................................... 26
4.3.2.2 Defining Status Schemes................................................................................ 27
4.3.2.2.1 Defining Status Scheme Y_DRGP ............................................................ 27
4.3.2.2.2 Defining Status Scheme Y_DRGO ............................................................ 28
4.3.2.2.3 Defining Status Scheme YDROPP_I ......................................................... 29
4.3.2.3 Sales Cycle and Phases ................................................................................. 29
4.3.2.3.1 Defining Sales Cycle.................................................................................. 29
4.3.2.3.2 Defining Phases......................................................................................... 31
4.3.2.3.3 Assigning Phases to Sales Cycles ............................................................ 32
4.3.2.4 Defining OEM Project Status .......................................................................... 33
4.3.3 Settings for Transactions ......................................................................................... 33
4.3.3.1 Defining Transaction Types ............................................................................ 33
4.3.3.1.1 Defining Transaction Type BP DR Project YDRP ..................................... 33
4.3.3.1.2 Defining Transaction Type Assembly YRGA............................................. 35
4.3.3.1.3 Defining Screen Layout for new Transaction Type ................................... 36
4.3.3.1.4 Defining Transaction Type DR Opportunity YORG ................................... 36
4.3.3.1.5 Defining Item Category YORG .................................................................. 38
4.3.3.1.6 Defining Item Category Determination ...................................................... 39
4.3.3.1.7 Defining Copying Control for Transaction Types....................................... 39
4.3.3.1.8 Defining Copying Control for Item Categories ........................................... 40
4.3.3.1.9 Selecting Relevant Transaction Types ...................................................... 40
4.3.3.2 Maintaining Status Reason and Status Profile for Opportunities.................... 41
4.3.3.2.1 Define Catalog ........................................................................................... 41
4.3.3.2.2 Defining Code Groups and Codes for Catalogs ........................................ 42
4.3.3.2.3 Defining Code Group Profiles.................................................................... 43
4.3.3.2.4 Defining Subject Profile ............................................................................. 44
4.3.3.2.5 Assign Status Profile and Subject Profile to Business Transaction Type . 45
4.3.4 Sales Methodology .................................................................................................. 45
4.3.4.1 Defining Questionnaires.................................................................................. 45
4.3.4.2 Defining Determination for Questionnaires ..................................................... 48
4.3.4.3 Assign Questionnaire to Transaction Type ..................................................... 48
4.4 Settings for Scenario Contract Management ............................................................... 49
4.4.1 Settings for Basic Functions .................................................................................... 49
4.4.1.1 Defining Partner Processing ........................................................................... 49
4.4.1.1.1 Defining Partner Determination Procedure................................................ 49
4.4.2 Settings for Transactions ......................................................................................... 49
4.4.2.1 Defining Transaction Type Quant./Value Contr. YQVC .................................. 49
4.4.2.2 Defining Item Category Determination............................................................ 50
4.4.2.3 Defining Copying Control for Transaction Types ............................................ 51
4.4.2.4 Defining Copying Control for Item Categories ................................................ 52
4.5 Settings for Master Data .............................................................................................. 52
4.5.1 Maintaining Design Registrable Attributes for Products .......................................... 52
4.5.2 Maintaining PPR Settings for Design Registration .................................................. 53
CRM Design Registration for High Tech: Configuration Guide
1 Purpose This configuration guide provides the information you need to set up the configuration of this building block manually.
2 Prerequisites Before you begin with the installation, please also refer to the scenario configuration guide for this scenario.
3 Notes Before you begin the installation and configuration, read the relevant SAP Notes. These SAP Notes contain important information for installation and configuration.
Make sure that you have the most up-to-date version of SAP Notes. You can find the SAP Notes on the SAP Service Marketplace (http://service.sap.com/notes) or in SAPNet.
SAP Notes that are relevant for SAP CRM Design Registration Scenario:
SAP Note Number Description Valid until Release
824897 Design Reg. error message when product is registrable 4.0 SP08
811016 Registrable products check not done when document is copied
4.0 SP08
4 Configuration
4.1 Settings for Basic Functions
4.1.1 Defining Partner Processing
In this section you do the settings for partner processing. You should carry out the following:
1. Define partner functions
2. Define access sequences
3. Define partner determination procedures in which you specify an access sequence
4. Assign the partner determination procedures to the required business transaction types and item categories.
4.1.1.1 Defining Partner Functions
Use
In this activity, you define partner functions by entering short descriptions (such as Distributor or Project owner) that are used in the scenario for Design Registration. The partner functions are assigned to partner function categories and the usages, Customer Relationship Management. In some cases, you also specify a corresponding business partner relationship category.
The descriptions you enter here are displayed in the transactions that include these partner functions.
Procedure
1. To carry out the activity, choose one of the following navigation options:
Transaction Code SPRO
IMG Menu Customer Relationship Management � Basic Functions � Partner Processing � Define Partner Functions
2. Choose New Entries and enter the following data:
Partner Function
Text Abbrev. Function category
Usage
Y0000001 Individual Contributor
INDC Employee Customer Relationship Managem.
Y0000002 Project Owner POWN Employee Customer Relationship Managem.
Y0000003 Assembly Owner AOWN Employee Customer Relationship Managem.
Y0000004 Design Reg Owner ROWN Employee Customer Relationship Managem.
Y0000005 Approving Manager APPR Employee Customer Relationship Managem.
Y0000006 Account Manager AMAN Employee Customer Relationship Managem.
Y0000007 OEM Contact OEMC Contact Customer Relationship
Partner Function
Text Abbrev. Function category
Usage
person Managem.
Y0000008 Distributor Contact DIC Contact person
Customer Relationship Managem.
Y0000009 Contract Manu. Contact
CMC Contact person
Customer Relationship Managem.
Y0000010 Product Line Responsible
PLR Employee Customer Relationship Managem.
Y0000011 Contract Manufacturer
CMAN Sales Partners
Customer Relationship Managem.
Y0000012 Distributor DIS Sales Partners
Customer Relationship Managem.
Y0000013 OEM End Customer DOEM Activity Partner
Customer Relationship Managem.
Table continued:
Relation category Block
Is the Responsible Employee For X
Is the Responsible Employee For X
Is the Responsible Employee For X
Is the Responsible Employee For X
Is the Responsible Employee For X
Is the Responsible Employee For X
Is Contact Person For X
Is Contact Person For
Is Contact Person For
Is the Responsible Employee For X
X
X
Is Activity Partner For X
3. Save your entries.
4.2 Settings for Scenario Activity Management
4.2.1 Settings for Basic Functions
4.2.1.1 Defining Partner Processing
In this section you do the settings for partner processing. You should carry out the following:
1. Define access sequences
2. Define partner determination procedures in which you specify an access sequence
4.2.1.1.1 Defining Access Sequences
4.2.1.1.1.1 Defining Access Sequence Y003
Use
The purpose of this activity is to define a new access sequence for the determination of the partner function Sales Representative for the document flow from DR Opportunity to activity Sample Request. This is necessary because of the differences of used partner functions in the normal sales process transactions and the specific partner functions for the design registration process.
Prerequisites
The standard access sequence 0003 – Business Partner Relationships: Activity Partner -> User exists.
Procedure
1. To carry out the activity, choose one of the following navigation options:
Transaction Code SPRO
IMG Menu Customer Relationship Management → Basic Functions →
Partner Processing → Define Access Sequences
2. Select sequence 0003 – Business Partner Relationships: Activity Partner → User and copy
as Y003 – BP Preceding Document → Business Partner Relationships: Activity Partner → User with all entries.
3. Go to Individual Accesses and add new entry:
Attribute Value
Batch Seq: 0005
Dialog Seq: 0005
Source Preceding Document
The Employee Responsible is determined from the Sales Area Manager when creating a follow-up task Approve in High Tech scenario. Otherwise this function would be filled with Employee Responsible of the preceding document or the current User.
4. Save your settings.
4.2.1.1.1.2 Defining Access Sequence Y008
Use
The purpose of this activity is to define a new access sequence for the determination of the partner function Employee Responsible for the document flow from DR Opportunity to task Approve This is necessary because of the differences of used partner functions in the normal sales process transactions and the specific partner functions for the design registration process.
Prerequisites
The standard access sequence 0008 – Preceding Document User exists.
Procedure
1. To carry out the activity, choose one of the following navigation options:
Transaction Code SPRO
IMG Menu Customer Relationship Management → Basic Functions →
Partner Processing → Define Access Sequences
2. Select sequence 0008, Preceding Document User and copy as Y008, BP Prec. Doc Sales
Area Manager → Preceding Document → User with all entries.
3. Go to Individual Accesses and add new entry:
Attribute Value
Batch Seq: 0005
Dialog Seq: 0005
Source Preceding Document
The Employee Responsible is determined from the Approving Manager when creating a follow-up task Approve in High Tech scenario. Otherwise this function would be filled with person responsible of the preceding document or the current User.
4. Save your settings.
4.2.1.1.1.3 Defining Access Sequence YRES
Use
The purpose of this activity is to define a new access sequence for the determination of the partner function Employee Responsible for the document flow from DR Opportunity to activity OEM Activity. This is necessary because of the differences of used partner functions in the normal sales process transactions and the specific partner functions for the design registration process.
Procedure
1. To carry out the activity, choose one of the following navigation options:
Transaction Code SPRO
IMG Menu Customer Relationship Management → Basic Functions →
Partner Processing → Define Access Sequences
2. Choose New Entries and enter YRES – BP Preceding Document Responsible Person or Employee.
3. Go to Individual Accesses and add new entry:
Attribute Value
Batch Seq: 0010
Dialog Seq: 0010
Source Preceding Document
Mapping/Definition for Partner being searched
Funct. Cat. in Source Employee (0005)
Usage in Source Customer Relationship Management
Thus Employee Responsible is determined from all partner functions of category Employee or Person Responsible when creating a follow-up.
4. Save your settings.
5. Go Back (F3).
6. Choose New Entries and enter the following data:
Attribute Value
Batch Seq: 0020
Dialog Seq: 0010
Source Preceding Document
Mapping/Definition for Partner being searched
Funct. Cat. in Source Person Responsible (0008)
Usage in Source Customer Relationship Management
7. Save your settings.
4.2.1.1.2 Defining Partner Determination Procedures
4.2.1.1.2.1 Defining Partner Determination Procedure YAPP0003
Procedure
1. To carry out the activity, choose one of the following navigation options:
Transaction Code SPRO
IMG Menu Customer Relationship Management → Basic Functions →
Partner Processing → Define Partner Determination Procedures
2. Choose New Entries and enter the following data:
Attribute Value
Procedure YAPP0003
Description BP Task Approve
Permitted Functions Only Functions Assigned in Procedure
3. Go to Folder Procedure User and choose New Entries.
4. Enter as user Task.
5. Go to folder Partner Functions in Procedure and choose New Entries.
6. Make the following entries for partner function 00000014 Employee Responsible (CRM):
Attribute Value
No. of Occurrences (Lowest) 1
No. of Occurrences (Highest) 5
Changeable (if Correct After Entry or Determination)
Calendar maintenance
Access Sequence Y008 (BP Prec. Doc Sales Area
Manager → Preceding Document
→ User)
Determination Recurring
7. Go to folder User Interface Settings and change Partner Function 1 to: ‘00000014 Employee Responsible (CRM)’.
8. Save your entries.
In section Settings for Transactions the Partner Procedure is assigned to the relevant transaction type.
4.2.1.1.2.2 Defining Partner Determination Procedure YSRQ0001
Procedure
1. To carry out the activity, choose one of the following navigation options:
Transaction Code SPRO
IMG Menu Customer Relationship Management → Basic Functions →
Partner Processing → Define Partner Determination Procedures
2. Choose New Entries and enter the following data
Attribute Value
Procedure YSRQ0001
Description BP Sample Request Activity
Permitted Functions Only Functions Assigned in Procedure
3. Go to folder Procedure User and choose New Entries.
4. Enter as user Business Activity.
5. Select procedure YSRQ0001 – BP Sample Request Activity and go to folder ‘Partner Functions in Procedure’.
6. Make the following entries for partner function 00000014 Employee (CRM):
7. Assign the following functions and the appropriate settings to procedure YSRQ0001:
The following settings have to be applied to all partner functions.
Attribute Value
Changeable
Determination Recurring
Characteristics Generally Valid Group
Fu
ncti
on
No
. o
f O
ccu
rren
ce
s
(Lo
west)
No
. o
f O
ccu
rren
ce
s
(Hig
hest)
Sele
cti
on
Lim
it
(Sele
ct.
Scre
en
)
Cale
nd
ar
Main
ten
an
ce
Ch
an
geab
le A
dd
ress
Acce
ss S
eq
uen
ce
00000012 Sales Representative (CRM)
10 2 � Y003 BP Preceding Document → Business Partner Relationships: Activity
Partner → User
00000014 Employee Responsible (CRM)
1 1 �
Y0000001 Individual Contributor (CRM)
1 � 1000 Preceding Document
Y0000002 Project Owner (CRM)
1 1000 Preceding Document
Y0000003 Assembly Owner (CRM)
1 1000 Preceding Document
Fu
ncti
on
No
. o
f O
ccu
rren
ce
s
(Lo
west)
No
. o
f O
ccu
rren
ce
s
(Hig
hest)
Sele
cti
on
Lim
it
(Sele
ct.
Scre
en
)
Cale
nd
ar
Main
ten
an
ce
Ch
an
geab
le A
dd
ress
Acce
ss S
eq
uen
ce
Y0000004 Design Reg Owner (CRM)
1 1000 Preceding Document
Y0000005 Sales Area Manager (CRM)
1 1000 Preceding Document
Y0000006 Account Manager (CRM)
1 1000 Preceding Document
Y0000007 OEM Contact (CRM)
10 � 0002 Preceding Document -> Business Partner Relationships: Activity Partner 1
Y0000008 Distributor Contact (CRM)
10 � 1000 Preceding Document
Y0000009 Contract Manu. Contact (CRM)
10 � 1000 Preceding Document
Y0000010 Product Line Responsible (CRM)
1 1000 Preceding Document
Y0000011 Contract Manufacturer (CRM)
1 � 1000 Preceding Document
Y0000012 Distributor (CRM)
1 � 1000 Preceding Document
Y0000013 OEM End Customer (CRM)
1 � 0019 Preceding Document: Activity
Partner → Preceding Document Sold-to
8. Go to folder User Interface Settings and make the following entries:
Attribute Value
Partner Function1 Y0000013 OEM End Customer (CRM)
Partner Function2 Y0000007 OEM Contact
Partner Function3 00000014 Employee Responsible
Display Variant 0101 Partner number / Number type / Address
9. Save your entries.
In section Settings for Transactions the Partner Procedure is assigned to the relevant transaction type.
4.2.1.1.2.3 Defining Partner Determination Procedure YOEM0001
Prerequisite
The partner determination procedure YSRQ0001 from the previous step exists.
Procedure
1. To carry out the activity, choose one of the following navigation options:
Transaction Code SPRO
IMG Menu Customer Relationship Management → Basic Functions →
Partner Processing → Define Partner Determination Procedures
2. Select the Procedure YSRQ0001 – BP Sample Request Activity and choose Copy As (F6).
3. As name for the Procedure enter YOEM0001 – BP OEM Activity.
4. Press ENTER.
5. Choose Copy all.
6. Select your newly created Procedure.
7. Go to folder Partner Functions in Procedure in the dialog structure.
8. Select partner function Employee Responsible and enter the access sequence – BP Preceding Document Responsible Person or Employee (YRES).
9. Save your entries.
In section Settings for Transactions the Partner Procedure is assigned to the relevant transaction type.
4.2.2 Settings for Transactions
Use
A transaction type controls the processing of a specific business transaction. It defines the properties and characteristics (for example, sales order, service request, sales call) and defines further on the control attributes (for example, text determination procedure, partner determination procedure, status profile, organizational data profile).
A transaction type is assigned to one or several business transaction categories. This category determines the business context in which the transaction type can be used (for example, service, sales, activity). One business transaction category must be defined as the leading category. This one is not related hierarchically to other transaction categories, but represents a preference. A sales transaction with business activity data would, for example, be more likely to have sales as leading business transaction category than business activity. Depending on the leading business transaction category, only specific combinations are possible with further business transaction categories.
The purpose of this activity is to extend and adapt the available transaction types.
4.2.2.1 Defining Transaction Types
4.2.2.1.1 Transaction Type Sample Request YSRQ
Procedure
1. To carry out the activity, choose one of the following navigation options:
Transaction Code SPRO
IMG Menu Customer Relationship Management →Transactions → Basic
Settings → Define Transaction Types
2. Copy the following transaction type to the new transaction type with the following description.
Trans. Type Description New Trans. Type
Description
0020 Bus.Act.:With Prods YSRQ BP Sample Request
3. Set this new transaction type to active.
4. Change the settings of the transaction type in the following way.
Description BP Sample Request
Profile ID Description
Text Determination Proc.
ACT00001 Business Activities
Partner det. proc. YSRQ0001 BP Sample Request Activity
Status Profile CRMACTIV CRM Activity
Org. data prof. 000000000005 Org. Data Profile for Order (Header)
Date Profile 000000000001 Activity: Planned / Actual / Plan Compl.
Action Profile
5. Assign new Categories and Directions to the Transaction Type at the Customizing header level for business transaction category Business Activity.
Trans. Type Description Category Direction
YSRQ Sample Request Various Outbound
6. Save your entries.
4.2.2.1.2 Transaction Type Approve YAPP
Procedure
1. To carry out the activity, choose one of the following navigation options:
Transaction Code SPRO
IMG Menu Customer Relationship Management →Transactions → Basic
Settings → Define Transaction Types
2. Copy the following transaction type to the new transaction type with the following description.
Trans. Type Description New Trans. Type
Description
1003 Tasks YAPP BP Approve
3. Set this new transaction type to active.
4. Change the settings of the transaction type in the following way.
Description BP Approve
Profile ID Description
Text Determination Proc.
ACT00002 Task
Partner det. proc. YAPP0003 BP Task Approve
Status Profile CRMACTIV CRM Activity
Org. data prof. 000000000005 Org. Data Profile for Order (Header)
Date Profile 000000000005 Task: Plan / Actual
Action Profile
5. In the Dialog Structure hierarchy choose Assignment of Business Transaction Categories and select transaction category Task.
6. In the customizing header for Task make the following entries:
Field name Description User action and values Notes
Category <Leave blank>
Priority Medium
Direction <Leave blank>
Subject Profile Activity Reason
7. Save your changes.
4.2.2.1.3 Transaction Type OEM Activity YOEM
Procedure
1. To carry out the activity, choose one of the following navigation options:
Transaction Code SPRO
IMG Menu Customer Relationship Management →Transactions → Basic
Settings → Define Transaction Types
2. Copy the following transaction type to the new transaction type with the following description.
Trans. Type Description New Trans. Type
Description
0020 Bus.Act.:With Prods YOEM BP OEM Activity
3. Set this new transaction type to active.
4. Change the settings of the transaction type in the following way.
Description BP OEM Activity
Profile ID Description
Text Determination Proc.
ACT00001 Business Activities
Partner det. proc. YOEM0001 BP OEM Activity
Status Profile CRMACTIV CRM Activity
Org. data prof. 000000000005 Org. Data Profile for Order (Header)
Date Profile 000000000001 Activity: Planned / Actual / Plan Compl.
Action Profile ACTIVITY Activities
8. In the Dialog Structure hierarchy choose Assignment of Business Transaction Categories and select transaction category Business Activity.
9. In the customizing header for Business Activity make the following entries:
Field name Description User action and values Notes
Category Meeting
Priority Medium
Direction Outbound
Subject Profile Activity Reason
10. Save your changes.
4.2.2.2 Defining Item Category Determination
Use
In this process, you can define, per business transaction category and item category group, which item categories the system defaults for processing business transactions. At the same time, you can define which item categories can alternatively be entered manually for system default. A maximum of three alternative item categories are possible.
Prerequisite
The entries for transaction type 0020 exist.
Procedure
1. To carry out the activity, choose one of the following navigation options:
SAP CRM Define Item Category Determination
Transaction Code SPRO
IMG Menu Customer Relationship Management → Transactions → Basic
Settings → Define Item Category Determination
2. Select the entries for transaction type 0020 and choose Copy As… (F6):
Trans. Type
Description Trans.
Item cat. usage
Item Category
Alt. itm cat. 1
Alt. itm cat. 2
YSRQ Sample Request --- ACT ACT0 ACT1
YSRQ Sample Request ACT0 Bus.Act.:Mat. Return
ACT0 ACT ACT1
YSRQ Sample Request ACT1 Bus.Act.:Mat. Request
ACT1 ACT ACT0
3. Save your entries.
4.2.3 Activity Journal
Use
You can use activity journals in activities to record and update information gathered from customer visits or meetings. The information in the activity journal may or may not be product-related. An activity journal can contain the following information:
• Type and number of products discussed with or samples handed out to customers.
• Position of products in store, for example, are they placed on promotional shelf? Are they placed at the check-out or near the entrance of the store?
• Customer feedback
The information gathered in activity journals can be used to:
• Track the distribution of samples
• Analyse sales data, for example, number of products handed out to customers
• Track the progress of your sales team, for example, the number of discussions held with customers, and the result of these discussions
• Detect possible problem areas, for example, slow and non-moving products
Prerequisites
Before you can work with activity journals, you need to have defined an activity journal template type and (optional) an activity journal template. Both the activity journal template type and template can be used to store products with an activity. You can additionally use the template to work with pre-filled products.
Specifics of CRM Enterprise:
Two wizards are available for creating activity journal template types and templates in the SAP
Easy Access Menu under Activities →Maintain Activity Journal Template Type and Maintain Activity Journal Template.
Industry-Specific Fields in Activity Journals:
You can insert industry-specific fields and corresponding selection lists (drop-down lists) into your activity journals, which you can use to enter information on specific topics, for example, main location placement of goods or promotion price in store.
Before you can insert industry-specific fields, you must carry out the activity described in the
documentation under Customizing for CRM → Transactions →Settings for Activities → Activity
Journal →Industry-Specific Fields → Define Industry-Specific Fields. Once you have carried out this activity, you can maintain the required selection lists in the Customizing activities under the node referred to above. But this is optional.
4.2.3.1 Creation of Standard Activity Journal Template Type
Use
In this activity, you activate the standard activity journal template type, which is part of the standard delivery. You can use the standard template type to copy products from preceding documents to activity journals, or to copy products from activity journals to follow-up transactions. For example, products from an opportunity are automatically copied to the corresponding activity journal template type when you use the standard activity journal template type. This template type is valid for all transaction types, categories and date ranges.
Note that you carry out this activity only once. Once you have created the standard template type, you cannot make any changes to it, such as add new fields, and you cannot assign a transaction type or an activity journal template to it.
Procedure
1. To carry out the activity, choose one of the following navigation options:
Transaction Code CRM_ACT_STD_JRNL
IMG Menu Customer Relationship Management → Transactions →
Settings for Activities → Activity Journal → Vorlagenart für Standardaktivitätsbericht anlegen
2. Enter the required languages, for example EN.
3. Choose Execute (F8).
4. Confirm the following dialog box with Enter.
Result
You have created an SAP Standard activity template type SAP_TYPE to copy items from preceding documents to activities.
4.2.3.2 Maintaining Activity Journal Template Type (Optional)
Use
The template type is a pre-defined form, which contains fields which you have defined for reporting information in. You can use this form as a basis for defining a pre-filled template. You can use the template type to define which fields you want to see when you open the activity journal, for example, which products the fields are pre-filled with. You can also add your own fields you want to fill with information, such as result, reason for result, product priority, product status. Use the wizard to create a template type for the activity journal.
Procedure
1. To carry out the activity, choose one of the following navigation options:
Transaction Code CRM_ACT_JR_TMPT_TYPE
SAP Menu Activities → Maintain Activity Journal Template Type
2. Choose Continue.
3. Enter Template Type YSRQ and choose Continue.
4. Enter Description BP Sample Request, select fields Samples History, Number of Samples and Request and choose Continue.
5. Choose Transaction Type YSRQ BP Sample Request and choose Continue
6. Continue with next steps and release the template type.
4.3 Settings for Design Registration Process
4.3.1 Settings for Basic Functions
4.3.1.1 Defining Partner Processing
4.3.1.1.1 Defining Access Sequence YSAM
Use
The purpose of this activity is to define a new access sequence for the determination of the partner function Sales Area Manager for the document flow from DR Assembly to DR Opportunity.
Prerequisites
The standard access sequence 1000 – Preceding Document exists.
4.3.1.1.1.1 Defining New Function Module
Procedure
1. To carry out the activity, choose one of the following navigation options:
Transaction Code SE80
SAP Menu Architecture and Technology → ABAP Workbench → Overview
→ Object Navigator
2. Choose function group SWXA in the navigation area.
3. Open the folder function modules.
4. Click on the function module SWX_GET_MANAGER Copy... with right mouse button to copy the function module.
5. Enter ZZ_SWX_GET_MANAGER in field To Function module.
6. Press ENTER.
7. Click Create (F8) to create a new Workbench Request.
8. Enter an appropriate description for the request and press Save.
9. Press Continue (ENTER).
10. Double-click the function module ZZ_SWX_GET_MANAGER to open the source code.
11. Switch to change mode (CTRL+F1).
12. Change the following code:
Original Code * Get the org-object under consideration.
SWC_GET_ELEMENT AC_CONTAINER 'ORG_OBJECT' ORG_OBJECT.
Changed Code * Get the org-object under consideration.
SWC_GET_ELEMENT AC_CONTAINER 'SA_RESPORG' ORG_OBJECT.
13. Press the button Activate (Ctrl+F3) to activate the changed function module.
4.3.1.1.1.2 Maintain Determination Rule
Procedure
1. Choose the following navigation option:
Transaction Code PFAC
IMG Menu Customer Relationship Management → Master Data →
Organizational Management → Organizational Data
Determination → Change Rules and Profiles � Maintain Determination Rules
2. Enter rule 10000162.
3. Choose Copy (F8) and enter the following data:
Field name User action and values Note
Object Abbreviation Z_APPR_MANAG
Object name Approving Manager for resp. org. unit
4. Enter your own package in the following dialog box.
5. Create a new workbench request for the new determination rule.
6. Choose Change (F5) to change the newly created rule and change the function module from CRM_ORGMAN_ORGOBJECTS_FIND_2 to ZZ_SWX_GET_MANAGER.
7. Save your changes.
4.3.1.1.1.3 Define Access Sequences
Procedure
1. Choose the following navigation option:
SAP CRM Define Access Sequences
Transaction Code SPRO
IMG Menu Customer Relationship Management → Basic Functions →
Partner Processing → Define Access Sequences
2. Select sequence 1000 – Preceding Document and copy as YSAM – BP Prec. Doc Sales Area Manager -> Manager of resp. Sales Org. with all entries.
3. Go to Individual Accesses and add new entry and select the new determination rule Z_APPR_MANAG in field Determination Rule: Org.Data Model:
Field name User action and values Note
Batch Seq: 0020
Dialog Seq: 0020
Field name User action and values Note
Source Organizational Data
Determination Rule: Org.Data Model
Z_APPR_MANAG Generated in previous step
Thus Approving Manager is determined from the preceding document when creating the DR Opportunity in High Tech scenario. Otherwise this function would be filled with person assigned to the head of postion of the responsible sales organization.
4. Save your settings.
4.3.1.1.2 Defining Partner Determination Procedures
4.3.1.1.2.1 Defining Partner Determination Procedure YDRP0001
Prerequisite
The partner determination procedure YSRQ0001 from the previous step exists.
Procedure
1. To carry out the activity, choose one of the following navigation options:
Transaction Code SPRO
IMG Menu Customer Relationship Management → Basic Functions →
Partner Processing → Define Partner Determination Procedures
2. Select Procedure YSRQ0001 – BP Sample Request Activity and copy as YDRP0001 – BP Design Registration Proj. (with all entries).
3. Select Procedure YDRP0001 – BP Design Registration Proj. and go to folder ‘Procedure User’.
4. Delete the entry Business Activity.
5. Choose New Entries and select Project.
6. Go to folder ‘Partner Functions in Procedure’.
7. Delete partner function 00000014 Employee Responsible (CRM).
8. Select partner function Y0000002 Project Owner (CRM) and change the access sequence from 1000 – Preceding Document to 0004 – User.
9. Go to folder User Interface Settings and change Partner Function settings to:
Attribute Value
Partner Function1 Y0000013 OEM End Customer (CRM)
Partner Function2 Y0000012 Distributor (CRM)
Partner Function3 Y0000002 Project Owner (CRM)
Display Variant 0102 Address / Number type
10. Save your entries.
In section Transaction Types the Partner Procedure is assigned to the relevant transaction type.
Result
You have created a new Partner Determination Procedure for transaction type DR Project.
4.3.1.1.2.2 Defining Partner Determination Procedure YDRA0001
Prerequisite
The partner determination procedure YDRP0001 – BP Design Registration Proj. from the previous step exists.
Procedure
1. To carry out the activity, choose one of the following navigation options:
Transaction Code SPRO
IMG Menu Customer Relationship Management → Basic Functions →
Partner Processing → Define Partner Determination Procedures
2. Select Procedure YDRP0001 – BP Design Registration Proj. and copy as YDRA0001 – BP Design Registration Assemb. (with all entries).
3. Select Procedure YDRA0001 – BP Design Registration Assemb. and go to folder ‘Partner Functions in Procedure’.
4. Select partner function 00000012 Sales Representative (CRM) and change the access sequence from Y003 BP Preceding Document -> Business Partner Relationships: Activity
Partner → User to 1000 – Preceding Document.
5. Select partner function Y0000002 Project Owner (CRM) and change the access sequence from 0004 – User to 1000 – Preceding Document.
6. Select partner function Y0000003 Assembly Owner (CRM) and change the access sequence from 1000 – Preceding Document to 0004 – User.
7. Go to folder User Interface Settings and clear all settings:
Attribute Value
Partner Function1
Partner Function2
Partner Function3
Partner Function4
Display Variant
8. Save your entries.
In section Transaction Types the Partner Procedure is assigned to the relevant transaction type.
Result
You have created a new Partner Determination Procedure for transaction type DR Assembly.
4.3.1.1.2.3 Defining Partner Determination Procedure YDRO0001
Prerequisite
The partner determination procedure YDRP0001 – BP Design Registration Proj. from the previous step exists.
Procedure
1. To carry out the activity, choose one of the following navigation options:
Transaction Code SPRO
IMG Menu Customer Relationship Management → Basic Functions →
Partner Processing → Define Partner Determination Procedures
2. Select Procedure YDRP0001 – BP Design Registration Proj. and copy as YDRO0001 – BP Design Registration Opp. (with all entries).
11. Select Procedure YDRO0001 – BP Design Registration Opp. and go to folder ‘Procedure User’.
3. Delete the entry Business Project.
4. Choose New Entries and select Opportunity.
5. Go to folder ‘Partner Functions in Procedure’.
6. Select partner function Y0000002 Project Owner (CRM) and change the access sequence from 0004 – User to 1000 – Preceding Document.
7. Select partner function Y0000004 Design Reg Owner (CRM) and change the access sequence from 1000 – Preceding Document to 0008 – Preceding Document --> User.
8. Select partner function Y0000005 Sales Area Manager (CRM) and change the access sequence from 1000 – Preceding Document to YSAM – BP Prec. Doc. Sales Area Manager
→ Manager of resp. Sales Org.
9. Go to folder User Interface Settings and change the settings to:
Attribute Value
Partner Function1 Y0000013 OEM End Customer (CRM)
Partner Function2 Y0000012 Distributor (CRM)
Partner Function3 Y0000004 Design Reg Owner (CRM)
Partner Function4 Y0000005 Approving Manager (CRM)
Display Variant 0102 Address / Number type
10. Save your entries.
In section Transaction Types the Partner Procedure is assigned to the relevant transaction type.
Result
You have created a new Partner Determination Procedure for transaction type DR Assembly.
4.3.1.1.2.4 Defining Partner Determination Procedure YDRO0002
Prerequisite
The partner determination procedure YDRO0001 – BP Design Registration Opp. from the previous step exists.
Procedure
1. To carry out the activity, choose one of the following navigation options:
Transaction Code SPRO
IMG Menu Customer Relationship Management → Basic Functions →
Partner Processing → Define Partner Determination Procedures
2. Select Procedure YDRO0001 – BP Design Registration Opp. and copy as YDRO0002 – BP Design Reg.Opp. Item (with all entries).
3. Select Procedure YDRO0002 – BP Design Reg.Opp. Item and go to folder ‘Procedure User’.
4. Delete the entry Business CRM Opportunity.
5. Choose New Entries and select CRM Opportunity Item.
6. Set the Block Determination indicator for the partner determination procedure YDRO0002.
7. Save your settings.
4.3.1.2 Actions
Use
Actions in CRM use the Post Processing Framework (PPF). The Post Processing Framework is a Basis component, which generates actions (for example, sales call or workflow) from the data for an application according to an action definition (for example, a follow-up sales activity). The actions are processed at a specific time. The PPF provides the tools for planning, starting and monitoring the actions.
The purpose of this activity is to create an action profile and templates for actions. When creating an action profile, note for which business transaction type you can use this action profile. You must assign the relevant business object type to the action profile. The assignment of the business object type makes sure that the attributes for the relevant business transaction type (for example, business activity) can be used for defining and processing the conditions. Only one business object can be assigned for each action profile. You can find out the business object type for the transaction type or the item category in Customizing for transactions under Define
transaction types or Define item categories.
All maximum allowed actions are defined for a transaction type. You also specify general conditions in the action profile for the actions contained in the profile.
In this activity, you create an action profile and templates for actions.
4.3.1.2.1 Creating Actions with Wizard
Procedure
1. To carry out the activity, choose one of the following navigation options:
SAP CRM Create Actions with wizard
Transaction Code CRMC_ACTION_WIZARD
IMG Menu Customer Relationship Management → Basic Functions →
Actions → Actions in Transaction → Create Actions with wizard
2. Start the wizard and follow the steps described.
3. Continue with the next step.
4. Select the radio button Create New Action Profile and enter the following data:
Field Field Entry
Action Profile Y_DESIGN_REG_ASSISTANT
Description BP Action Profile for Design Registration
Object Type BUS2000111
5. Continue with the next step to specify a name and description of the action.
Field Field Entry
Action Definition YORG: ACTIVITY 1
Description Approval: Set Status "In Process" of related DR Opportunity
6. Continue with the next step to specify the action details.
Field Field Entry
Prcessing Time Processing when saving document
Schedule Automatically
Display in Toolbox
Chngbl in Dialog
Executable in Dialog
7. Continue with the next step without any entries and go to the next step.
8. Select the processing type Method Call and continue with settings for the method call.
9. Select the method COPY_DOCUMENT via F4-Help.
Field Field Entry
Method COPY_DOCUMENT
10. Press the button Change definition.
11. Choose Create F5 to enter the relevant data.
Field Field Entry
Element Process_Type
Name Process_Type
Short Description Process_Type
Structure CRMD_ORDERADM_H
Field PROCESS_TYPE
12. Go to TAB Initial Value and enter YAPP.
13. Press Enter to confirm the entries.
14. Continue to enter a description of your action, e.g. Approval by responsible Manager.
15. Skip the next two steps and complete the action definition.
16. Save your settings.
Result
The new action profile Y_DESIGN_REG_ASSISTANT was defined with an automatically action for approval of the opportunity.
4.3.1.2.2 Defining Action Profiles and Actions
Use
In this step, you change the parameters defined by the wizard in the previous step.
Procedure
1. To carry out the activity, choose one of the following navigation options:
Transaction Code CRMC_ACTION_DEF
IMG Menu Customer Relationship Management → Basic Functions →
Actions → Actions in Transaction → Change Actions and
Conditions → Define Action Profiles and Actions
2. Double Click Y_DESIGN_REG_ASSISTANT – BP Action Profile for Design Registration.
3. Press button Display -> Change (Ctrl+F1).
4. Select folder Action Definition in the dialog structure.
5. Change the action merging from Max. 1 Unprocessed Action for Each Action Definition to Max. 1 Action for Each Action Definition.
6. Save your settings.
4.3.1.2.3 Defining Conditions
Use
In this step, you process the action templates you have created in the activity Defining Action Profiles and Actions. Define the following characteristics in the newly created action profile BP Action Profile for Design Registration.
Procedure
1. To carry out the activity, choose one of the following navigation options:
Transaction Code CRMC_ACTION_CONF
IMG Menu Customer Relationship Management → Basic Functions →
Actions → Actions in Transaction → Change Actions and
Conditions → Define Conditions
2. Double Click BP Action Profile for Design Registration.
3. Choose Create from the toolbar at the right side and select
− Approval: Set Status "In Process" of related DR Opportunity
4. Save your settings.
4.3.2 Settings for Design Registration Projects/Opportunities
4.3.2.1 Defining Authorization Code for Status
Use
The purpose of this activity is to create an authorization code for approving the design request opportunity. Only those users can set the status assigned to the respective code that are authorized for. Additionally the authorization code has to be assigned in the authorization role of the user.
Procedure
1. To carry out the activity, choose one of the following navigation options:
Transaction Code SPRO
IMG Menu Customer Relationship Management → Transaction → Basic
Settings → Status Management → Define Status Authorization Keys
2. Choose New Entries.
3. Enter the following values:
AuthKey Text
YRELOPP Release Opportunity
4. Save your entries.
Result
This setting is used for authorization purposes in the next step.
4.3.2.2 Defining Status Schemes
4.3.2.2.1 Defining Status Scheme Y_DRGP
Use
The purpose of this activity is to create a new status profile to be used in Design Registration Projects.
Prerequisites
The standard status profile CRMDRGP - Design Registration Project exists as copy template.
Procedure
1. To carry out the activity, choose one of the following navigation options:
Transaction Code SPRO
IMG Menu Customer Relationship Management → Channel Management
→ Channel Sales →Industry Specific Channel Sales →
Channel Sales for Hi-Tech Industry → Partner Design Projects
→ Setting for Design Projects → Define Status Profile for User Status
2. To create a new status profile Y_DRGP - BP Design Registration Project as a copy of CRMDRGP – Design Registration Project perform the following steps:
3. Mark status profile CRMDRGP and choose Copy.
4. Enter the following values:
Status Profile Text Maintenance Language
Y_DRGP BP Design Registration Project EN
5. Choose Enter.
6. Insert the following new entry in table.
Status No.
Status Short Text
Init. Status
Lowest Highest Position Prio Auth. code
Trans.
25 PWON Partially Won
20 40 1 1
7. Save the new entry.
Result
A new status profile Y_DRGP has been created.
4.3.2.2.2 Defining Status Scheme Y_DRGO
Use
The purpose of this activity is to create a new status profile to be used in Design Registration Projects.
Procedure
1. To carry out the activity, choose one of the following navigation options:
Transaction Code SPRO
IMG Menu Customer Relationship Management → Channel Management
→ Channel Sales → Industry Specific Channel Sales →
Channel Sales for Hi-Tech Industry → Partner Design Projects
→ Setting for Projects → Define Status Profile for User Status
2. Choose New Entry (F5) to create a new status profile Y_DRGO - BP Design Registration Opp.
3. Enter the following values:
Field Field Entry
Status Profile Y_DRGO
Text BP Design Registration Opp.
Maintenance Language
EN
4. Choose Continue.
5. Position on new status profile Y_DRGO and choose Details to enter the following data.
Status No.
Status Short Text Init. Status
Lowest Highest Position Prio Auth. code
Trans.
10 NEW Design Requested
X 10 30 1 1 OPEN
20 RQNA Request Not Approved
20 30 1 1 YRELOPP FINI
30 INPR In Process 20 90 1 1 YRELOPP INPR
40 REJE Rejected 30 90 1 1 FINI
50 REJD Design Lost
30 90 1 1 FINI
80 DGWN Business Win
30 90 1 1 FINI
90 LOST Business Lost
30 90 FINI
6. Set the cursor on status Request not approved and choose Details (F2) to set the transaction control.
7. Choose New Entries (F5) and go to Change document.
8. Set the radio buttons Forbidden and Set.
9. Save the new entry.
Result
A new status profile Y_DRGO has been created.
4.3.2.2.3 Defining Status Scheme YDROPP_I
Use
The purpose of this activity is to create a new status profile to be used in Design Registration Opportunity item.
Procedure
1. To carry out the activity, choose one of the following navigation options:
Transaction Code SPRO
IMG Menu Customer Relationship Management → Channel Management
→ Industry Specific Channel Sales → Channel Sales for Hi-
Tech Industry → Partner Design Projects → Setting for Projects
→ Define Status Profile for User Status
2. Choose New Entry (F5) to create a new status profile YDROPP_I – BP DR Opportunity Item.
3. Enter the following values:
Status Profile YDROPP_I
Text BP DR Opportunity Item
Maintenance Language
EN
4. Choose Continue.
5. Set the cursor on status profile YDROPP_I and choose Details to enter the following data.
Status No.
Status Short Text Init. Status
Lowest Highest Position Prio Auth. code
Trans.
10 PROC In process X 1 50 1 1 INPR
20 DLST Design Lost
1 50 1 1 LOST
30 WINN Business Won
1 50 1 1 WINN
40 LOST Business Lost
1 50 1 1 LOST
6. Save your entries.
Result
A new status profile YDROPP_I has been created.
4.3.2.3 Sales Cycle and Phases
4.3.2.3.1 Defining Sales Cycle
Use
A sales cycle is defined by time, by the start and estimated end date of an opportunity. The sales cycle of a product or service begins with the recognition of an opportunity. The process ends with
a sales order or a rejection from the customer. The sales cycle for an opportunity is split into different phases, for example, project scope, decision making phase and so on.
For scenario Design Registration, for example, the following phases in the opportunity are used that are related to certain status described in the table below.
Phase Possible Status Description
Design Registration Request Design Requested DR Requested, needs to be approved
Design Registration Request Request Not Approved DR requested, Request not approved, Opportunity closed
Design Registration Approved
In process DR Owner is officially assigned to follow up on this opportunity
Design Registration Approved Design Lost OEM decided against Brand Owner, Opportunity closed
Design Registration Approved Rejected Brand owner decided not to follow up on the opportunity, Opportunity closed
Design In In process OEM has decided to use the products of the Brand owner in his product
Design In Business lost OEM decided to reject his decision to use our products, Opportunity closed
Design In Rejected Brand Owner decided to reject the opportunity after the OEM has decided to use our products
Design Win Business Win Sales Order request has been issued by customer. Opportunity still open for final remarks or reviews
In Production Business Win Regular sales order requests are coming. Opportunity is used for forecast. Opportunity still open
Complete Business Win OEM has finished ordering the products. Opportunity closed
In this step, you define the possible sales cycles for your enterprise. Then you assign the sales cycle in customizing to the business transaction type for opportunities. The sales cycle is set in the document, depending on the transaction type chosen.
Procedure
1. To carry out the activity, choose one of the following navigation options:
Transaction Code SPRO
IMG Menu Customer Relationship Management → Transactions →
Settings for Opportunities → Define Sales Cycle and Phases → Define Sales Cycle
2. Choose the New Entry button.
3. Maintain the following data:
Sales Cycle Description Service Description
YDRP BP DR Project BP Design Registration Project
YORD BP DR Opp. BP Design Registration Opportunity
4. Save your entries.
4.3.2.3.2 Defining Phases
Use
In this step, you define the possible phases for your sales cycles.
Procedure
1. To carry out the activity, choose one of the following navigation options:
Transaction Code SPRO
IMG Menu Customer Relationship Management → Transactions →
Settings for Opportunities → Define Sales Cycle and Phases → Define Phases
2. Choose the New Entry button.
3. Maintain the following data:
Phase Description Description
YD1 Project Initiation Project Initiation
YD2 Project Scope Def. Project Scope Definition
YD3 Decision Making Decision Making
YD4 In Production In Production
YD5 Complete Complete
YO1 Design Reg. Request Design Registration Request
YO2 Design Req. Approved Design Request Approved
YO3 Design In Design In
YO4 Design Win Design Win
4. Save your entries.
4.3.2.3.3 Assigning Phases to Sales Cycles
Use
A phase is a section of the sales cycle in which specific activities are carried out.
You define the following in this section:
• The phases which can occur in a sales cycle Depending on the sales cycle, the phases which you have assigned here are displayed in the document in the phase field in the input help.
• The time sequence of the phases one after the other within the sales cycle
• The probability in % with which the opportunity will be successful within a specific phase (for example, in the project scope phase, there is a 30 % probability that the opportunity will be closed successfully) The percentage entries set here are transferred into the document as a default value for the phase selected.
Procedure
1. To carry out the activity, choose one of the following navigation options:
Transaction Code SPRO
IMG Menu Customer Relationship Management → Channel Management
→ Industry Specific Channel Sales → Channel Sales for Hi-
Tech Industry → Partner Design Projects → Setting for Projects
→ Assign Phases to Sales Cycles
2. Choose the New Entry button.
3. Enter the following data:
Sales Cycle
Description Phase Description Seq. Anal. phase
Description Exptd. Dur.
Prob
abil.
YDRP BP Design Registration Project
YD1 Project Initiation
10 10
YDRP BP Design Registration Project
YD2 Project Scope Definition
20 30
YDRP BP Design Registration Project
YD3 Decision Making
30 50
YDRP BP Design Registration Project
YD4 In Production
40 100
YDRP BP Design Registration Project
YD5 Complete 50 100
YORD BP Design Registration Opportunity
YO1 Design Registration Request
10 0
Sales Cycle
Description Phase Description Seq. Anal. phase
Description Exptd. Dur.
Prob
abil.
YORD BP Design Registration Opportunity
YO2 Design Request Approved
20 10
4. Save your entries.
4.3.2.4 Defining OEM Project Status
Use
The OEM Project Status describes the status of the design project at the customer site.
Procedure
1. To carry out the activity, choose one of the following navigation options:
Transaction Code SPRO
IMG Menu Customer Relationship Management → Channel Management
→ Channel Sales � Industry Specific Channel Sales →
Channel Sales for Hi-Tech Industry → Partner Design Projects
→ Setting for Design Projects → Define Project Status at Customer Site
2. Delete existing standard entries 01 and 02.
3. Enter the required data:
OEM Project Status Description Description
Y10 Project Idea Project Idea
Y20 Design Engineering Design Engineering
Y30 Prototype Prototype
Y40 Test Test
Y50 Production Production
4. Save your entries.
4.3.3 Settings for Transactions
4.3.3.1 Defining Transaction Types
4.3.3.1.1 Defining Transaction Type BP DR Project YDRP
Use
The purpose of this activity is to create a new document type for Project to be used in the Design Registration scenario for High Tech.
Prerequisites
The standard project DRGP – Project exists as copy template.
Procedure
1. Access the activity using the following navigation options:
Transaction Code SPRO
IMG Menu Customer Relationship Management → Transactions → Basic
Settings → Define Transaction Types
2. To create a new transaction type YDRP – BP DR Project as a copy of DRGP – Project perform the following steps:
3. Mark business transaction DRGP and choose Copy as…
4. Enter the following values:
Transaction Type Description
YDRP DR Project
5. Choose Enter.
6. On screen Specify object to be copied choose copy all and confirm the following information. Now the project type YDRP is created.
7. To assign the former defined profiles, highlight line YDRP – DR Project.
8. Choose Details and make the following entries:
Description BP Design Registration Project
Profile ID Description
Text Determination Proc.
OPP00001 Opportunity
Partner det. proc. YDRP0001 BP Design Registration Project
Status Profile Y_DRGP BP Design Registration Project
Org. data prof. Y00000000001 BP Sales Org. Data Profile - Country/Reg
Date Profile DRGPDATES Project
Action Profile
9. Open Folder Assignments of Business Transaction Categories in the dialog structure.
10. Mark the entry Project.
11. Open folder Customizing Header in the dialog structure to assign the sales cycle.
12. Enter sales cycle YDRP BP Design Registration Project in field sales cycle.
13. Do not change the values of the other fields.
14. Save your entries.
Result
The settings for the new business transaction YDRP have been maintained.
4.3.3.1.2 Defining Transaction Type Assembly YRGA
Use
The purpose of this activity is to create a new document type for Assembly to be used in the Design Registration scenario for High Tech.
Prerequisites
The standard assembly DRGA – Assembly exists as copy template.
Procedure
1. Access the activity using the following navigation options:
Transaction Code SPRO
IMG Menu Customer Relationship Management → Transactions → Basic
Settings → Define Transaction Types
2. To copy new transaction type YRGA – BP DR Assembly as a copy of DRGA – Assembly perform the following steps:
3. Mark business transaction DRGA and choose Copy as…
4. Enter the following values:
Transaction Type Description
YRGA DR Assembly
5. Choose Enter.
6. On screen Specify object to be copied choose copy all and confirm the following information. Now the project type YRGA is created.
7. To assign the former defined profiles, highlight line YRGA – BP DR Assembly.
8. Choose Details and make the following entries:
Description BP DR Design Registration Assembly
Profile ID Description
Text Determination Proc.
OPP00001 Opportunity
Partner det. proc. YDRA0001 BP Design Registration Assemb.
Status Profile Y_DRGP BP Design Registration Project
Org. data prof. Y00000000001 BP Sales Org. Data Profile - Country/Reg
Date Profile DRGPDATES Project
Action Profile
8. Save your settings.
Result
The settings for the new business transaction YRGA have been maintained.
4.3.3.1.3 Defining Screen Layout for new Transaction Type
Use
This step has to be performed to assign the standard layout for an assembly.
Prerequisites
The standard settings for screen control of transaction type DRGA – Assembly exists as copy template.
Procedure
1. Access the activity using the following navigation options:
Transaction Code SPRO
IMG Menu Customer Relationship Management → Transactions → Basic
Settings → User Interface Settings → Set Up Screen Sequence Control
2. Enter the transaction type DRGA and the UI method Order to copy the screen sequence control data from the standard.
Field Field Entry
Transaction Type DRGA
UI Method Order
3. Press the button Copy.
4. Enter in area Object to be created the following data.
Field Field Entry
Transaction Type YRGA
Screen Profile ASSMB_STND
5. Press button Start Copy transaction.
4.3.3.1.4 Defining Transaction Type DR Opportunity YORG
Use
The purpose of this activity is to create a new document type for Opportunity to be used in the Design Registration scenario for High Tech.
Prerequisites
The standard project ORGN – Des.Registration Opp exists as copy template.
Procedure
1. Access the activity using the following navigation options:
Transaction Code SPRO
IMG Menu Customer Relationship Management → Transactions → Basic
Settings → Define Transaction Types
2. Mark business transaction ORGN and choose Copy as…
3. Enter the following values:
Transaction Type Description
YORG DR Opportunity
4. Choose Enter.
5. On screen Specify object to be copied choose copy all and confirm the following information. Now the project type YORG is created.
6. To assign the former defined profiles, highlight line YORG – DR Opportunity.
7. Choose Details and make the following entries:
Description BP Design Registration Opportunity
Profile ID Description
Text Determination Proc.
DREG0001 Design Registration
Partner det. proc. YDRD0001 BP Design Registration Opp
Status Profile Y_DRGO BP Design Registration Opp.
Org. data prof. Y00000000001 BP Sales Org. Data Profile - Country/Reg
Date Profile DRGODATES Design Registration
Action Profile Y_DESIGN_REG_ASSISTANT BP Action Profile for Design Registration
8. Maintain settings for transaction category Opportunity.
9. Open Folder Assignments of Business Transaction Categories in the dialog structure.
10. Mark the entry Opportunity.
11. Open folder Customizing Header in the dialog structure to assign the sales cycle.
12. Enter sales cycle YORD – BP Design Registration Opportunity in field sales cycle.
13. Do not change the values of the other fields.
14. Save your settings.
Result
The settings for the new business transaction YORG have been maintained.
4.3.3.1.5 Defining Item Category YORG
Use
The purpose of this activity is to create item category for the opportunity to be used in the Design Registration scenario for High Tech.
Prerequisites
The standard item category OREG – Registration Item exists as copy template.
Procedure
1. Access the activity using the following navigation options:
Transaction Code SPRO
IMG Menu Customer Relationship Management → Transactions → Basic
Settings → Define Item Categories
2. To create a new item category YORG – BP Des.Registr. Item as a copy of OREG – Registration Item perform the following steps:
3. Mark item category OREG and choose Copy as…
4. Enter the following values:
Item Category Description
YORG BP Des.Registr. Item
5. Choose Enter.
6. On screen Specify object to be copied choose copy all and confirm the following information.
7. To assign the former defined profiles, you highlight line YORG – BP Des.Registr. Item.
8. Choose Details and make the following entries:
Field Entry
Profiles
Text Det. Procedure OPP00001 Opportunity Item
Partner Determ.Proc. YDRO0002 BP Design Reg.Opp. Item
Status Profile YDROPP_I BP DR Opportunity Item
Org. Data Prof. 000000000007 Standard Org. Data Profile (Item)
Date Profile OPP_ITEM Date Profile Opportunity (Item)
Action Profile OPP_SUB Opportunity Hierarchy
9. Save your entries.
Result
The settings for the new item category YORG have been maintained.
4.3.3.1.6 Defining Item Category Determination
Use
In this process, you can define, per business transaction category and item category group, which item categories the system defaults for processing business transactions. At the same time, you can define which item categories can alternatively be entered manually for system default. There are a maximum of three alternative item categories possible.
Procedure
1. To carry out the activity, choose one of the following navigation options:
Transaction Code SPRO
IMG Menu Customer Relationship Management → Transactions → Basic
Settings → Define Item Category Determination
2. Create the following entries:
Trans. Type
Desc.Tran ItmCtyGrp Item usage
Main
ItmCty
Desc. Itm cat.
Item Cat.
Desc.ItmCty
YORG Des.Registration Opp
YORG Des.Registr. Item
YORG Des.Registration Opp
NORM Sales Item
YORG Des.Registr. Item
3. Save your entries.
Result
You have added your own Transaction Type to the Item Category Determination.
4.3.3.1.7 Defining Copying Control for Transaction Types
Use
In this step, you define the control for copying business transaction types to process the document flow.
To do this, you enter a source transaction type and a target transaction type, and define the corresponding conditions for this combination.
Procedure
1. To carry out the activity, choose one of the following navigation options:
Transaction Code SPRO
IMG Menu Customer Relationship Management → Transactions → Basic
Settings → Copying Control for Business Transactions → Define Copying Control for Transaction Types
2. Choose New Entries.
3. Enter the following data:
Trans. Type
Trans. tpye
Description Serv.Proc
Copy item no.
…
YORG AG Quotation
4. Save your entries.
Result
You have assigned the Transaction Types Quotation to the copying control for your own Transaction Type.
4.3.3.1.8 Defining Copying Control for Item Categories
Use
In this step, you define the control for copying item categories. To do so, you enter a source item category and a target item category, and define the corresponding conditions.
Procedure
1. To carry out the activity, choose one of the following navigation options:
Transaction Code SPRO
IMG Menu Customer Relationship Management → Transactions → Basic
Settings → Copying Control for Business Transactions → Define Copying Control for Item Categories
2. Select New Entries
3. Enter the following data:
SourceCat TargItmCat Description Copying routine
Copy conditions
Generate data
YORG ACT Activity Item ACT001 Do not copy conditions
X
YORG AGN Quotation Item
Copy all conditions
4. Save your entries.
Result
You have assigned the Item Categories from the DR Opportunity to the Item Categories of the Sample Request and the quotation. Now it is possible to transfer products from DR Opportunity to the Sample Request and Quotations.
4.3.3.1.9 Selecting Relevant Transaction Types
Use
In this process, you select the Transaction Types you want to use.
Procedure
1. To carry out the activity, choose one of the following navigation options:
Transaction Code SPRO
IMG Menu Customer Relationship Management → Transactions → Basic
Settings → Define Transaction Types
2. Set the following Transaction Types to Inactive:
Trans. Type
Description Serv. Proc
Description Inactive
DRGA Assembly Design Registration Assembly
X
DRGP Project Design Registration Project
X
ORGN Des.Registration Opp
Design Registration Opportunity
X
3. Save your entries.
4.3.3.2 Maintaining Status Reason and Status Profile for Opportunities
4.3.3.2.1 Define Catalog
Use
In this activity, you define a new catalog.
You access each catalog individually, define profiles with short texts, and can then assign code groups using the application help in the second level under Code groups for profile.
The key for the code group profile contains the catalog type so that it is unique.
You use the profile for filtering purposes, that is, the catalog record key consists of the catalog type, code group, and code.
Prerequisites
The standard catalog O1 – Opportunity: Reason for Status exists as copy template.
Procedure
1. To carry out the activity, choose one of the following navigation options:
Transaction Code SPRO
IMG Menu Customer Relationship Management → Transactions →
Settings for Opportunities → Maintain Status Reasons and
Status Profiles for Opportunities → Define Catalogs
2. Select catalog O1.
3. Choose Copy as.
4. Enter the following data:
Catalog Descript. Catalog type S Keyword
Y1 BP DR Opportunity: Reason for Status
Status Reason (Opportunities)
BP DR Rsn: Status
5. Save your entries.
Result
New catalog Y1 has been created.
4.3.3.2.2 Defining Code Groups and Codes for Catalogs
Use
In this activity, you define code group profiles. You create procedures that should only contain a selection of the code groups of a catalog.
You access each catalog individually, define profiles with short texts, and can then assign code groups using the application help in the second level under Code groups for profile.
The key for the code group profile contains the catalog type so that it is unique.
You use the profile for filtering purposes, that is, the catalog record key consists of the catalog type, code group, and code.
Procedure
1. To carry out the activity, choose one of the following navigation options:
Transaction Code SPRO
IMG Menu Customer Relationship Management → Transactions →
Settings for Opportunities → Maintain Status Reasons and
Status Profiles for Opportunities → Define Code Groups and Codes for Catalogs
2. Select catalog Y1.
3. Within the dialog structure choose Code Groups.
4. Choose New Entries.
5. Enter Code Group YDRGO001.
6. Within the dialog structure choose Code Groups for Profile.
Code Group Description Status
YDRGO001 Design Registration Released
7. Select Code Group YDRGO001.
8. Within the dialog structure choose Codes.
9. Choose New Entries.
10. Enter the following data:
Code Description
Y001 Price Not Competitive
Y002 Gap in Technical Requirements
Y003 Decision by OEM
Y004 Decision by Brand Owner
Y005 Legal Requirements
11. Press ENTER.
12. Save your entries.
Result
You have assigned Code Groups, containing Codes, to the Code Groups. The Code Groups are assigned to the Subject Profiles, which are assigned to the Transaction Types and Status.
4.3.3.2.3 Defining Code Group Profiles
Use
In this activity, you define code group profiles. You create procedures that should only contain a selection of the code groups of a catalog.
You access each catalog individually, define profiles with short texts, and can then assign code groups using the application help in the second level under Code groups for profile.
The key for the code group profile contains the catalog type so that it is unique.
You use the profile for filtering purposes, that is, the catalog record key consists of the catalog type, code group, and code.
Procedure
1. To carry out the activity, choose one of the following navigation options:
Transaction Code SPRO
IMG Menu Customer Relationship Management → Transactions →
Settings for Opportunities → Maintain Status Reasons and
Status Profiles for Opportunities → Define Code Group Profiles
2. Select catalog Y1.
3. Within the dialog structure choose Definition of Code Group Profile.
4. Enter a new Code Group Profile YDRGO0001.
Code group profile Description
YDRGO0001 Design Registration
5. Press ENTER.
6. Select Code Group Profile YDRGO0001.
7. Within the dialog structure choose Code Groups for Profile.
8. Choose New Entries.
9. Select YDRGO0001 As Code Group.
10. Press ENTER.
11. Save your entries.
Result
You have assigned Code Groups, containing Codes, to the Code Groups. The Code Groups are assigned to the Subject Profiles, which are assigned to the Transaction Types and Status.
4.3.3.2.4 Defining Subject Profile
Use
In this activity, you define code group profiles. You create procedures that should only contain a selection of the code groups of a catalog.
You access each catalog individually, define profiles with short texts, and can then assign code groups using the application help in the second level under Code groups for profile.
The key for the code group profile contains the catalog type so that it is unique.
You use the profile for filtering purposes, that is, the catalog record key consists of the catalog type, code group, and code.
Procedure
1. To carry out the activity, choose one of the following navigation options:
Transaction Code SPRO
IMG Menu Customer Relationship Management → Transactions →
Settings for Opportunities → Maintain Status Reasons and
Status Profiles for Opportunities → Define Subject Profiles
2. Choose New Entries and enter the following data:
Subj.Prof. SubjPrfCat. Text
YDRGO0001 Status Reason (Opportunities) BP Des. Reg. Opportunity
3. Select Subject Profile YDRGO0001.
4. Within the dialog structure choose Code Group Profile for Subject Profile.
5. Choose New Entries.
6. Enter a Catalog Y1 and Code Group Profile YDRGO0001.
Catalog CdGrpPrfle CdPrfle Text
Y1 BP DR Rsn: S YDRGO0001 Design Registration
7. Press ENTER.
8. Select this entry.
9. Within the dialog structure choose Code Groups.
10. Choose New Entries.
11. Select YDRGO0001 As Code Group.
12. Press ENTER.
13. Save your entries.
Result
You have assigned Code Groups, containing Codes, to the Code Groups. The Code Groups are assigned to the Subject Profiles, which are assigned to the Transaction Types and Status.
4.3.3.2.5 Assign Status Profile and Subject Profile to Business Transaction Type
Use
In this step, you assign subject profiles to the business transaction opportunity for each status that you have defined in the user status profile. In this way, the system provides you with possible reasons in the document in the input help, depending on the status you have chosen.
Procedure
1. To carry out the activity, choose one of the following navigation options:
Transaction Code SPRO
IMG Menu Customer Relationship Management → Transactions →
Settings for Opportunities → Maintain Status Reasons and
Status Profiles for Opportunities → Assign Status Profile and Subject Profile to Business Transaction Type
2. Choose New Entries.
3. Enter the following data:
Trans. type Status Descriptn. Subj.Prof. Option
YORG E0004 BP Des.Registr. Opp
YDRGO0001 Reason is necessary
YORG E0008 BP Des.Registr. Opp
YDRGO0001 Reason is necessary
YORG E0009 BP Des.Registr. Opp
YDRGO0001 Reason is necessary
YORG E0010 BP Des.Registr. Opp
YDRGO0001 Reason is necessary
4. Press ENTER.
5. Save your entries.
Result
You have assigned subject profiles to the business transaction opportunity for each status.
4.3.4 Sales Methodology
4.3.4.1 Defining Questionnaires
Use
The questionnaire in the opportunity is based on the survey. A survey is created in the Survey Suite. This is a tool for managing surveys, opinion polls and questionnaires. The surveys can be found in the left area of the Suite. The surveys for each application are found in the corresponding folders in the tree.
For an overview of the available surveys for the relevant application, open the folder for that application.
To display the content of a survey, double-click the survey you wish to see. The content is displayed on the right hand side of the screen.
If a translation has been created for a survey, and is available, the symbol next to the survey in the tree is the symbol for the "Translate" function.
It is possible to copy an existing survey. In this way, you make savings by reusing questionnaires in the same or similar survey projects.
Procedure
Access the activity using one of the following navigation options:
Transaction code CRM_SURVEY_SUITE
SAP CRM IMG menu Customer Relationship Management → Transactions →
Settings for Opportunities → Sales Methodology →
Questionnaire for Opportunities → Define Questionnaire
Using the predefined Best Practices questionnaires:
1. In the list of applications choose the component OPPORTUNITIES.
2. Choose Import.
3. Select the predefined Best Practices questionnaire from the directory MISC of the SAP Best Practices documentation CD:
• BP_OPPORTUNITY_EN: English version of the questionnaire
• BP_OPPORTUNITY_DE: German version of the questionnaire
4. Select the uploaded questionnaire and choose Activate.
Defining your individual questionnaire:
1. In the list of applications choose the component OPPORTUNITIES.
a. Press button Create (F5) to create a new questionnaire.
b. If you have already assigned a survey to the component, you can choose button Change (F6) to maintain it.
c. If you are copying an existing survey from another application, select the survey, choose the button Copy (F7), assign your newly created survey to application OPPORTUNITIES and rename the survey.
You can edit your questionnaire in the Survey Builder that is opened for case a. and b.
A template is generated for a newly created survey. It already contains a survey title and a section with a question/answer and pushbuttons to send or reset the filled out questionnaire.
2. You can maintain survey attributes (CTRL + F12) to make central settings for your questionnaire.
The system opens a dialog box in which you can decide, for example, whether the survey can
still be changed after sending or for which scenarios is it valid.
Create Survey Elements:
1. In the upper left screen area, select the hierarchy node in the structure view of the questionnaire.
2. Choose Insert Section to create a group of individual questions that belong together as regards subject.
The system displays detailed information for the section in the lower left screen area.
3. Enter a name into fieldText that is to appear as the title of the question group in the survey.
4. Select the new section and choose Insert Question to define your questions. The system displays entry fields in which you can enter the question text, ID (is visible in expert mode) and the rating factor.
A question consists of the attributes question text, Id, and rating factor, which you must maintain and also of as many answers as required.
A unique Id must be assigned to each question. This Id is necessary for the later evaluation of the completed survey. The system gives you a suggestion for a unique Id, but you can overwrite this.
With the rating factor, you can control the quantitative evaluation of the survey. The higher the rating factor, the greater the weighting of the question in the evaluation. In the evaluation, the calculation is made by multiplying the rating factor of each question by the rating of the selected answer.
5. Select your question and choose Insert Answer to pre-define your answers. The system displays entry fields.
An answer consists of answer attributes and answer options. According to the answer category, the answer can contain one or more answer options. For input fields and text areas, only one answer option per answer is allowed, for radio buttons, check- boxes and list boxes, as many answer options as required are possible.
A unique Id (is visible in expert mode) must be assigned to every answer. This Id is necessary for the later evaluation of the completed survey. The system will give you a suggestion for a unique Id, but you can overwrite this.
You can also determine whether the text is placed to the left or the right of the input element and whether the answer should be in display format only and therefore unchangeable.
For input fields and text areas, you must also specify the size.
If necessary, select one of the answer options as a default value that is already selected when you open the questionnaire.
6. Add other questions/answers that you want to ask in this section or create new sections with questions/answers.
The system updates the status of the questionnaire in the structure view and in the preview every time as soon as you confirm your entries.
7. To change the attributes of a survey element you created, you have to double-click on it in the structure view.
8. Choose Save.
You can run a test for the created survey (CTRL + F8).
9. Go back (F3) and activate your survey (CTRL + F1).
4.3.4.2 Defining Determination for Questionnaires
Use
The purpose of this activity is to define the rules according to which questionnaires for opportunities should be found. Here, it is possible for you to specify which questionnaires should be proposed in which time period for a specific transaction type and item category.
Procedure
1. To carry out the activity, choose one of the following navigation options:
Transaction Code SPRO
IMG Menu Customer Relationship Management → Transactions →
Settings for Opportunities → Sales Methodology →
Questionnaire for Opportunities → Define Determination for Questionnaires
2. Choose New Entries.
3. Enter the following data (leave other fields empty):
Determ. Description Serv.Proc Trans.Type Questionnaire ID Activ
Y000000000 YORG ==> BP_OPP YORG BP_OPPORTUNITY_EN or BP_OPPORTUNITY_DE
X
4. Press ENTER.
5. Save your entries.
Result
You have assigned the Questionnaire Standard to your Transaction Type YORG.
4.3.4.3 Assign Questionnaire to Transaction Type
Procedure
1. To carry out the activity, choose one of the following navigation options:
Transaction Code SPRO
IMG Menu Customer Relationship Management → Transactions →
Settings for Opportunities → Sales Methodology →
Questionnaire for Opportunities → Assign Questionnaire to Transaction Type
2. Choose transaction type YORG.
3. On the customizing header level make the following entries:
Field Entry
Assessment BP_OPPORTUNITY_EN or BP_OPPORTUNITY_DE
4. Save your entries.
4.4 Settings for Scenario Contract Management
4.4.1 Settings for Basic Functions
4.4.1.1 Defining Partner Processing
4.4.1.1.1 Defining Partner Determination Procedure
Prerequisites
The standard partner determination procedure 00000121 has to exist.
Procedure
1. To carry out the activity, choose one of the following navigation options:
Transaction Code SPRO
IMG Menu Customer Relationship Management → Basic Functions →
Partner Processing → Define Partner Determination Procedures
2. Select Procedure 00000121 – BP Design Registration Proc. and copy as Y0000121 –BP Customer Contract Header (with all entries).
3. Select Procedure Y0000121 –BP Customer Contract Header and go to folder ‘Partner Functions in Procedure’.
4. Make the following entries for partner function 00000014 Employee Responsible (CRM) and change the access sequence to 0008:
Attribute Value
Access Sequence 0008 (Preceding Document � User)
5. Save your entries.
In section Transaction Types the Partner Procedure is assigned to the relevant transaction type.
4.4.2 Settings for Transactions
4.4.2.1 Defining Transaction Type Quant./Value Contr. YQVC
Use
The purpose of this activity is to create a new document type for Opportunity to be used in the Design Registration scenario for High Tech.
Prerequisites
The standard quantity contract QVCT – Quantity/Value Cont. exists as copy template.
Procedure
1. Access the activity using the following navigation options:
Transaction Code SPRO
IMG Menu Customer Relationship Management → Transactions → Basic
Settings → Define Transaction Types
2. Mark business transaction QVCT and choose Copy as…
3. Enter the following values:
Transaction Type Description
YQVC Quant./Value Contr.
4. Set the new transaction type active.
5. Choose Enter.
6. On screen Specify object to be copied choose copy all and confirm the following information. Now the project type YQVC is created.
7. To assign the former defined profiles, highlight line YQVC – Quant./Value Contr.
8. Choose Details and make the following entries:
Description BP Quant./Value Contr.
Profile ID Description
Text Determination Proc.
ORDER001 Sales Order
Partner det. proc. Y0000121 BP Customer Contract Header
Status Profile CRMORDER Sales Order
Org. data prof. 000000000005 Org. Data Profile for Order (Header)
Date Profile CONT001 Standard Contract Dates
Action Profile
Cancellation Proced.
Condition Group
Auth. SP Hier. Cat.
9. Save your entries.
Result
The settings for the new business transaction YQVC have been maintained.
4.4.2.2 Defining Item Category Determination
Use
In this process, you can define, per business transaction category and item category group, which item categories the system defaults for processing business transactions. At the same time, you can define which item categories can alternatively be entered manually for system default.
Procedure
1. To carry out the activity, choose one of the following navigation options:
Transaction Code SPRO
IMG Menu Customer Relationship Management → Transactions → Basic
Settings → Define Item Category Determination
2. Create the following entry:
Trans. Type
Desc.Tran ItmCtyGrp Item usage
Main
ItmCty
Desc. Itm cat.
Item Cat.
Desc.ItmCty
YQVC Quantity Contract
QVCT Quantity/Value Cont.
3. Save your entries.
Result
You have added your own Transaction Type to the Item Category Determination.
4.4.2.3 Defining Copying Control for Transaction Types
Use
In this step, you define the control for copying business transaction types to integrate the transaction type YQVC in the business process and document flow for this scenario.
To do this, you enter a source transaction type and a target transaction type, and define the corresponding conditions for this combination.
Procedure
1. To carry out the activity, choose one of the following navigation options:
Transaction Code SPRO
IMG Menu Customer Relationship Management → Transactions → Basic
Settings → Copying Control for Business Transactions → Define Copying Control for Transaction Types
2. Choose New Entries.
3. Enter the following data:
Trans. Type
Trans. type
Description Serv.Proc
Copy item no.
…
AG YQVC Quant./Value Contr.
4. Save your entries.
Result
You have assigned the Transaction Types Quotation to the copying control for your own Transaction Type.
4.4.2.4 Defining Copying Control for Item Categories
Use
In this step, you define the control for copying business transaction types.
To do this, you enter a source transaction type and a target transaction type, and define the corresponding conditions for this combination.
Procedure
1. To carry out the activity, choose one of the following navigation options:
Transaction Code SPRO
IMG Menu Customer Relationship Management → Transactions → Basic
Settings → Copying Control for Business Transactions → Define Copying Control for Item Categories
2. Choose New Entries.
3. Enter the following data:
Field name Description User action and values Note
Source Item Cat. AGN
Target item cat. QVCT
Copy conditions D Copy all conditions
4. Save your entries.
4.5 Settings for Master Data
4.5.1 Maintaining Design Registrable Attributes for Products
Use
The purpose of this activity is to define a product as admissible for the design registration.
Procedure
1. To carry out the activity, choose one of the following navigation options:
Transaction Code CRMM_CSDR_PROD_MAIN
SAP Menu Industries � Channel Sales � Channel Sales for the High-Tech Industry � Master Data � Design Registration Attributes � Maintain Design Registration Attributes
2. Choose Create.
3. On the Maintain Design Registrable Attributes screen enter the following values:
Field name Description User action and values Note
Product_ID HT55-1100 Product that has to be registered
Hierarchy ID No entry
Sales Area Enter your sales area data
Start date Enter a start date Start of the registration validity period
End date Enter an end date End of the registration validity period
Registration Attribute
Select an attribute, e.g. New Design
4. Choose Save.
Result
The product can now be used within the design registration transactions.
4.5.2 Maintaining PPR Settings for Design Registration
Use
For automatically checking the Design Registration attribute of a product within a business transaction (for example, an opportunity) the Partner Product Range type for Design Registration has to be activated.
Procedure
1. To carry out the activity, choose one of the following navigation options:
Transaction Code SPRO
IMG Menu Customer Relationship Management � Master Data � Partner/Product Range � Basic Settings � Define General Settings for Partner/Product Range
2. On the Overall Control Table for Partner/Product Ranges (PPRs) screen enter the following values:
Field name Description User action and values Note
Check PPRs in Business Transactions and other Applications
Activate
PPR Type for Design Registration
Choose type 0DRG CMS Design Registration: PPR Type
3. No further changes are required.
4. Choose Save.