Business partner relationships in order entry

[Former Member]

Hello,

I have an issue with the business partner relationships. I have replicated the customer master data from ECC to CRM. In ECC the partner functions look like this for customer 100457:

SP Sold-to party 100457

BP Bill-to party 100000

PY Payer 100000

PE Sales employee 1026

SH Ship-to party 100457

SH Ship-to party 100439

ZE Employee for mail E1026

In CRM for BP 100457, the following business partner relationships exist:

Has the Bill-To Party 100000

Has the payer 100000

Has the Sales Employee 9000000621

Has the Ship-To Party/Recipient 100439

Has the Employee for Mail E1026

The problem is that when I create a sales order in CRM, I receive a pop-up where I have to select the Bill-To Party and the Payer. I can then select partner 100000 or 100457.

When entering an order in ECC, partner 100000 is selected automatically as Bill-To Party and Payer. I would like CRM to work the same way. Do you know if this is possible?

Kind regards,

Johan Wigert

[Former Member · Accepted solution]

Hi Hemant,

Before doing any changes, I checked the determination log for partners.

The partners are determined via access 20. I thus followed your suggestion

and removed access 20. The result was that none of the partners for

bill-to party, ship-to party and payer was determined.

Kind regards,

Johan Wigert

[Former Member · Accepted solution]

As said above the problem does not lie in your determination or setup, but in the concept of partner determination which is different in CRM than R/3. Only by setting the above mentioned blocking flag you will achieve the functionality you want, but then your solution cannot determine situations where a partner is e.g. a ship to for itself.

You might want to check out the blocking flag in the partner function settings, but if that does not suffice you need to write your own partner determination functions.

Regards, Kai

[former_member613650]

Hey Johan,

I have the same requirement to restrict the popups for single deviating parter when creating a sales order. can you please let me know how did you work on this requirement.

Thanks in advance,

harsha.

[Former Member]

Hi Kai,

Sorry for not addressing your reply earlier. As I understand your answer

I should set the flag in COMV_PARTNER_FCT-NO_REFLECTION. I tried this

out for the bill-to party in the above example. This works just as you

described, but this is unfortunately not sufficient. Have you been involved

in any project where the type of functionality that I require has been developed?

Is it a possible solution to implement BADI COM_PARTNER_BADI, method

COM_PARTNER_CHECK and perform an RFC-call to the ECC system to check

the partner relationships in the customer master?

Kind regards,

Johan Wigert

[Former Member]

Hello,

Anybody has any more info on this?

Thanks

[Former Member]

Hi Shwetha,

In the partner determination procedure the partner functions

- 00000003 Bill-To Party (CRM)

- 00000004 Payer (CRM)

both have the access sequence 0005 (Preceding Document -> Business

Partner Relationships: Sold-To Party -> Current Partner: Sold-To Party.)

The access sequence looks like this:

10 COM_PARTNER_A Preceding Document

20 CRM_PARTNER_A BP Relationships By Sales Organization

30 CRM_PARTNER_C Business Partner Relationships

40 COM_PARTNER_C Current Partner

I created my own copy of this access sequence (Z005) and removed step 40.

This did not help. Was this what you had in mind?

Kind regards,

Johan Wigert

[Former Member]

Hi Johan

CRM partner determination works a bit different from R/3: While in R/3 only those partners maintained in the partner roles are found, in CRM always the partner itself is found as well. If in the customizing for the CRM partner functions you set the 'Block' flag, this reflexive determination is not used. Please take into account that, however, if in R/3 you have e.g. SP 1000 with PY 1002 maintained this will work in CRM, but if you have SP 1000 with payer 1000 this will not create a relationship in CRM and therefore also the reflexive determination of 1000 as a payer will not work.

As this is fixed concept-wise, only a major change in the system can bring you around this.

Hope this helps,

Kai

[Former Member]

Hi Johan

Try removing the steps 10 and 20 also in your Z access sequence and keep only 30.

If that does not work then try removing 10 and 30 and keep only 20.

10 COM_PARTNER_A Preceding Document

20 CRM_PARTNER_A BP Relationships By Sales Organization

30 CRM_PARTNER_C Business Partner Relationship

Regards

Hemant

[Former Member]

Hi Johan,

You are getting a pop-up because 100457, has 10000 as its bill-to and payer defined in relationships and also 100457 have roles Bill-to party and payer. This pop-up would not come in case 100457 is not defined as bill-to party and payer in the system.

Did you check the partner determination procedure? Is the acess partner relationships?

Regards,

Shwetha