1. How many BP classifications exist in my SAP CRM? The business partner has five classifications.

1) Customer, 2) Consumer (Organization), 3 Consumer (Person), 4) Prospect, 5) Competitor 2) Identify the BP categories a) Person, b) Organization, c) Group BP can be created as a person (For example, a contact person), as an organization (For example, a company) or a group (for example, a grouping of natural persons like contact persons and organizations like companies). 3) The following describes BP roles: a) The BP role is assigned to the business partner based on the business process. b) Configuration of screens and fields can be done per BP role. c) Authorization checks can be setup per BP role. d) One Business partner can have one or more roles. e) None of the above. * The answer is E. The BP role is assigned to the business partner based on the business process (For example: Prospect). A BP created in prospect role can be extended to a sold-to role when a prospect becomes a customer by ordering a product or service. The BP ID is going to remain the same even after extending to the BP role from prospect to customer. 4) Can a BP with the classification "rented address" be distributed to the back-end R/3 system? A BP with the classification "rented address," can't be distributed to the back-end R/3 system, since they are used for marketing purposes only. 5) How many international address versions are supported by SAP in WAS 6.20? (ANS 11)

6) How many address formats are offered in standard my SAP CRM? a) US , b) Europe/Standard , c) Japan

7) The following explains the address usage feature: a) It is configurable and allows addresses for different usage. b) The default address in a transaction can be maintained in a partner determination. c) The system prompts for address selection if it is not specified in the partner determination, when multiple addresses are maintained in address usage. d) All of the above* e) None of the above 8) Which one of the following describes the role of the BP-type field? a) Used to group business partners. b) Used to show or hide fields in customizing. c) It can be defaulted for customers created via ICWC.

d) All of the above* e) None of the above 9) Is it possible to upload a CRM business partner to R/3 to a particular account group? a) Yes. Maintain the account group in the business partner record. b) Yes. Maintain the account group in the PIDE transaction. c) Yes. Use either A or B.* d) Yes. Use all of the above. e) No. None of the above are possible. The best practice is to configure the R/3 account groups relevant to CRM classification for CRM to R/3 distribution using PIDE transaction in R/3. Otherwise the account group can be manually maintained in customer master record in CRM that needs to uploaded into the specific account group in R/3. 10) How is the R/3 account group mapped to a CRM customer in PIDE? Via CRM classification to the R/3 account group* The R/3 account group is mapped to a CRM customer in PIDE via CRM classification to the R/3 account group.

11) How are business partner process rights controlled? a) Maintain the authorization group in the business partner. b) Assign the authorization group to a user. c) All pf the above.* d) Maintain user profiles. e) None of the above. The business partner has five classifications. 1) Customer 2) Consumer (Organization) 3 Consumer (Person) 4) Prospect 5) Competitor 12) How many types of communication data can be maintained in my SAP CRM business partner record? a) Address-dependent communication b) Address-independent communication c) All of the above* d) None of the above 13) The following defines the BP-relationship categories. a) They are used to set up the relationship type between business partners. b) The relationship between business partners could be specific to a sales area of a customer. c) The relationship could be set up to have a validity period. d) All of the above* e) None of the above 14) The following describes functionality of the easy enhancement workbench usage in business partner.

a) With the workbench you can extend the BP master data without modifications. b) The workbench requires no detailed knowledge of programming and the data dictionary. c) The workbench has a wizard to add new fields and new tables to Business partner master data. d) The workbench enhancements are retained during the software upgrade. e) All of the above. * 15) What is a visual configuration tool? a) A GUI tool b) A screen-control tool c) A BP-field and screen-control tool d) All of the above* e) None of the above The visual configuration tool is a VB-based tool provided by mySAP CRM. It has a great deal of functionality for example, the business partner record look and feel can be changed using this tool. The unused screens can be deleted. The screen labels can be changed. Fields can be moved from one screen to another screen. The tool also helps to restore the SAP standard delivered business partner screens if required nullifying the previous screen changes. Screen configurations are also transportable from one system to other system. If you go to the relationship tab in the SAP CRM Business Partner ( BP ), you will find that there are one or more tabs with different partners associated via different relationships with the main BP. Example, a BP can have the following relationships. BP 415165 1. has End Customer Friedrich Newbauer ( 531 ) 2. has Contact Person Cheryl Anderson ( 408787 )

Each of the tabs ( Has End Customer , Has Contact Person ) are called Relationship Categories. These are freely

configurable. To create a new Relationship, select the right relationship category ( For example, if you want to create a new Contact Person, select Has Contact Person ) and click on the Relationship to BP field and select the right Contact Person and click on the Create button.

If additional details were requested, fill them up and your new contact person should be created.

Configuration : The menu path for configuring already created BP Relationship Configuration is at [ spro-> IMG -> Cross Application Components -> SAP Business Partner -> BP Relationships ] Go to Properties of BP Relationship Categories to see the different relationship categories, select the Relationship Category BUR001 Contact Person Relationship for example and double click on it.

In the details section, you can see that you can do the following. 1. Click on the Hide checkmark to hide it from the standard dropdown in the Relationship Categories section of the BP Relationship view. 2. You can change the Title that shows up in the Tab 3. You can also change the position in which the tabs are displayed in the BP Relationship view.

How to Create new BP Relationship Categories in SAP ?

This part is a little tricky and can be left out if desired. This is actually an SAP Easy Access Transaction [ BUPT ] Once you are in, go to Relationship Categories or [ BUBA ]

Here you can select the right relationship category that you want to copy from and create your own. Try and avoid creating BP Relationship categories from scratch in your SAP CRM Training. Its an overkill. I created a copy of my own ( by copying from the standard BUR001 Contact Person relationship category ) and named it ZBUR09 to represent the Credit Representative relationship. We will go through some important fields here. Descriptions : The descriptions that should appear in the BPs relationship view should be specified here. We already discussed in the class what the views represent.

Cardinality : The BP Relationships cardinality ( How many Credit Reps per Account for example ) can be configured in the semantics section. You can leave it blank if you do not want to impose any constraints.

BP Relationship Possibilities : In this case you define who the first partner can be and who the second partner should be. For example in case of Has Contact Person relationship, the rule here says Only a BP of BP Category Person can be associated as a Contact Person to the first BP. The same can be extended to Credit Representative.

Results : As you can see from the picture now, the BP relationship category Has Credit Representative is showing up in the BP Relationship view.

We have specified in the BP Categories section of the BP Relationship categories config that the Partner 2 only needs to be a BP category of person. So, if you try to add any other BP category, you will get an error.

Exercises : Define a new Relationship Category Credit Controller as follows. 1. The Credit Controller is always a Person 2. There is NO reverse for it. ( Like, NO credit controlled by relationship) 3. Let the title of this relationship category tab say Credit Controller SAP CRM Business Partner Roles Business Partner Roles define the responsibilities that the BP has in transactions. Roles have a far reaching implication in the Classification System that is used extensively during the ECC-CRM data transfer process. Roles are defined in [ spro -> IMG -> Cross Application Components -> SAP Business Partner -> Business Partner -> Basic Settings -> Business Partner Role -> Define BP Roles ] There are some SAP defined BP Roles that we are not supposed to change, but we can as well create copies of the same. Here are some examples of BP roles in an

IDES system. There are not an awful lot of controls behind BP Roles. Double click a role to view the controls behind it. As usual you can copy an existing role to define your own role.

The ones that are highlighted in red are the important controls.

1. Title : You can change the title of the BP Role to reflect the description in the BP in the transaction BP. 2. Hide : If you want to hide a BP role from being displayed in the BP transaction, check-on the hide checkbox. 3. BP Role Category : A BP Role category can be associated with any number of BP Roles with one Role being defined as the standard role against the Role Category ( The check box Std. Assignment BP Role -> BP Role Category defines this ) . The controls behind BP Role Categories can be seen right on the same screen by clicking on the BP Role Categories hierarchy on the left.

Select the right BP role category and double click it to view the controls. As you can see from the controls below, the BP role category defines the BP Categories that can be associated with a particular BP Role Category (and

subsequently the BP Role) and the differentiation type. 4. BP View : Each role is technically associated with a BP View.A strong understanding of BDT is required to understand views technically and requires extensive help from your CRM Web UI or ABAP consultant. The transaction code to generate views is [ BUSD ]. The area menu for full BDT customization is [ BUPT ] and requires the expertise of module pool programming and BDT knowledge which is beyond the scope of this post. Exercises Business Scenario : Assuming that your business requires a Guarantor for the payer for transactions exceeding half a million, you have been asked to create a new BP role called Payer Guarantor. 1. Create a new BP Role called Payer Guarantor ( As a copy of Payer ). Which standard BP role would you choose to copy from ? 2. Create a new BP or modify an existing BP and try to add the newly created role Payer Guarantor to the BP . Specify the new BP Role you have created and the BP that you have extended with this newly created BP Role BP Number Ranges & Groupings

The number ranges of a BP are defined through BP Groupings which are ultimately assigned to BP Number Ranges. [ spro -> IMG -> Cross Application Components -> SAP Business Partner -> Business Partner -> Number Ranges & Groupings ] 1. Define Number Ranges : The definition of Number Ranges is pretty straight forward.

Each number range is assigned to a specific two character alpha-numeric id. for example, the number range 08 shown below specifies a number range of 400000 to 499999 and the current number range is 415190. So the next

BP that you create with that number range interval would be 415190. Also, the number range is NOT external. That means, SAP will generate the BP Number for you automatically. Now, the association between a BP and Number range is not that straight forward. There is another level of indirection called BP Groupings. Each of the groupings is assigned a Number range as defined above.

For example, the BP Grouping 0001 is assigned a number range of 08, grouping 02 is assigned a number range of 01 and so on. Whether the grouping is external or not is controlled by the number ranges parameters. The radio button Internal Std. Grouping is used to signify the fact that if you do NOT choose a grouping while creating a BP, then this number range will be used. Example, if you try and create a BP without specifying the BP Grouping in the transaction [ BP ], then by default , the BP Grouping with the radion button Internal Std. Grouping checked-on will be used during the creation process.

You can as well specify the BP Grouping explicitly. Exercises : Typically BPs are synced from ECC but there are some BPs/ Contacts that are created in CRM. Lets say that you were asked to do the following.

1. Define a new number range for a BP called Broker. The BP will be a person with the following Number Ranges. 2. Call the Number Range as Broker and assign it to a number range of 03 Create a BP with the above BP Grouping and specify the custom BP Grouping you have created along with the BP Number that you have created BP Role Field Grouping Field Grouping ( A grouping of fields that specifies which of the fields is mandatory and which of them are not ) is directly linked to the BP role. In SAP CRM however, this could be done using a variety of parameters ( Like Role, Activity type Create , change or Display Transaction , customer type etc ) among which BP Role plays a major role.The menu path for configuring this is [ spro -> IMG -> Cross Application Components -> SAP Business Partner -> Business Partner -> Basic Settings -> Field Groupings -> Configure Field Attribute per BP Role ] For example, the field grouping for BP Role Sold-to Party ( CRM000 ) has the following Data Sets and corresponding Field Groups.

The field groups are pretty obvious. You can make fields mandatory, optional , grayed out or be made hidden. Exercises : Scenario : A new BP role needs to be created called sponsor with similar attributes as Sold-to BP role. In this BP role, you have to make certain fields mandatory and certain fields hidden. 1. Create a new BP Role - Sponsor as a copy of BP Role CRM000 2. Configure the BP Role with the following fields in the following tabs set accordingly. Sales Tab o Make the Payment Guarantee Procedure to be mandatory o Hide Customer Group 4 and Customer Group 5 Shipping Tab o Make Inco Terms 1 & 2 Mandatory

Extend a BP of your choice with the newly created Sponsor BP Role and give the BP Number