Vous êtes sur la page 1sur 29

custom partner functions in table CRMV_ORLALL_BTIL (SM30)

https://websmp104.sap-ag.de/~sapidb/011000358700000409422011E

CRMC_PARTNER_FCT", "CRMC_PARTNER_PFT"

CRM->Basic Functions->Partner Processing->Define Partner Functions


There you will find the " Function category" field.
008-- Employee responsible
007-- Sales Prospect
BTPartner_PFT_0008_MAIN--- Employee resposible

SOLMAN_CM_AIC_PARTNE - Specify Partner Function Display in Transactions


This activity specifies the partner functions to be displayed in the Details assignment block, per transaction type. The
system also displays these partner functions as transaction type search criteria.
Note: For each transaction type, up to 10 partner functions can be configured.
You can configure the following, per partner function:

 Display sequence in the Details assignment block (Function and Ordercolumns)


 Role of each partner function, for example, Change Manager or Message Processor (Role Typecolumn)
 Business object layer (BOL) relation name of each partner function (Object relation namecolumn)
The system uses the entry in this field to get the partner function from the BOL model when reading and
updating the assigned business partner. If the relation name is not explicitly specified, the system uses the
partner function category and the partner function abbreviation (in English) to determine the relation name.
 Search help type for each partner function (Search Helpcolumn)
If the search help is not explicitly specified, the system uses the following determination sequence:
o Search help: Employee
Partner function abbreviation: DEVE, TEST, ITOP, CPRC, PROD, CHMA, QMAN, ADMI and PROC
o Search help: Contacts
Partner function category: 0007 Contact Person
o Search help: Sold-to party
Partner function category: 0001 Sold-To Party
o Search help: Organizational Unit
Partner function category: 0016 Service Team and 0034 Organization Responsible
o Search help: Employee
Anything not covered by the above steps
 You have made the required settings for partner functions in Customizing under SAP Solution
Manager -> Capabilities -> Change Management -> Standard Configuration -> Transaction Types >
Partner Schema.
 You have specified the generic interaction layer for business transactions, with additional
connections for the partner functions you specified, in Customizing underExtend Model for Business
Transactions with New Relations.
Note: All connections used in transactions must be specified.
1. In this Customizing activity, make the required settings for the partner functions, and save your
entries.
2. Go to transaction BSP_WD_CMPWB.
For the Detailsassignment block, the partner functions to be displayed are also determined by the BSP
configuration. This means that after you have made the settings for the partner functions, you have to adapt
the BSP configuration for the specific transaction type to match these settings.

1. Adapt the configuration for the BSP component view that contains the Detailsassignment block,
for example component AIC_CMCD_H/AICCMCDHeaderEF.
2. Adjust or add technical fields from //BTPARTNERSET//AICRM/HEADER_FCT_1 to
//BTPARTNERSET//AICRM/HEADER_FCT_10 to the configuration.
For example, in the standard component configuration only four partner functions are displayed. To make
the additional fifth partner function (for example, current processor) visible, you also need to add the
technical field //BTPARTNERSET//AICRM/HEADER_FCT_05 to the configuration.

The most important information is Order and Object Relation Name column . Those two things
should be in relation. If You Order is 6 (like is in our case) then you should
use BTPartner_PFT_0006_MAIN

Later in the WEB UI you should just use //BTPARTNERSET//AICRM/HEADER_FCT_6 and add to you
screen like is presented below.
How to add an existing field to a search page of a
different component
Skip to end of metadata

 Created by Guest, last modified by Gregor Wolf on Jun 06, 2010


Go to start of metadata

Request Description
When searching for accounts we f.i. can't search for their Sales Area Data. But let's say we only want to display accounts
that have a certain Sales Office. This guide explains how to add a field from one component (Sales) into a search of another
(Account Search). Of course the data has to be related -> check the GENIL Model Browser.

Step by Step
1. Get technical data of the Account Search
Log in to the Web UI and navigate to the Account Management. Under Search, click on Accounts. Now click in any input
field and press F2 to get the technical data. So we write down:

Component: BP_HEAD_SEARCH
View: MainSearch
Context Node: SEARCH
Role Key (Found): ZSALES

2. Get technical data of the Sales Office


Log in to the Web UI and navigate to the Account Management. Under Search, click on Accounts. Search for any account
and look at it. Find the Sales Area Data and click on Edit respectively New. Locate Sales Office under Organization and click
into the picklist. While still clicking, press F2 to get the technical data. So we write down:

Component: BP_SALES
View: CorpAccountOrgEF
Context Node: BUILRESORG
Attribute: STRUCT.SALES_OFFICE

3. Get the dictionary structure of the Account Search


We can find structures through the Genil Model Browser - Transaction GENIL_MODEL_BROWSER. Choose Component
Set ALL and press F8. Open the node Search Objects and locate BuilHeaderSearch. Open Attribute Structure and write
down...
Account Head Search Structure: CRMT_BUPA_IL_HEADER_SEARCH

4. Get the dictionary data element of the Sales Office


Again open the Genil Model Browser with Component Set ALL. We know that account and sales data are related. So we
search through the Relations.
Open Root Objects and locate BuilHeader. Open node Relations and search for the sales relation. You'll find one
called BuilSalesArrangementRel.
Open it and again open the Relations node. There you'll find an object called BuilResponsibleOrganisationRel. Open this
relation and its object. Now open Attribute Structure and the structure below it: there is our Sales Office. Open it to get the
dictionary data element and write it down...

Sales Office Data Element: CRMT_SALES_OFFICE

5. Extend the Account Search structure


Open structure CRMT_BUPA_IL_HEADER_SEARCH and click on the "Append Structure" button. Create a new structure in
your customer Namespace i.e. ZCRMT_BUPA_IL_HEADER_SEARCH and add the Sales Office as ZZSALES_OFFICE with
the data element we found in Step 4.

6. Add the Sales Office to the Account Search page


Now that we have the field Sales Office in the account search structure can we add it to the View MainSearch as search
parameter.
Open the Component Workbench - transaction BSP_WD_CMPWB - and display BP_HEAD_SEARCH. Double click
on View MainSearch and go the Configuration tab. Select the configuration of found Role Key in step 1 (or copy
configuration if there is none existing yet). Locate in Available Search Criteria the newly added Sales Office, move it to the
right side and display it.

Can we search yet? No!


We added the field to the search structure but that's it. The search logic is missing. At the moment the search would try to
find the Sales Office directly in the account header data - and that obviously won't work.

7. Enhance the Business Partner Search with BAdI implementation


Because we added a new field which doesn't belong to the account header data, must we program our own search logic.
This is done using BAdI Implementation. In transaction se18 we got to find the needed BAdI and its Enhancement Spot:

Enhancement Spot: CRM_BUPA_IL_SEARCH


BAdI: BADI_CRM_BUPA_IL_SEARCH_EXT

Open the above mentioned Enhancement Spot and go to tab Enh. Spot Element Definitions. Open the search
extension BAdI, right click on Implementation and choose Create Implementation. You will get a window showing all existing
implementations. Click on New (empty paper icon). Follow the instructions to create the implementation.

Open the newly created Enhancement Implementation. In tab Enh. Implementation Elements expand your BAdI and double
click on Implementing Class. If a class has not yet been created, create one.

Now we reached the programming part. Open your Implementing Class and the method
IF_EX_CRM_BUPA_IL_SEARCH_EXT~SEARCH_CRITERIA_INITIAL. This method should check if there are relevant
search criteria for this implementation. In our case we check if the Sales Office has been filled:
data: ls_bupa_header_search type crmt_bupa_il_header_search.

move-corresponding is_parameters to ls_bupa_header_search. " set search parameters in accout s


if ls_bupa_header_search-zzsales_office is not initial. " check if the Sales Office has been f

cv_is_not_initial = abap_true. "...and set the changing parameter to true

endif.

Now open the actual search method IF_EX_CRM_BUPA_IL_SEARCH_EXT~SEARCH_PARTNERS. This method either
gets the business partner that were found so far or nothing (parameter CT_PARTNER_KEYS). In the second case, this
method has to search for all partners and return the ones that have the searched Sales Office. The code I'm going to post is
just an example. There are maybe better ways to do it.

Data definitions:
data: ls_bupa_header_search type crmt_bupa_il_header_search, " account search structure

ls_partner_key type bupa_partner_guid, " strucutre of the parameter CT_PARTNER_

ls_partner_crm type crmm_but_lnk0141, " table which contains the SET_GUID of th


PARTNER_GUID)

ls_partner_sales type crmm_but_set0140, " table which contains the SALES_OFFICE o


SET_GUID)

lv_guid type crmmspl_bp_l0011-set_guid, " local SET_GUID variable

rt_bu_type type range of but000-type, " partner category range table for sel

rs_bu_type like line of rt_bu_type, " structure for partner category range

lv_index type sytabix, " index variable to hold sy-tabix

lv_i type i. " misc. numeric variable

Getting the account search parameters:

move-corresponding is_parameters to ls_bupa_header_search.


Search for partners if none received:
if ct_partner_keys is initial.

" set partner category filter

cv_category_filtered = abap_true.

rs_bu_type-sign = 'I'.

rs_bu_type-option = 'EQ'.

if is_category-organizations = abap_true.

rs_bu_type-low = '2'.

append rs_bu_type to rt_bu_type.

endif.

if is_category-persons = abap_true.

rs_bu_type-low = '1'.

append rs_bu_type to rt_bu_type.

endif.

if is_category-groups = abap_true.

rs_bu_type-low = '3'.

append rs_bu_type to rt_bu_type.

endif.

" get partners

select partner partner_guid from but000

into corresponding fields of table ct_partner_keys

where type in rt_bu_type.

endif.

Filter partner that have the searched Sales Office:


loop at ct_partner_keys into ls_partner_key.

lv_index = sy-tabix.
clear: ls_partner_crm, ls_partner_sales, lv_guid.

" try to get set guid...

select single * from crmm_but_lnk0141 into ls_partner_crm

where partner_guid = ls_partner_key-partner_guid.

if sy-subrc = 0.

" check if partner has wanted sales office...

if ls_bupa_header_search-zzsales_office cs '*'.

replace all occurrences of '*'

in ls_bupa_header_search-zzsales_office

with '%'.

select single * from crmm_but_set0140 into ls_partner_sales

where set_guid = ls_partner_crm-set_guid

and sales_office like ls_bupa_header_search-zzsales_office.

else.

select single * from crmm_but_set0140 into ls_partner_sales

where set_guid = ls_partner_crm-set_guid

and sales_office = ls_bupa_header_search-zzsales_office.

endif.

if sy-subrc <> 0.

"...if not, remove partner

delete ct_partner_keys index lv_index.

endif.

else.

"...if not existing, remove partner (no sales data exist for partner)

delete ct_partner_keys index lv_index.


endif.

Raise exception if no partners were found:


if ct_partner_keys is initial.

raise no_partners_found.

endif.

NOW we can search for the Sales Office. But... only for its object key. Wouldn't a picklist be much better? Of course it
would. Let's do it.

8. Create an Enhancement Set (optional)


If we want to add a picklist for our Sales Office we have to enhance the account main search and add the picklist through
programming. To do that we need an Enhancement Set. Such a set is created using transaction sm34 with View
Cluster BSPWDVC_CMP_EXT.
Secondly the Enhancement Set needs to be assigned to a client. This is done in transaction sm30
with View BSPWDV_EHSET_ASG.

9. Enhance Account Search View (optional)


Display BP_HEAD_SEARCH in the Component Workbench with your just created Enhancement Set. Right click
on View MainSearch and choose Enhance. Create all objects needed.

10. Add a picklist to the Sales Office search parameter (optional)


Go to the implementation class of the enhanced MainSearch View (probably called ZL_BP_HEAD_MAINSEARCH_IMPL).
Redefine the method GET_DQUERY_DEFINITIONS. Make sure that you call the original code from class
CL_BP_HEAD_MAINSEARCH_IMPL by using the super->get_dquery_definitions call. In addition to the Sales Office we
also provide a dropdown list for the Sales Group. This is how I've done it:

Data defintions:
DATA: lt_ddlb TYPE bsp_wd_dropdown_table, " drop down table type of method

ls_ddlb TYPE bsp_wd_dropdown_line, " cl_crm_uiu_bp_cust_get=>get_val_for_sale

lt_ddlb_opt TYPE crmt_thtmlb_search_ddlb_nvp, " drop down table type of field ddlb

ls_ddlb_opt TYPE crms_thtmlb_search_ddlb_nvp, " of parameter rt_result

lt_ddlb_group TYPE bsp_wd_dropdown_table,

ls_ddlb_group TYPE bsp_wd_dropdown_line,


lt_ddlb_opt_group TYPE crmt_thtmlb_search_ddlb_nvp,

ls_ddlb_opt_group TYPE crms_thtmlb_search_ddlb_nvp,

lt_operators type CRMT_THTMLB_SEARCH_OPERATOR,

lv_operator type CRM_THTMLB_SEARCH_OPERATOR,

ls_sales_area TYPE crmt_bus_sales_area, " sales area structure

lv_sales_office TYPE crmt_sales_office,

lt_partner_crm TYPE TABLE OF crmmspl_bp_l0011,

ls_partner_crm TYPE crmmspl_bp_l0011.

FIELD-SYMBOLS: <rs_result> LIKE LINE OF rt_result.

Calling super method:


CALL METHOD super->get_dquery_definitions

RECEIVING

rt_result = rt_result.

Adding Sales Office and Sales Group:


" Initial line of Sales Offices

APPEND INITIAL LINE TO lt_ddlb.

MOVE-CORRESPONDING ls_ddlb TO ls_ddlb_opt.

APPEND ls_ddlb_opt TO lt_ddlb_opt.

" Initial line of Sales Groups

APPEND INITIAL LINE TO lt_ddlb_group.

MOVE-CORRESPONDING ls_ddlb_group TO ls_ddlb_opt_group.

APPEND ls_ddlb_opt_group TO lt_ddlb_opt_group.

" Get all Sales Organizaions


SELECT DISTINCT sales_org channel division

FROM crmmspl_bp_l0011

INTO CORRESPONDING FIELDS OF TABLE lt_partner_crm.

LOOP AT lt_partner_crm INTO ls_partner_crm.

MOVE-CORRESPONDING ls_partner_crm TO ls_sales_area.

" Get values for SALES_OFFICE provide sales area

CALL METHOD cl_crm_uiu_bp_cust_get=>get_val_for_sales_office

EXPORTING

is_sales_area = ls_sales_area

RECEIVING

rt_value = lt_ddlb

EXCEPTIONS

error_occurred = 1

OTHERS = 2.

IF sy-subrc = 0.

LOOP AT lt_ddlb INTO ls_ddlb.

lv_sales_office = ls_ddlb-key.

" get sales groups

CALL METHOD cl_crm_uiu_bp_cust_get=>get_val_for_sales_group

EXPORTING

is_sales_area = ls_sales_area

iv_sales_office = lv_sales_office

RECEIVING

rt_value = lt_ddlb_group
EXCEPTIONS

error_occurred = 1

OTHERS = 2.

IF sy-subrc = 0.

LOOP AT lt_ddlb_group INTO ls_ddlb_group.

MOVE-CORRESPONDING ls_ddlb_group TO ls_ddlb_opt_group.

APPEND ls_ddlb_opt_group TO lt_ddlb_opt_group.

ENDLOOP.

ENDIF.

MOVE-CORRESPONDING ls_ddlb TO ls_ddlb_opt.

APPEND ls_ddlb_opt TO lt_ddlb_opt.

ENDLOOP.

ENDIF.

ENDLOOP.

lv_operator = 'EQ'.

append lv_operator to lt_operators.

LOOP AT rt_result ASSIGNING <rs_result>.

CASE <rs_result>-field.

WHEN 'ZZSALES_OFFICE'.

SORT lt_ddlb_opt BY value.

<rs_result>-ddlb_options = lt_ddlb_opt.

<rs_result>-operators = lt_operators.

WHEN 'ZZSALES_GROUP'.
SORT lt_ddlb_opt_group BY value.

<rs_result>-ddlb_options = lt_ddlb_opt_group.

<rs_result>-operators = lt_operators.

WHEN OTHERS.

ENDCASE.

ENDLOOP.

How to specify partners functions display in ChaRM and ITSM


7.1 SP5 onwards
July 19, 2013 | 758 Views |

Raquel Pereira da Cunha



more by this author

SAP Solution Manager

almApplication Lifecycle Managementcharmitsmsap solution managersapmentorsolman

 share 0
 share 0
 tweet
 share 0

Follow

A very good new functionality in my opinion released with SPS05 of SolMan 7.1 is the possibility to configure
in IMG the Partner functions to be displayed in the Details assignment block of the web client UI, per
transaction type. My example is related to ChaRM, but the functionality is valid for ITSM as well.
In one of my ChaRM projects last year I used Solution Manager 7.1 with SPS 04 and then upgraded this year
to SPS 07, some months after golive. In SP4 I had to create different transaction types based o the standard and
for each of them I had to create a different version of the web client UI. I also had to define new partner
functions besides the existing ones. The hard work began when I started to define these new web client screens
and its new partner functions. When you create a new partner function in IMG activity Partner Functions (view
COMV_PARTNER_FCT) , you select the function category and the relationship category, as in the figure
below.

But then, to make the partner function available in the web client UI before SP05, I had to find out which field
of the object BPARTNERSET could be used that corresponded to the partner function category selected. Each
BPARTNERSET field has a corresponding generic interaction layer, and for some partner functions the value
for the Request for Change is different for the value defined for Change Documents. It can be seen looking
into the classes that implement RfC and Change Documents.
From SP5 on, instead of trying to find out which BOL Object Relation Name was assigned to each field in the
web client screen looking deeply into the ChaRM Web Client classes, this new IMG activity allows you to see
how the assignment is done and change it the way you want. It’s also possible to select which type of Search
Help you need for that field, if you want to select partners of type Person or Org Unit and if they must be
searched in Business Partner function Employee, Sold-to-Party or Contact Person. This IMG activity saves
data in table AIC_PARTNER_FCT, Business Partner User Interface Control.

For each transaction type, up to 10 partner functions can be configured.


So, to specify the partner functions display in your transactions, execute the IMG activity “IT Service
Management->Partner Determination Procedure->Specify Partner Function Display in Transactions”.

Step 1: Specify Partner Function Display


You will see the screen below:

The only thing I did not really like is the fact that possible values of field Role Type (PARTNER_FCT_TYPE)
are fixed in domain AIC_CRM_PARTNER_FCT_TYPE_D, Semantical Definition of CRM Business Partner
Function. I don’t like fixed values, makes me think that I cannot adapt to the customers needs, and that
happens very, very often, even if SAP recommends not to do many things out of standard since the standard
was configured based on “most of the customers requests and on ITIL Best practices”. Each customer has its
own needs. Who implemented ChaRM in many different customers in the last 8 years knows that. I didn’t go
deep into this subject to understand why this field needs to have a fixed list of values, and cannot be
customized, but there must be a reason for that.

If you created the Z transaction types in SP05 or later versions, when you copied the standard transaction types
this table was also copied, so you just need to adjust your Z entries and include new partner functions. But in
case your transaction types are not included in this table yet, create new entries and use the standard entries as
a template. In my case they didn’t exist because the Z transaction types were created in SP4 before the
upgrade, so I had to create all the entries for all my Z transaction types in order to start using this good
functionality and keep the customer updated.

For each transaction type you will define the partner functions you want to display in Details assignment block
of the web client UI, an order, the role type, the Object Relation name, which is related to the role type, and the
Search help you want for that partner function field. You can decide if you will search for employee business
partners, sold-to-party business partner or Org Unit business partners. This Search Help option was also a very
interesting functionality added with this IMG activitiy. Now we can select which kind of search we want.

Step 2: Select the right fields for your WEB UI view


The order you define for each partner function will correspond to the name of the field that you will select in
the WEB client UI. Together with this IMG activity was also released a group of new Partner Function fields,
as you can see in the UI component for Change Documents below (transaction BSP_WD_CMPWB or IMG
Activity “CRM->UI Framework->Access UI Component Workbench”):
You probably have a custom WEB UI view for your Z transaction type, copied from the standard. In the
example below I have one UI configuration for each Z, because they must be all different from each other. I
also have one for Request for Change ZMCR.

Select the configuration you want to change and look for the partner fields according to the configuration you
have done in the IMG activity of Step 1.
Click “Show Available fields” to open the list of fields you can use. Look for the fields below
BTPARTNERSET. Click “Show Technical Details” to make your life easier. Instead of having to look for
available fields such as EMP_RESP_NAME, SERVICE_UNIT_NAME etc as before, you will look for
/AICRM/HEADER_FCT_nn.

Add the partner fields to your UI according to your configuration. If necessary, change the labels to have the
correct description of your partner functions.

Behind the scenes:


During runtime, some methods check the new tables in order to correctly fill the UI partner function fields.
One of the main classes is CL_AI_CRM_BP_HELPER.
We can see new attributes created in this class for the new partner function fields:

When you open a document, method READ_UI_FIELDS reads the table AIC_PARTNER_FCT to get the
partner functions that must be displayed and their corresponding order for the transaction type. With that
information, the business partners are moved to the correct UI fields depending on their partner function.

SolMan 7.1 Custom Partners


changing at the same time
This question is answered

Hello Experts!
Hopefully one of you will have an answer to this. My client is on 7.1 SP10.
I created two custom partner functions (e.g. CRM and Technical Coordinator) and added both fields to the
Details assignment block on ZMCR. Both are manually entered at the beginning of ZMCR (there is no access
sequence). However, when CRM is entered, Technical Coordinator automatically changes to the value in
CRM. And when Technical Coordinator is updated, CRM changes to what Technical Coordinator was
changed to. The partners are acting like they are the same field and change at the same time. They should act
independently of each other. What am I missing to make the fields independent?
Here's my configuration...
Partner Functions created...
Partner Determination. Both partners were assigned to ZMCR, ZMHF, ZMMJ, ZMAD, and ZMTM. Only
ZMCR is shown here. No access sequence is assigned in ZMCR...

Here are the Extend Business Transaction Object Model settings...

The fields added to the UI availabillity on the Business Partner User Interface control screen for all 5
transaction types.
I did not assign an Object Relation Name so the system would default to use the standard methods for the Role
Type. Both fields are also assigned to different Role Types...
Added the new Partners to the UI in the Details assignment block...
The new CRM partner was assigned to field //BTPARTNERSET//AICRM/HEADER_FCT_06 and the Tech
Coordinator Partner was assigned to //BTPARTNERSET//AICRM/HEADER_FCT_10.

In SPRO's Make Settings for Change Transaction Types, here are some of the tabs...
Here are no settings in Specify Partner Assignment...
This shows the same Object Relation Names as on the prior screen shot...

And this shows the actions assigned to ZMCR...

I'm puzzled. The fields do not appear to be linked, but they are acting linked in the UI.
I'm going to debug the methods to try to track the cause down while I wait for a response from one of the
experts.
Thanks in advance for your help!
Tags:

 solutionmanager71
 solution_manager_7.1
 itsm
 charm
 sap_solution_manager
 solman_7_1
 solman_7.1
 solman_71
 solution_manager7.1
 solution_manager_71

Robyn Osby
March 05, 2015 at 17:37 PM
0 Likes
Correct Answer

Robyn Osby replied


March 05, 2015 at 17:37 PM

I found the answer to my question while debugging the standard methods that assigned to the fields in tcode
BSP_WD_CMPWB.
Since I didn't enter an specific Object Relation Name, the system defaulted the value to the same value for both
Partner fields (shown here in debug)...

To correct that, I entered standard values that were not in use by the other partners...
The fields are now working independently in the UI.
2View this answer in context

Not what you were looking for? View more on this topic or Ask a question

1 replies
Correct Answer

Robyn Osby replied


March 05, 2015 at 17:37 PM

I found the answer to my question while debugging the standard methods that assigned to the fields in tcode
BSP_WD_CMPWB.
Since I didn't enter an specific Object Relation Name, the system defaulted the value to the same value for both
Partner fields (shown here in debug)...
To correct that, I entered standard values that were not in use by the other partners...

The fields are now working independently in the UI.


That will be all.

ChaRM: Partner Function - Role


This question is answered

Fellow Members,
I am trying to add new partner to my Partner Determination Procedure. I have created them in
Partner Determination procedure as seen below and also have made the required settings for
partner functions in Customizing under SAP Solution Manager -> Capabilities -> Change
Management ->
Standard Configuration -> Transaction Types > Partner Schema.
Now I am in "Specify Partner Function Display in Transaction" step

Here I do not see my Z Partner Functions in the Dropdown of "Role" column. Only the standard
partners are displayed.

Any Clues why is like this? Where do I add "Role Type" for my Z Partner Functions?
Regards,
Vivek
Tags:

 sap_solution_manager
Vivek Hegde
July 19, 2013 at 11:40 AM
0 Likes
Correct Answer


Raquel Pereira da Cunha replied


July 18, 2013 at 23:00 PM

Hi Vivek,
you won't see your partner function in this list. This list of role types is fixed in domain
AIC_CRM_PARTNER_FCT_TYPE_D, Semantical Definition of CRM Business Partner Function,as
shown below. You need to select one of the existing role types and assign it to your new partner function.
Your partner function will be in field Function only.

Best regards,
Raquel

1View this answer in context

Helpful Answer
by

 Joyca Vervinckt

Not what you were looking for? View more on this topic or Ask a question
4 replies
Correct Answer


Raquel Pereira da Cunha replied


July 18, 2013 at 23:01 PM

Hi Vivek,
you won't see your partner function in this list. This list of role types is fixed in domain
AIC_CRM_PARTNER_FCT_TYPE_D, Semantical Definition of CRM Business Partner Function, as
shown below. You need to select one of the existing role types and assign it to your new partner function.
Your partner function will be in field Function only.

Best regards,
Raquel

1likes

Helpful Answer

Joyca Vervinckt replied


July 19, 2013 at 09:07 AM

Hi,
I also did it like that when I was adding extra partner functions, I chose one of the existing roles that
are quite general, like Contact Person or Message Processor.
As long as you have entered your Z-partner in the Function field, as Raquel indicated, it will be fine.
Same thing for the "Object Relation Name" field, I copied one from the other existing partner
functions.
I'm not sure what effect those two fields (Role Type and Object Relation Name) have, but I haven't
noticed anything about them (yet).
Kind regards,
Joyca
1 likes

Vivek Hegde replied


July 19, 2013 at 11:40 AM

Thanks Joyca, I am able to use the existing Role Types; as you pointed out, even I do not think they
have any effect anywhere.
Thanks Again,
Vivek
0 likes

Vivek Hegde replied


July 19, 2013 at 11:39 AM

Thank You Raquel ! Appreciate it.


I figured it out this now. I was having a notion that there might be some table where in I have to enter
the Role Types while forming a new Z Partner Function. I chose the existing Role Type as you
mentioned and everthing's fine .
Thanks Again,
Vivek
0 likes

Share & Follow


Vous aimerez peut-être aussi