Skip to Content
0
Former Member
Nov 29, 2006 at 10:00 AM

Which access sequence of Partner determination should be used?

334 Views

Now my company is upgraded from CRM 2.0c to CRM 5.0 HR1. I found the different result about partner determination on business activity (via transaction code: CIC0) between two version.

<b>On CRM 2.0C</b>

<b><u>Tcode: CIC0</u></b>

Enter sold-to party code: 5300001 as activity partner, Contact person:244 on 'BP searching' workspace. Then on 'Maintain Business Transaction' workspace will display 5300001 as activity partner and 244 as Contact person.

<b><u>Configuration:</u></b>

Partner Function: 00000015 Contact person (CRM) using Access sequence 0002

Access sequence 0002 from activity partner

Dialog seq:10 has partner origin COM_PARTNER_A Preceding document and mark 'Determine in incorrect source partner'.

Dialog seq:20 has partner origin CRM_PARTNER_D General business partner model and have origin details; Partner Function category '0006 Activity partner' and Usage 'CRM'.

<b>CIC0 of CRM 5.0 HR1</b>

<u>Tcode: CIC0</u>

Enter sold-to party code: 5300001 as activity partner, Contact person:244 on 'BP searching' workspace. Then on 'Maintain Business Transaction' workspace will display 5300001 as activity partner and 66 as Contact person (66 is the first contact person of sold-to party master record:5300001).

<b><u>Configation:</u></b>

Partner Function: 00000015 Contact person (CRM) using Access sequence 0002

Access sequence 0002 from activity partner

Dialog seq:10 has partner origin COM_PARTNER_A Preceding document and mark 'Allow Incorrect Source'.

Dialog seq:20 has partner origin CRM_PARTNER_D DO NOT USE - General business partner model and have details on the source; Partner Function category '0006 Activity partner' and Usage 'CRM'.

Dialog seq:30 has partner origin CRM_PARTNER_C Business Partner Relationship and have details on the source; Partner Function category '0006 Activity partner' and Usage 'CRM'.

Please suggest me which access sequence should be used for getting the correct contact person (result same as CRM 2.0C).

Thanks you so much for support.